I’m running Sentry in production simply under uWSGI Emperor just fine, it certainly doesn’t need Supervisor to run. (--virtualenv blah --wsgi sentry.wsgi should already do the basic trick)
That said, for an app of your scale (as you described in the OP), I’d suggest looking into Emperoring the three different configs (obviously each different app governed by its own master, etc., just like normal). And as for launching the emperor itself to govern its vassals, depending on your distro’s (I’m assuming Linux) init.d replacement, it may be easiest to just plonk something like “uwsgi --emperor /srv/uwsgi” (plus the appropriate uid/gid flags) into /etc/rc.local to have your server start up properly on boot. But the best way to do that obviously depends on your upstart/systemd/sysvinit/... configuration. From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Vanasco Sent: Friday, May 31, 2013 7:33 AM To: uWSGI developers and users list Subject: Re: [uWSGI] recommendation sought for production deployment On May 30, 2013, at 7:06 PM, Alberto Scotto wrote: But in your case Emperor is not enough: for managing Sentry you have to use supervisor (there isn't a uWSGI plugin for it, as far as I know), as stated in Sentry's docs: http://sentry.readthedocs.org/en/latest/quickstart/index.html#running-sentry-as-a-service But hey! No problem: you will already have setup supervisor, following my and uWSGI's guidelines :) Sorry if this sounds stupid -- but i was under the impression that sentry was just a django app, and could easily be managed by uwsgi as such. I'm fine with using supervisord for it ( and was looking at having supervisord manage uwsgi ). I just thought that supervisord would manage uwsgi, and uwsgi would manage sentry and the other apps.
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
