Opened 5 years ago
Closed 5 years ago
#30308 closed Uncategorized (wontfix)
Clarify in documentation that runserver is overridden for django.contrib.staticfiles
| Reported by: | David Beitey | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 2.2 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
In the main static files documentation, the serving process is generally explained that runserver will automatically serve files if DEBUG is set to true. This isn't quite the full story because it's not the _original_ runserver that is being used, and rather it's the one from django.contrib.staticfiles. This gets explained if you dig deeper, but it isn't clear what's happening before getting this deep.
PR at https://github.com/django/django/pull/11121
This PR makes a clarification to the wording of this section in the docs to explain how runserver is working its magic, and that if you have a custom runserver command (like I did), you need a special strategy.
Note:
See TracTickets
for help on using tickets.
Closing as per comment on PR. (Roughly: too much of an edge-case to be worth the complication, and advising the use of
collectstaticin development not the best way to go.)