Django shared hosting deployment documentation - chmod 755
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"
http://docs.djangoproject.com/en/dev/howto/deployment/fastcgi/#howto-deployment-fastcgi
Change History
(7)
| Summary: |
Django shared hosting deployment documentation - chmod 755, python egg dir → Django shared hosting deployment documentation - chmod 755
|
| milestone: |
→ 1.1
|
| Triage Stage: |
Unreviewed → Accepted
|
| Owner: |
changed from nobody to Jacob
|
| Status: |
new → assigned
|
| Triage Stage: |
Accepted → Design decision needed
|
| Resolution: |
→ wontfix
|
| Status: |
assigned → closed
|
That depends on specific hoster config and on good hostings is unnecessary. Also note that this can be very dangerous as anyone will be able to read passwords and secret keys from settings.py