#35450: Missing documentation: deploying Django in production behind a proxy.
-------------------------------------+-------------------------------------
Reporter: Klaas van Schelven | Owner: Wassef
Type: | Ben Ahmed
Cleanup/optimization | Status: closed
Component: Documentation | Version: 5.0
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Klaas van Schelven):
Despite being the original raiser of this issue, I do not have a strong
opinion about it, and I can largely follow the reasoning of keeping the
maintenance burden low etc.
A further 2c I'd like to add is that such a philosophy does seem to be
slightly at odds with the status quo, in which the docs do have various
(outdated?) articles on deployment.
--
Ticket URL: <https://code.djangoproject.com/ticket/35450#comment:10>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701906fd3441e-93b07460-1384-4ba1-b5a2-593e589aa537-000000%40eu-central-1.amazonses.com.
