Previously Noah Gift wrote: > On Sun, Mar 29, 2009 at 1:05 PM, Mike Orr <[email protected]> wrote: > > > > > On Sat, Mar 28, 2009 at 4:42 PM, jose <[email protected]> wrote: > > > So this brings me to the heart of what I've learned, if you are going > > > to deploy a long running app how do you do it? > > > > I put all my Pylons and Quixote apps under Supervisord, with Apache > > mod_proxy. I want to try nginx when I have a chance. > > > > Some people prefer mod_wsgi because it runs everything under Apache > > processes, but I like being able to "supervisor stop" and "supervisor > > start" individual applications for maintenance and debugging, plus > > seeing them under their own names in the ps listing. > > > This recently came up at work, at one other gotcha is that you have to write > your own init script. Is there a recipe on the Pylons wiki for this?
You can do three things: - start supervisord using init by adding an entry in /etc/inittab. This requires root and is for the very paranoid: even if supervisord dies (which never happens) it will be restarted. - use an init script to start supervisord at system boot. Requires root. - Start supervisord using an @reboot crontab entry in a normal account. Does not require root. Works on all Linux distributions, I'm not sure is other cron implementation support this. The last one is my preferred method: it is trivial to setup and can be done by any normal user. Wichert. -- Wichert Akkerman <[email protected]> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
