Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#19633 closed Bug (fixed)

Docs should discourage using gunicorn's Django integration

Reported by: aaugustin Owned by: nobody
Component: Documentation Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Since 1.4 introduced the new project layout, Django is a good WSGI citizen, and is best deployed as a WSGI app (gunicorn's default mode).

Quoting gunicorn's docs:

If you run Django 1.4 or newer, it’s highly recommended to simply run your application with the WSGI interface using the gunicorn command.

Django's docs should be updated to reflect this.

Attachments (1)

19633.diff (729 bytes) - added by timo 2 years ago.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 2 years ago by jezdez

Agreed.

comment:2 Changed 2 years ago by aaugustin

  • Triage Stage changed from Unreviewed to Accepted

Changed 2 years ago by timo

comment:3 Changed 2 years ago by timo

  • Has patch set

comment:4 Changed 2 years ago by Tim Graham <timograham@…>

  • Resolution set to fixed
  • Status changed from new to closed

In 0db86273ae1c31ee9881fe63f210cb2120fde18a:

Fixed #19633 - Discouraged use of gunicorn's Django integration.

comment:5 Changed 2 years ago by Tim Graham <timograham@…>

In 54887d686b1552ae98e3eb4fa57a64036eea72a5:

[1.5.x] Fixed #19633 - Discouraged use of gunicorn's Django integration.

Backport of 0db86273ae from master

comment:6 Changed 2 years ago by Tim Graham <timograham@…>

In 54887d686b1552ae98e3eb4fa57a64036eea72a5:

[1.5.x] Fixed #19633 - Discouraged use of gunicorn's Django integration.

Backport of 0db86273ae from master

Note: See TracTickets for help on using tickets.
Back to Top