StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>If you want to go the nginx route, the best choices are:</p> <ul> <li>nginx -> gunicorn</li> <li>nginx -> uWSGI</li> </ul> <p>Running Python WSGI applications on top of FASTCGI is not generally as good an experience due to issues with the FASTCGI/WSGI adapters and how they are deployed with servers.</p> <p>Apache/mod_wsgi is still a more than acceptable solution and it will actually perform better with less resources when run as:</p> <ul> <li>nginx -> Apache/mod_wsgi</li> </ul> <p>Because the bottlenecks aren't going to be the web server, ultimately it doesn't matter which you choose, so long as you set it up properly, something which most people wouldn't do as there site doesn't get enough traffic anyway, or they have no monitoring in place to know what they need to change.</p> <p>Overall, picking which you think is easier to manage is the best thing to do when starting out.</p> <p>For some background on what your real performance bottlenecks are going to be and the importance of monitoring, watch:</p> <ul> <li><a href="http://lanyrd.com/2012/pycon/spcdg/" rel="nofollow">http://lanyrd.com/2012/pycon/spcdg/</a></li> </ul> <p>That all said, you mention Heroku. Right now there is really only the once choice with Heroku and that is to use gunicorn and you wouldn't need to be worrying about nginx. That is a problem in itself though, as gunicorn alone is not a good option for serving static media assets so almost forced with Heroku to serve static assests elsewhere.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload