WhiteNoise สำหรับไฟล์สแตติก

In production Django will not serve your CSS and JS for you. Normally you need Nginx or a CDN, which adds setup. WhiteNoise simplifies this. 📦

WhiteNoise lets your Django app serve its own static files efficiently, so a simple Gunicorn-only deploy can ship CSS and JS too.

On platforms like Heroku or small containers where there is no separate web server for files, WhiteNoise keeps everything in one process.

Add the package with pip, then pin it in requirements.txt so your deploys stay reproducible. WhiteNoise needs no extra services.

Insert the WhiteNoiseMiddleware right after SecurityMiddleware. Order matters, since it intercepts static requests early in the chain.

Point STATICFILES_STORAGE at WhiteNoise to enable compression and cache-friendly hashed filenames automatically.

WhiteNoise serves whatever collectstatic gathers, so STATIC_ROOT must point to the folder where those files land.

Before serving, run collectstatic to copy every app's assets into STATIC_ROOT. WhiteNoise reads from that single folder.

The compressed storage backend pre-builds gzip and brotli versions of your files, so browsers download smaller, faster assets.

WhiteNoise adds a content hash to each filename and sets long cache headers, so browsers safely reuse files until they truly change.

WhiteNoise wins on simplicity, but a dedicated Nginx or CDN is faster at huge scale. Pick based on your traffic and hosting setup.

Where do you register WhiteNoise in your project?

You enabled WhiteNoise: install it, add the middleware, set compressed storage, run collectstatic, and your app serves cached static files itself. 🎯