#21978: Add optional gunicorn support to runserver
-------------------------------------+-------------------------------------
Reporter: timo | Owner:
Type: New feature | berkerpeksag
Component: Core (Management | Status: assigned
commands) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by berkerpeksag):
> I was thinking that if gunicorn is installed, then runserver would use
that automatically (passing data to --reload and --bind from the current
runserver options).
Ah, that is a good idea. Also, we can pass the `settings.DEBUG` setting to
Gunicorn's configration.
> Do you think that approach would be too limiting from a user
perspective?
No. I think that approach is a good start. It's a development server
afterall.
BTW, my WIP patch is at https://github.com/berkerpeksag/django/compare
/ticket-21978_gunicorn I will update it later.
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/21978#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.7b28fc0e5c016de066c58133a1131e51%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
