Django shared hosting deployment documentation - chmod 755
|Reported by:||jeff_anode||Owned by:||jacob|
|Cc:||Triage Stage:||Design decision needed|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Having just managed to negotiate a tortuous install on my host using fastcgi, I think it might be useful to remind people that using server-spawned processes means that the user 'nobody' is going to be trying to execute your settings.py file (and maybe the rest as well).
What I'm getting at is that it might be useful to quickly let people know that they need to apply a chmod 755 to files such settings.py, otherwise the fcgi process will fail (usually without much useful information in the error log). I'm not an expert in this stuff and it took me a very long time to work out what the problem was.
The relevant section is on this page under the heading "Running Django on a shared-hosting provider with Apache"
Change History (7)
comment:1 Changed 8 years ago by jeff_anode
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Summary changed from Django shared hosting deployment documentation - chmod 755, python egg dir to Django shared hosting deployment documentation - chmod 755
comment:2 Changed 8 years ago by jacob
- milestone set to 1.1
- Triage Stage changed from Unreviewed to Accepted
comment:3 Changed 7 years ago by jacob
- Owner changed from nobody to jacob
- Status changed from new to assigned
comment:6 Changed 7 years ago by ubernostrum
- Resolution set to wontfix
- Status changed from assigned to closed