On Wed, Nov 30, 2011 at 6:48 PM, Leo Shklovskii <[email protected]> wrote: > > I've just now started to look at Upstart instead of init.d for starting and > stopping processes so that may be an easy way to get the same level of > process management. Is it fairly straightforward to set up an upstart config > file for uWSGI? It did look like a lot of the init.d was boilerplate-ish.
yeah i wouldn't worry too much about the init.d script ... one way or another it's going away forever. i'm not too sure about the upstart stuff, as i'm a pretty hard-core systemd fan (it's pretty incredible on it's own merit) and hence i use that purely on all my systems ... ... but what are you looking for exactly? the simple/straightforward approach is to start an emperor/tyrant process from init (whatever "init" is), and let uWSGI and it's umpteen management methods handle it from there. are you looking to start/stop all apps manually, or create some kind of dependencies/triggers between them? looks like there is an example config in contrib: http://projects.unbit.it/uwsgi/browser/contrib/upstart/uwsgi.conf ... though i would use emperor mode, as detailed on the systemd wiki page: http://projects.unbit.it/uwsgi/wiki/SystemdIntegration -- C Anthony _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
