#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
-------------------------------------+-------------------------------------
Changes (by berkerpeksag):

 * cc: berker.peksag@… (added)
 * owner:  nobody => berkerpeksag
 * status:  new => assigned


Comment:

 I have a WIP patch for this ticket. Before open a pull request, I'd like
 to discuss structure of the runserver command.

 Current choices:

 1. Add a new "--gunicorn" option to runserver: ./manage.py runserver
 --gunicorn -c gunicorn_conf.py

 If the -c option is not given, use existing runserver options e.g.:

 ./manage.py runserver --gunicorn [--noreload] [optional port number, or
 ipaddr:port]

 2. Add a new "rungunicorn" command.

 Options:

 * -c conf.py
 * -b --bind
 * -w --workers
 * -l --logfile
 * --debug
 * --reload
 * probably other options from
 http://docs.gunicorn.org/en/latest/settings.html

 Use cases:

 * Use default options: ./manage.py rungunicorn (same as ./manage.py
 runserver)
 * Read config information from a file: ./manage.py rungunicorn -c conf.py
 (this is the configuration file used by Gunicorn)

 Thoughts?

 Thanks!

-- 
Ticket URL: <https://code.djangoproject.com/ticket/21978#comment:1>
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.4fd371f5cd7b9786b220bb056e126f6f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to