Code

Opened 6 years ago

Closed 3 years ago

#7721 closed (invalid)

Mention DocumentRoot in Apache deployment docs

Reported by: gregglind Owned by: nobody
Component: Documentation Version: master
Severity: Keywords: deployment
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

I understand that this may be my foolishness or oversight, but I was missing a DocumentRoot directive in my apache virtualhost config, causing 404 errors when I was looking in the /media directory. Maybe a slightly expanded discussion about how django handles django's urls, and apache handles things (in its normal way) when setHandler none is in effect would have helped me debug the error. I was spending time on the wrong path of MEDIA_ROOT, MEDIA_URL and the like.

Continue to be excellent!

Gregg L.

Attachments (0)

Change History (3)

comment:1 Changed 6 years ago by serialx

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

Good point. I've had problems with DocumentRoot too.

comment:2 Changed 4 years ago by gabrielhurley

  • Keywords deployment added
  • Summary changed from Perhaps mention DocumentRoot? to Mention DocumentRoot in Apache deployment docs

comment:3 Changed 3 years ago by vanschelven

  • Resolution set to invalid
  • Status changed from new to closed

The recommended way of deploying Django on Apache, i.e.

http://docs.djangoproject.com/en/dev/howto/deployment/modwsgi/

explains exactly how to serve static files if you choose to use Apache (rather than a separate server) for this purpose. DocumentRoot is not required for this.

I'm not sure if this was ever a valid complaint (my guess is it was) but time seems to have healed this particular wound. Marking as invalid.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.