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).
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.
When running
./manage.py runserver --noasgiI don't get static files served.This is because both
daphneanddjango.contrib.staticfilesprovides arunserverreplacement. Running daphne's runserver with--noasgijust 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.