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
23705	mod_wsgi deployment documentation includes unncessary AliasMatch	Keryn Knight	Tim Graham	"[https://github.com/django/django/blob/1b2debe89684724f0617bb89aa49cb70273ab0f1/docs/howto/deployment/wsgi/modwsgi.txt#L136 This line in the docs] appears to be a remnant of the time before staticfiles:
{{{
AliasMatch ^/([^/]*\.css) /path/to/mysite.com/static/styles/$1
}}}
which as far as I understand it, is to allow domain-root-relative CSS files to be point through to staticfiles `collectstatic` output.
Off the top of my head, this seems like it would sidestep using `{% static ""file.css"" %}` (which would still work) and is not required in any sane/tidy configuration [and probably makes it harder to load those files in the dev server by virtue of needing another urlconf pattern].
It additionally has the burden of implying that `static/styles` exists, or is the only place CSS files could reside [the `static/styles` path is *only* mentioned in that AliasMatch]

It looks like the commit that introduced it was 9fd19c01611e5ed1ed64bbeb462ab96499d72a6c, in the 1.1 days. Two tickets have existed: #13912 and #11229, also both back in the pre-staticfiles days. It appears to have just been carried forward across renames accidentally, IMHO, and I can't think of a great reason for it being there."	Cleanup/optimization	closed	Documentation	dev	Normal	fixed		django@…	Ready for checkin	0	0	0	0	0	0