Opened 7 years ago

Closed 5 years ago

Last modified 4 years ago

#9641 closed (wontfix)

Django shared hosting deployment documentation - chmod 755

Reported by: jeff_anode Owned by: jacob
Component: Documentation Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

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

Change History (7)

comment:1 Changed 7 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 6 years ago by jacob

  • milestone set to 1.1
  • Triage Stage changed from Unreviewed to Accepted

comment:3 Changed 6 years ago by jacob

  • Owner changed from nobody to jacob
  • Status changed from new to assigned

comment:4 Changed 6 years ago by dc

  • Triage 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

comment:5 Changed 6 years ago by adrian

  • milestone changed from 1.1 to 1.2

comment:6 Changed 5 years ago by ubernostrum

  • Resolution set to wontfix
  • Status changed from assigned to closed

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

comment:7 Changed 4 years ago by jacob

  • milestone 1.2 deleted

Milestone 1.2 deleted

Note: See TracTickets for help on using tickets.
Back to Top