You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running ./manage.py runserver --noasgi I don't get static files served.
This is because both daphne and django.contrib.staticfiles provides a runserver replacement. Running daphne's runserver with --noasgi just cause the real runserver to be used, giving no chance to the staticfiles runserver.
I don't know if there's an elegant solution here, maybe shadowing commands are not a good idea (I don't blame daphne, staticfiles does the same :D).
When running
./manage.py runserver --noasgi
I don't get static files served.This is because both
daphne
anddjango.contrib.staticfiles
provides arunserver
replacement. Running daphne's runserver with--noasgi
just cause the real runserver to be used, giving no chance to the staticfiles runserver.I don't know if there's an elegant solution here, maybe shadowing commands are not a good idea (I don't blame daphne, staticfiles does the same :D).
Maybe the elegant solution is to link from https://docs.djangoproject.com/en/5.0/howto/deployment/asgi/daphne/ to https://docs.djangoproject.com/en/5.0/ref/contrib/staticfiles/#django.contrib.staticfiles.views.serve for easy finding?
Running Django 5.0.6 with daphne 4.1.2 on Debian Trixie.
The text was updated successfully, but these errors were encountered: