See http://code.google.com/p/modwsgi/issues/detail?id=63
It has been listed as a task for a long time. Realize that mod_wsgi is a one man project. I have very liitle time to work on mod_wsgi as it is. It isn't like I get people donating me huge amounts of money such that I don't still have to work for a living. :-) Also why should I be making high quality documentation for someone else's project. Frankly that is a beef I have had with various projects, they assume that I will do things for them rather them developing their own decent documentation for the users of their product. That all said, I have had plans for quite a long time to develop documentation of great detail specifically focused around Django, but ultimately it comes down to what is in it for me. There ultimately is a limit of what I am prepared to do for free. BTW you should ensure you watch my PyCon talk where I do use Django as an example. http://blog.dscpl.com.au/2010/06/sydney-pycon-modwsgi-talk-slides.html Can you also perhaps add your suggestions as a comment against that issue in the issue tracker. Graham On Saturday, July 17, 2010, Dave Everitt <[email protected]> wrote: > I found the Google code mod_wsgi wiki pages very useful and clear and > got mod_wsgi up and running quickly. > > However, the 'Integration with Django' page (http://code.google.com/p/ > modwsgi/wiki/IntegrationWithDjango) isn't as clear as the 'Quick > Configuration Guide' and 'Configuration Guidelines'. Perhaps it could > be made clearer by adding subheads, and appear more up-to-date as > follows: > > 1. Collect information and issues already raised in Django tickets for > any *pre-1.0* versions of Django, under a subhead 'Older versions of > Django', so users of recent (backward compatible) versions don't have > to see irrelevant info (e.g. 'Be careful using the BuildBot > djangorecipe version 0.17...', 'Django's WSGI adapter prior to alpha > versions of version 1.0...', 'HTTPS detection done by Django was wrong > for WSGI...' etc.). > > 2. Since (as I understand it) from Django 1.0, successive versions are > backward-compatible and the majority(?) of developers are using at > least that version, make it clear at the top (instead of 'Requires > Django 0.90') that these instructions apply mainly to Django >= 1.0, > then collect version-specific issues under the 'Older versions of > Django' subhead. > > 3. Separate Windows-specific information under its own subhead. > > 4. Perhaps similar for Apache - mention up front that the instructions > apply mainly to Apache 2.*, and - although they will also work with > 1.* - the main difference is that WSGIDaemonProcess will not run. > > 5. It would - in the Python spirit - be good to have 'one obvious way' > of setting things up e.g. - daemon mode, an ideal directory structure > within a *nix user directory, a typical VirtualHost block, etc., then > cover other options afterwards. > > If it helps, I'm a good sub-editor and have a passion for making > instructions as simple as possible, although I'm sure others in the > community are more knowledgeable. > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" 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/modwsgi?hl=en. > > -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en.
