Code of Conduct
Package Information
whitenoise
Problem
I have found https://whitenoise.readthedocs.io to be an indispensable addition to any Django app that I launch -- at its core it sets the correct headers for static files so that browsers will compress/cache them correctly. It also leverages browser web standards to reduce the amount of load that hits a Django app -- paired with a CDN, it allows Django apps to scale and serve much more traffic.
Rationale
It seems like any web application that serves static assets, i.e. the majority of web apps, could benefit from these headers being set correctly. It would provide a better deployment story for Django. Including this in core means official Django tutorials can improve the guidance around "how to deploy Django apps".
Additional Details
- The repo has 2.7k stars on GitHub, so it seems pretty popular
- up to 300k downloads of the library from PyPI per day
Implementation Details
Personally, I am not convinced that all of whitenoise needs to be included in Django core. Maybe there is just some core functionality that makes sense to include, but the more fiddly bits can stay in whitenoise for devs who might need additional features?
Code of Conduct
Package Information
whitenoise
Problem
I have found https://whitenoise.readthedocs.io to be an indispensable addition to any Django app that I launch -- at its core it sets the correct headers for static files so that browsers will compress/cache them correctly. It also leverages browser web standards to reduce the amount of load that hits a Django app -- paired with a CDN, it allows Django apps to scale and serve much more traffic.
Rationale
It seems like any web application that serves static assets, i.e. the majority of web apps, could benefit from these headers being set correctly. It would provide a better deployment story for Django. Including this in core means official Django tutorials can improve the guidance around "how to deploy Django apps".
Additional Details
Implementation Details
Personally, I am not convinced that all of
whitenoiseneeds to be included in Django core. Maybe there is just some core functionality that makes sense to include, but the more fiddly bits can stay inwhitenoisefor devs who might need additional features?