#19680: "STATIC_ROOT" directory usage is unclear in "settings.py"
-------------------------------------+-------------------------------------
     Reporter:  retail79174@…        |                    Owner:  nobody
         Type:  Uncategorized        |                   Status:  closed
    Component:  Core (Management     |                  Version:  1.4
  commands)                          |               Resolution:  wontfix
     Severity:  Normal               |             Triage Stage:
     Keywords:  settings             |  Unreviewed
  collectstatic                      |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  1                    |
-------------------------------------+-------------------------------------

Comment (by aaugustin):

 Your comments will be read: there's a mailing-list where every comment is
 notified, with ~1000 subscribers, including myself :)

 ----

 By now I suppose you've read the
 [https://docs.djangoproject.com/en/dev/howto/static-files/#basic-usage
 basic usage guide for static files] and you've figured out how it works.

 You're far from being the first person to struggle with static files.
 That's mainly because the concept isn't trivial — it allows post
 processing and shipping static files in pluggable apps, which isn't
 possible with a standard serve-this-directory setup — but we can try to
 improve the situation with better docs. That's the topic of ticket #19582.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/19680#comment:4>
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 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 https://groups.google.com/groups/opt_out.


Reply via email to