id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
32379	Documentation: hypercorn and static files	Sven R. Kunze	nobody	"Coming from the age-old problem of service static files, the usual process looks like this:

1) ✅develop and test using {{{ manage.py runserver }}} and everything just works fine
2) ✅ deploy code using WSGI or ASGI as described in the docs
3) ❌ find out that static files are missing

Specifically referring to https://docs.djangoproject.com/en/3.1/howto/deployment/asgi/hypercorn/

As there is a dedicated documentation page for hypercorn, it doesn't look like there's a need for thinking of serving static files.

A friend of mine suggested to use whitenoise: https://github.com/evansd/whitenoise

Would it make sense to integrate this into the Django docs?


To be transparent here, I started also different threads on different channels but it seems like nobody really wants to tackle this issue, so I thought addressing the issue at least via Django sounds reasonable because it's a Web framework:
here: https://softwarerecs.stackexchange.com/questions/77600/simple-and-secure-command-line-http-server
and there: https://gitlab.com/pgjones/hypercorn/-/issues/173
from another guy: https://gitlab.com/pgjones/hypercorn/-/issues/45

As of now, I addressed my real-world setup by setting up a ""mini""-nginx for now, serving static files and proxying hypercorn, but that does not feel like a holistic solution; also when it comes to automated deployment, permissions, principles such as ""test as you fly, fly as you test"" etc. it's a lot more brittle."	Uncategorized	closed	contrib.staticfiles	3.1	Normal	duplicate		Carlton Gibson	Unreviewed	0	0	0	0	0	0