On Aug 11, 1:02 pm, Noah Gift <[email protected]> wrote: > On Tue, Aug 10, 2010 at 4:49 PM, Graham Dumpleton > > > > > > <[email protected]> wrote: > > > On Aug 11, 5:23 am, Mike Orr <[email protected]> wrote: > >> On Tue, Aug 10, 2010 at 10:48 AM, [email protected] <[email protected]> > >> wrote: > >> > 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 > > >> So you have a separate uwsgi daemon for each application, > > > Which you can also do with Apache/mod_wsgi. > > I have used mod_wsgi with Apache a lot and I like it. On the other > hand, nginx is a pretty cool web server. Any thought to combining > efforts on making a unified module, that shares some of the same code, > for both platforms? I could see situations where I would want to use > Apache and other situations where I would want nginx. I think they > are both good to have around.
I have pondered that for mod_wsgid. That is mod_wsgi without embedded mode, but now having its own process manager (supervisor). Technically the daemon infrastructure, even though written against Apache runtime library could be used as back end to nginx in similar style to uWSGI, but retaining various features mod_wsgi has which uWSGI doesn't. I will not disagree that nginx from everything I know is better for static file handling, and also the behaviour of mod_proxy in nginx when used as a front end to Apache/mod_wsgi allows Apache to work more efficiently for dynamic web application with less resources than if no front end. Ie., due to nginx acting as network buffer and isolating Apache from slow clients. This model of nginx proxying to Apache/mod_wsgi does as some point out though mean having to manage multiple servers, so the daemon infrastructure of mod_wsgi directly behind nginx is attractive, presuming that mod_proxy's good qualities in nginx can be harnessed in that arrangement as well. Why am I not doing this though. The prime reason is lack of time. When I can find myself a better job, maybe I'll get that opportunity time wise to pursue it. This does though presume I can get the motivation up as well. The joke used to be that every man and his dog was writing a Python web framework, now it is that every man and his dog is writing a WSGI hosting mechanism. With the rash of options around, one has to question whether yet another variation is going to be accepted or not. A further issue is trying to support multiple servers. Right now I am happy with supporting just Apache because it means I can do a top class job with it and ensure that it works perfectly. When you support multiple servers, you have to spread your time more across all the options and quality potentially drops. This may be fine for the uWSGI folks who get to do the work as part of their paid day job and have customers potentially paying them for support as well, but I don't have that luxury. All the same, would be interested to here if people think that supporting other servers would be good, or whether felt that uWSGI, and Phusion Passenger, is already satisfying that space now and so no point. Graham > >> rather than > >> one for all the applications? In that case, the uwsgi command line > >> itself could run under Supervisor. > > >> -- > >> 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 > > athttp://groups.google.com/group/pylons-discuss?hl=en. > > -- > Thanks, > > Noah -- 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.
