Florian, I was merely presenting a rhetorical question to illustrate a point. Perhaps there weren't other available web servers then, but there are now, as has been pointed out. Prevalence and expectation of TLS/SSL is another thing that's changed since 2005. We can choose to maintain runserver and keep it up to date with modern standards, abandon it, or leave it alone to effectively abandon it.
So far we've demonstrated that we have an interest in maintaining runserver supported by: - The existence of https://code.djangoproject.com/ticket/21978 - The fact that runserver has not been deprecated (nor are there any warnings of future deprecation) We also have demonstrated that we have no interest in maintaining runserver supported by the apparent direction of this discussion. I'm fine with either case, but therein lies the so-called identity crises and the origination of my confusion. As a developer using Django, I've long been directed toward runserver for development in the documentation yet it falls short of modern expectations. Which brings me back to my current, fundamental point. *We should update runserver or update the documentation to more clearly address modern, third-party alternatives and how to resolve them with desirable development features (e.g. serving static files from app directories).* I am willing to put in the work in any case, but I cannot do so without a decision and a ticket. At any rate, Gert, thank you for the gunicorn suggestion from Saturday. This meets my needs after some adjustment to my wsgi module (I needed to include my requisite sys.path modifications so I moved them from my passenger_wsgi module). Regards, Steven -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/349614b8-14c2-42a6-8d46-af0bb7dd3b66%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
