Django

Code

Ticket #9641 (closed: wontfix)

Opened 1 year ago

Last modified 2 weeks ago

Django shared hosting deployment documentation - chmod 755

Reported by: jeff_anode Assigned to: jacob
Milestone: 1.2 Component: Documentation
Version: 1.0 Keywords:
Cc: Triage Stage: Design decision needed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

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

Attachments

Change History

11/19/08 22:58:25 changed by jeff_anode

  • needs_better_patch changed.
  • summary changed from Django shared hosting deployment documentation - chmod 755, python egg dir to Django shared hosting deployment documentation - chmod 755.
  • needs_tests changed.
  • needs_docs changed.

02/26/09 16:56:36 changed by jacob

  • stage changed from Unreviewed to Accepted.
  • milestone set to 1.1.

04/02/09 13:44:22 changed by jacob

  • owner changed from nobody to jacob.
  • status changed from new to assigned.

04/28/09 09:23:28 changed by dc

  • stage changed from Accepted to Design decision needed.

they need to apply a chmod 755 to files such settings.py

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

05/06/09 03:38:37 changed by adrian

  • milestone changed from 1.1 to 1.2.

03/03/10 02:21:16 changed by ubernostrum

  • status changed from assigned to closed.
  • resolution set to wontfix.

Going to wontfix this, since recommending a "chmod 755" is always the wrong thing to do.

Add/Change #9641 (Django shared hosting deployment documentation - chmod 755)




Change Properties
Action