#27929: Add an option when collecting statics to remove non-cached files after
processing
-----------------------------------------------+------------------------
Reporter: Jesse | Owner: nobody
Type: New feature | Status: new
Component: contrib.staticfiles | Version: 1.10
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------------+------------------------
When collecting statics with `CachedStaticFilesStorage` or
`ManifestStaticFilesStorage`, hashed versions of the files are created
along side the originals. The documentation
[https://docs.djangoproject.com/en/1.10/ref/contrib/staticfiles/#django.contrib.staticfiles.storage.ManifestStaticFilesStorage
specifically states that] this is intended to support any old links which
point to the original non-cached versions of the files. However, for a new
project, it's perfectly reasonable to not want to generate both sets of
static files once your project is being served on a production server.
--
Ticket URL: <https://code.djangoproject.com/ticket/27929>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.2d8c7ee606882bad40d6b401d773a8c6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
