#21581: collecstatic --clear is too lax about warning users
-------------------------------------+------------------------------------
     Reporter:  loic84               |                    Owner:  loic84
         Type:  Bug                  |                   Status:  closed
    Component:  contrib.staticfiles  |                  Version:  master
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+------------------------------------

Comment (by loic84):

 @marfire I can relate to your story since this happened to me on a staging
 server. I was quite grateful that my fabric task performed a `cd` to the
 project folder and didn't execute `/srv/project/manage.py` from my user
 directory!

 The tricky part is that since [3f1c7b70537330435e2ec2fca9550f7b7fa4372e],
 `STATIC_ROOT` isn't present in the `settings.py` shipped by the default
 template, so it's a lot easier to forget setting it to a meaningful value,
 which in turn exposes to this bug.

 Hopefully we'll be able to release 1.6.2 soon enough so we can forget
 about this bug.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/21581#comment:11>
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/064.e8c7e67b03c653cf1227510c44dfa522%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to