mod_wsgi: follow-up
I believe I have the last few kinks worked out. Although I've already had experience with mod_wsgi, I always like to have documentation to refer back to. Considering the overall quality of Django documentation as a whole I've had little to complain about, but I find the relatively poor state of wsgi/django documentation a little odd.
The documentation at http://code.djangoproject.com/wiki/django_apache_and_mod_wsgi as an example is unnecessarily complex, seems to contain a lot of redundant and inexplicable configuration, and doesn't even touch on certain optimizations that seem necessary even on a low traffic site.
http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango is much, much better, but it seems more of a good starting point than anything else. If mod_wsgi is going to be the future "best practice," as far as Python web applications are concerned, it needs better documentation. Who knows, perhaps this is somewhere where I can step up and help.
blog comments powered by Disqus