Opened 5 months ago

Closed 3 months ago

#35451 closed Cleanup/optimization (wontfix)

Documentation: Gunicorn deployment should probably mention the usage of a proxy

Reported by: Klaas van Schelven Owned by: Wassef Ben Ahmed
Component: Documentation Version: 5.0
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The current documentation for deploying using gunicorn(which happens to be the top entry in the list of deployment options) does not mention using gunicorn should probably be installed behind a proxy, even though this is the very first thing the gunicorn deployment documentation itself says. Since not putting a proxy in front is insecure, this is probably good advice to add.

Given that various specific settings are required (#35450) when setting up a proxy, it would be nice to refer those from the same page.

Change History (5)

comment:1 by Sarah Boyce, 5 months ago

Component: UncategorizedDocumentation
Triage Stage: UnreviewedAccepted
Type: UncategorizedCleanup/optimization

Happy to review improvements here 👍

comment:2 by Wassef Ben Ahmed, 4 months ago

Owner: changed from nobody to Wassef Ben Ahmed
Status: newassigned

comment:3 by Wassef Ben Ahmed, 3 months ago

Has patch: set

comment:4 by Sarah Boyce, 3 months ago

Has patch: unset

Please either link the PR or make sure the PR title has the prefix "Fixed #35451 --" so that it will be linked automatically when you set "Has patch" to "Yes"

comment:5 by Sarah Boyce, 3 months ago

Resolution: wontfix
Status: assignedclosed

To reduce the maintenance burden, the Django docs avoid stating duplicate information that is available in official linked docs/sources and is not Django specific.
As the advice of deploying gunicorn behind a proxy is the very first thing it says, this also means this is not difficult to find. Hence there is little value in having this repeated in the Django how to.

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