#27590: Allow configuration of where to save staticfiles manifest.
-------------------------------------+-------------------------------------
Reporter: David Sanders | Owner: Jarosław
Type: | Wygoda
Cleanup/optimization | Status: assigned
Component: contrib.staticfiles | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Kevin Christopher Henry):
If we take a step back, the problem here isn't that there's no way to
configure the manifest location, it's that the standard location for it is
bad. That's the reason people want to change it. So rather than making it
''possible'' for people to avoid the problem by introducing a new
customization mechanism, we should just fix the standard value so that no
one has the problem in the first place.
If we accept that the default manifest location needs to change at some
point then there will inevitably be a backwards incompatibility.
One way to address that would be to just document in the release notes
that people using `ManifestStaticFilesStorage` need to run `collectstatic`
after upgrading. If they don't do that they will immediately see a helpful
error message at startup since the manifest won't be found, and they can
fix the problem then. Still, perhaps that's overly burdensome, I'm not
sure.
Another approach would be to have a deprecation cycle where `STATIC_ROOT`
continues to be checked if the manifest isn't found at the designated
location in the code base, showing a deprecation warning in that case.
--
Ticket URL: <https://code.djangoproject.com/ticket/27590#comment:12>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.9b040782c89ced1f123edc33d0378929%40djangoproject.com.
