tickets: 21978
This data as json
id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
21978 | 2014-02-07 20:46:15 | 2018-08-09 23:50:51 | 2022-03-06 04:17:53.760821 | Accepted | assigned | Core (Management commands) | New feature | Normal | dev | Add optional gunicorn support to runserver | gunicorn has added a [https://github.com/benoitc/gunicorn/pull/682 --reload option for code reloading] which should lower the barrier of entry to removing our own HTTP server functionality. Simply deprecating and removing the `runserver` management command entirely may not be desirable. As Loic noted on IRC "even if we use gunicorn, we still need some special handling for the dev server, we run validate() and now there are some migrations checks going as well. So would we really deprecate runserver? rather than just change the underlying webserver it wraps?" Michael Manfre also expressed concern the gunicorn does not currently work on Windows. Aymeric suggested: "optional support for gunicorn could be an interesting start." | berkerpeksag | timo | 0 | 1 | 1 | 0 | 0 | 0 |