Improve WhiteNoise configuration #199
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
STATICFILES_STORAGEDjango config option toSTORAGESwhitenoise.runserver_nostatictoINSTALLED_APPSso that WhiteNoise's runserver implementation is used instead of Django's default implementation, for improved dev-prod parityWHITENOISE_KEEP_ONLY_HASHED_FILES, which means the original (un-hashed filename) copy of static assets are no longer unnecessarily stored in the slug. (This does mean all Django templates must use thestaticprocessor for asset URLs, but all of the templates in this guide do that already.)brotliWhiteNoise package extra, so that the Brotli package ends up being installed, so that static assets can also be served using the more efficient Brotli compression (for browsers that support it, which is all modern browsers), and not just GZip.See:
https://whitenoise.readthedocs.io/en/latest/django.html
GUS-W-13323144.