#8356 closed (fixed)
The documentation for mod_python should state the permissions or ownership settings of the project files
| Reported by: | anonymous | Owned by: | Jacob |
|---|---|---|---|
| Component: | Documentation | Version: | 0.96 |
| Severity: | Keywords: | apache, mod_python, ownership, permissions, django | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
http://www.djangoproject.com/documentation/0.96/modpython/
The docs should be explicit about the permissions that the apache user must have over the project source files. I think that the apache user should either have ownership or read and execute rights. (Can someone please clarify this?)
Thanks!
Change History (6)
comment:1 by , 15 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 15 years ago
| milestone: | → 1.1 |
|---|
comment:3 by , 15 years ago
comment:4 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:5 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
This has been fixed for a bit; the docs now read:
Make sure that your Python source files' permissions are set such that the Apache user (usually named apache or httpd on most systems) will have read access to the files.
(http://docs.djangoproject.com/en/dev/howto/deployment/modpython/#basic-configuration)
Note:
See TracTickets
for help on using tickets.
I believe all the apache needs is read access to the files, as long as the database isn't sqlite, or similarly file-based.