Why another static file combiner for Django?¶
Short version: None of them did exactly what I needed.
- JS/CSS belong in the templates
- Every static combiner for Django I’ve seen makes you configure
your static files in your
settings.py. While that works, it doesn’t make sense. Static files are for display. And it’s not even an option if your settings are in completely different repositories and use different deploy processes from the templates that depend on them.
- Django Compressor doesn’t care if different pages use different combinations of statics. It doesn’t care if you use inline scripts or styles. It doesn’t get in the way.
- Automatic regeneration and cache-foreverable generated output
- Statics are never stale and browsers can be told to cache the output forever.
- Full test suite
- I has one.
- Common Deployment Scenarios
- Remote storages
- Behind the scenes
- Jinja2 In-Request Support
- Jinja2 Offline Compression Support
- django-sekizai Support