#30308: Clarify in documentation that runserver is overridden for
django.contrib.staticfiles
-----------------------------------------+------------------------
Reporter: davidjb | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 2.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
In the main [https://docs.djangoproject.com/en/dev/howto/static-files
/#serving-static-files-during-development 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
[https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles/#runserver
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/30308>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.60c2dce957a19bc3af57dac65ed0f0bb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
