#15199: Allow MEDIA_ROOT inside STATIC_ROOT
------------------------------------------------------+---------------------
Reporter: brutasse | Owner:
Status: closed | Milestone: 1.3
Component: django.contrib.staticfiles | Version: SVN
Resolution: wontfix | Keywords: blocker
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 |
------------------------------------------------------+---------------------
Changes (by carljm):
* status: new => closed
* resolution: => wontfix
Comment:
After further IRC discussion with jezdez, closing this wontfix. Supporting
a configuration with MEDIA_ROOT inside STATIC_ROOT introduces a number of
additional complexities and couplings between staticfiles and the MEDIA_*
settings, which we are trying to avoid, and it's not clear what meaningful
benefits it buys us. The main mentioned benefit was to only require one
alias on the front-end webserver: that seems minor, since an alias is e.g.
just one line in an nginx conf file. In any case, the same result can be
achieved by putting MEDIA_ROOT and STATIC_ROOT side by side in a parent
directory, and aliasing the front-end webserver to that parent directory.
--
Ticket URL: <http://code.djangoproject.com/ticket/15199#comment:5>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
