Opened 13 years ago
Closed 11 years ago
#17709 closed Cleanup/optimization (needsinfo)
Include info on DocumentRoot in Apache setup doc
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Documentation | Version: | 1.3 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
In the Django Book, DocumentRoot is at least mentioned in describing the process for serving files from the static and media directories via Apache. This is a pretty important caveat and should really be on the doc page for How To Use Django with Apache and mod_wsgi. (https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/modwsgi/)
Change History (4)
comment:1 by , 13 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 13 years ago
If this ticket really only applied to mod_python
I'd have no trouble wontfixing it right now. However, I note that that the mod_wsgi page also includes Apache configuration samples for serving static assets, and that that example doesn't include DocumentRoot
either, and it seems like it probably ought to.
comment:3 by , 13 years ago
Description: | modified (diff) |
---|
I modified the description to redirect the fix to the Apache + WSGI docs.
comment:4 by , 11 years ago
Resolution: | → needsinfo |
---|---|
Status: | new → closed |
I don't know of a case where DocumentRoot
is required to serve static assets under mod_wsgi. If there is one, please re-open with details.
This is a valid suggestion.
However, mod_python is deprecated and will be removed in version 1.5; so this ticket will be closed as "wontfix" in one month.