AFAIK, supervisord is able to take care of assuring that my process is up and running, and does this through a really nice console script. Foreman can start up/show down my processes, but does not assures that they are restarted when I would need it. I thought the same goes for uwsgi, but I might have been wrong.
thanks for your answer, I'm looking more into uwsgi as a process manager now On Mon, May 26, 2014 at 1:48 PM, Roberto De Ioris <[email protected]> wrote: > > > Hi, > > > > this is the first time trying to use uwsgi, and stuck at integrating it > > into supervisord for process management > > > > I have my project set up in a virtualenv. I've created a uwsgi.ini file, > > and can start the server manually with "uwsgi --ini > > /home/openerp/etc/openerp.uwsgi.ini". Everything works fine. > > > > Then I've created a supervisord config script file using a Procfile and > > foreman. Starting the program through supervisord fails with the > following > > log lines: > > > > > > Before investigating your problem, just one question ? why so many layers ? > > foreman is already a process starter, just configure it to start uWSGI. > Nowadays supervisord is useful only if you already have legacy apps > running on it, otherwise uWSGI by itself is a way more capable process > manager. > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
