#16161: Warn that extra static files shouldn't be added directly into
STATIC_ROOT
-------------------------------------+-------------------------------------
Reporter: gnotaras | Owner: nobody
Type: | Status: new
Cleanup/optimization | Component: Documentation
Milestone: | Severity: Normal
Version: 1.3 | Keywords:
Resolution: | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Comment (by gnotaras):
Replying to [comment:2 aaugustin]:
> You shouldn't put some extra static files in `STATIC_ROOT`.
So, what you say is that the transformation of a file to a symlink to
itself is expected behavior from a software. What if I didn't have a
backup of that file? I think this issue requires more clarification before
changing the subject and the ticket type.
Why would putting extra files in STATIC_ROOT manually be a problem? These
extra files are still files required for proper display of the web site,
like a custom logo or a custom image map and the place they belong to is
STATIC_ROOT.
Suppose that STATIC_URL points to a separate domain dedicated to serving
web site media. Why shouldn't I be able to put the logo or a custom CSS
file in there? Where would be the right place to put the custom logo?
The change of the summary line is unacceptable as it practically buries
the reported issue. Please change it back to the original.
--
Ticket URL: <https://code.djangoproject.com/ticket/16161#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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
