Suggested method of installation
|Reported by:||trodrigues||Owned by:||jacob|
|Severity:||Keywords:||documentation, mod_python, mod_wsgi|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
I'd like to suggest a change on the documentation which might be a source of confusion for some persons, and lead them the wrong way.
On the main installation guide (http://docs.djangoproject.com/en/dev/topics/install/#topics-install) the suggested method of installation is mod_python. However, once we click the link on "See How to use Django with mod_python for information on how to configure mod_python once you have it installed.", we're taken to the mod_python howto (http://docs.djangoproject.com/en/dev/howto/deployment/modpython/#howto-deployment-modpython) where we can see the following:
"The mod_python module for Apache can be used to deploy Django to a production server, although it has been mostly superseded by the simpler mod_wsgi deployment option."
And, on the mod_wsgi page (http://docs.djangoproject.com/en/dev/howto/deployment/modwsgi/#howto-deployment-modwsgi):
"Deploying Django with Apache and mod_wsgi is the recommended way to get Django into production."
Why aren't people led to the mod_wsgi page on the first place when accessing the main installation guide ?
Also, the main installation guide, takes people to a wiki page (http://code.djangoproject.com/wiki/ServerArrangements), when there are similar guides on the main documentation (at least for mod_wsgi and mod_python, I haven't checked others).
Change History (6)
Changed 7 years ago by timo
comment:1 Changed 7 years ago by timo
- Has patch set
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Accepted
comment:2 Changed 7 years ago by jacob
- Owner changed from nobody to jacob
- Status changed from new to assigned
comment:3 Changed 7 years ago by jacob
- Resolution set to fixed
- Status changed from assigned to closed