I don't know. Can you propose a patch so we can see what's involved? How would a "production" web server (nginx, apache, etc.) handle the issue?
I'm more interested in moving runserver toward using gunicorn [0] (Windows support seems the main blocker to proceeding there) than adding more features to our own webserver, although it's not clear if the fix would actually involve the webserver. [0] https://code.djangoproject.com/ticket/21978 On Wednesday, March 1, 2017 at 6:52:48 PM UTC-5, is_null wrote: > > Sometimes it's not started because some modern orchestration tools such as > ansible-container and docker-compose (perhaps more) start everything at > once, and django might be faster than the db, or I have to fix something > with the db orchestration tool. > > I noted we might have the same issue with redis+channels (if I've not > waited long enough before taking action instead of waiting for channels to > retry). It seems like something reasonable to improve the development > experience with Django while keeping up with the orchestration tools > because I've heard about other users making tools in python on top of > docker-compose just to add the orchestration that their Django project > needed (I swear) already two years ago. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d2d72cc5-3b18-4d6e-bbed-833fdff02226%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
