Improve docs about handling static files without django.contrib.staticfiles.
|Reported by:||loic84||Owned by:||nobody|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Following discussion on IRC with @apollo13 and @ubernostrum.
Since django.contrib.staticfiles is optional, we should document how to serve STATIC_URL without it during development; the docs for serving MEDIA_URL [ 1 ] may be used as a template.
Some parts of the docs need to be reviewed; for example "Note that the Django development server automatically serves the static files of the admin app (and any other installed apps)" [ 2 ] is actually only true if django.contrib.staticfiles is installed.
It might be helpful to warn that MEDIA_URL and STATIC_URL must have different values, the same applies to MEDIA_ROOT and STATIC_ROOT. This is mostly an issue because historically (pre-contrib.staticfiles) a lot of projects were using MEDIA_ROOT/MEDIA_URL to serve static files.
Change History (4)
comment:1 Changed 3 years ago by timo
- Easy pickings unset
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Accepted
- Type changed from Uncategorized to Cleanup/optimization
comment:3 Changed 3 years ago by Tim Graham <timograham@…>
- Resolution set to fixed
- Status changed from new to closed