I picked uwsgi b/c it seemed like potentially less overhead coupled with nginx, rather than nginx > apache mod_wsgi. My reasoning was that the newer stable versions of nginx comes with uwsgi integration by default, you just need to install uwsgi to get started.
I've not using supervisor but it's super easy to start the uwsgi daemon: uwsgi --uid www-data --paste config:/location/to/your/production.ini -- socket :8080 -d /var/log/uwsgi.log cd34 was the one that mentioned it and I was prompted to look into it. This article has benchmarks: http://nichol.as/benchmark-of-python-web-servers I used this article as a reference: http://tonylandis.com/python/deployment-howt-pylons-nginx-and-uwsgi/ It works just like mod_wsgi except a lot simpler as you don't need to apache config files. On Aug 10, 10:16 am, Mike Orr <[email protected]> wrote: > On Tue, Aug 10, 2010 at 2:42 AM, Weixi Yen <[email protected]> wrote: > > My stack is nginx > uwsgi > pylons. > > I haven't heard of uWSGI before so I assume a lot of Pylons users > haven't either. From the website (http://projects.unbit.it/uwsgi/) it > looks like a mod_wsgi equivalent plus a lot of other stuff. Who here > is using it and how do you like it? > > I run my apps under Supervisor with http proxy, mainly so that I can > stop and restart them individually ("supervisor restart app1"). Does > uWSGI allow this? > > -- > Mike Orr <[email protected]> -- 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.
