#29570: Add check that MEDIA_URL is not inside STATIC_URL.
--------------------------------------+------------------------------------
     Reporter:  Alejandro Dubrovsky   |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  Core (System checks)  |                  Version:  master
     Severity:  Normal                |               Resolution:
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  1                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  1                     |                    UI/UX:  0
--------------------------------------+------------------------------------
Changes (by Carlton Gibson):

 * component:  Documentation => Core (System checks)
 * version:  2.0 => master
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 >  The documentation could also mention that adding an explicit url
 pattern for static and running python manage.py runserver --nostatic can
 be used as a workaround.

 The conclusion from #15199 was that having MEDIA_URL inside STATIC_URL
 (MEDIA_ROOT inside STATIC_ROOT?) is a pattern that we want to avoid, so I
 don't think documenting a workaround is consistent with that.

 Rather, strengthening the system check seems reasonable. (The patch checks
 media is not inside static. Is it worth doing the opposite too?)

 The MEDIA_ROOT docs already say:

 > MEDIA_ROOT and STATIC_ROOT must have different values. ...

 With the extra check this ''may'' be enough (I've always read it that way)
 but if an alternative phrasing that says "not inside each other too" that
 is both short and precise can be found then maybe we can update that as
 well.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29570#comment:1>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.cbb3c0b6b880e5704b9772e6cc3f8cd2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to