4 ms·
Thanks, I'll look into those. When you say ditch Apache, do you mean completely? I know a fairly common setup is to use nginx+Apache to serve Django (with ngin
by edanm 16y ago
Thanks, I'll look into those.
When you say ditch Apache, do you mean completely? I know a fairly common setup is to use nginx+Apache to serve Django (with nginx serving the static content and Apache the Django code). Should I be running everything from nginx?
- jacques_chester 16y agoPersonally I don't see the point in keeping Apache. It just adds more moving parts and more points of failure to have two HTTP daemons. I'd ditch it entirely and switch to WSGI or FastCGI.
- 2mur 16y agoYou should at least try nginx/gunicorn (http://gunicorn.org/ http://gunicorn.org/). And if your clients are constantly pinging and the data hasn't changed, make sure you are caching it in memcache (etc) to relieve the database. http://ericholscher.com/blog/2010/aug/16/lessons-learned-dash-easy-django-deployment/ http://ericholscher.com/blog/2010/aug/16/lessons-learned-das...
- edanm 16y agoHonestly, I'm a little scared of using something like gunicorn. I could be wrong, but it seems like an extremely new technology, especially when compared to Apache, which has a lot of history behind it.
- antihero 16y agoYou can have a failover, so if one breaks you can quickly boot the apache one back up.