Comments on: Control production buildouts with supervisor

By: fRiSi

fRiSi — Thu, 15 Jan 2009 07:37:48 +0000

i don’t add my debuginstance to supervisor but start it manually (bin/debuginstance) which is actually shorter than ‘bin/supervisorctl start debuginstance’. in addition i can start it in foreground mode to enable pdb debugging.

however, supervisor seems to have a configuration option ‘autostart’ (see http://supervisord.org/manual/current/configuration.html)
i’m not sure how to pass it over in the collective.recipe.supervisor recipe. eventually the only way is to tell the recipe to use a hand-made configuration file.

By: Zupo

Zupo — Wed, 14 Jan 2009 18:25:00 +0000

Hi,

How can you make a program not auto-start? I want one Zope instance just for debugging and it should be off till I tell it otherwise?

By: fRiSi

fRiSi — Wed, 04 Jun 2008 08:08:40 +0000

for me it did not work. maybe it’s broken in 2.1 egg release:

> easy_instlal ZopeSkel
Searching for ZopeSkel
Best match: ZopeSkel 2.1
…

> paster create -t plone_hosting
… answer questions, provide proxy port 6180
… bootstrapping buildout, downloading and compiling zope, varnish etc

> find . -name supervisord.conf
> grep -r supervisor base.cfg
#do not return anything

By: Wichert Akkerman

Wichert Akkerman — Tue, 03 Jun 2008 21:07:37 +0000

This is not true: ZopeSkel does create a complete supervisor configuration. We have several deployments in production using that setup.