#34712: Prevent misconfiguration of `STORAGES` setting
--------------------------------------+------------------------------------
Reporter: Bruno Alla | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.staticfiles | Version: 4.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Mariusz Felisiak):
* component: Documentation => contrib.staticfiles
* stage: Unreviewed => Accepted
Comment:
Documentation improvements are welcome.
> Another thing that could be maybe be added is a deployment check, to
make sure that both `default` and `staticfiles` storages are present in
the setting.
I agree that we could add a check for a `staticfiles` storage, e.g.
- `staticfiles.E005`: `You must define a 'staticfiles' storage in your
:setting:``STORAGES`` setting.` in the
`django.contrib.staticfiles.checks`.
However, as far as I'm aware, you don't have to use the `default` storage
so a new system check might be an issue for some projects.
--
Ticket URL: <https://code.djangoproject.com/ticket/34712#comment:2>
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/0107018961fac8f5-260c6337-ff0b-4723-83c6-30df1f74d82d-000000%40eu-central-1.amazonses.com.
