#35450: Missing documentation: deploying Django in production behind a proxy.
-------------------------------------+-------------------------------------
Reporter: Klaas van Schelven | Owner: Wassef
Type: | Ben Ahmed
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 5.0
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
-------------------------------------+-------------------------------------
Comment (by Wassef Ben Ahmed):
I wrote a small guide to a bare minimum production deployment of Django on
a VPS.
It covers most things needed from pointing a domain to an IP address to
generating self-signed certs.
should I try removing any Django-unrelated parts and push it as a PR?
If so: any suggestions on parts that shouldn't be included? or
recommendation on what to focus on?
Link to guide: https://dev.to/wassef911/deploying-django-in-production-b1p
also related ticket https://code.djangoproject.com/ticket/35451
---
closes thing I found online, is:
https://www.digitalocean.com/community/tutorials/how-to-set-up-django-
with-postgres-nginx-and-gunicorn-on-ubuntu
although it's not really focusing on making the deployment a "production"
but to just get things running...
--
Ticket URL: <https://code.djangoproject.com/ticket/35450#comment:3>
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/0107019046e666aa-58886d8f-01d9-495e-b2ae-6e334414dd7b-000000%40eu-central-1.amazonses.com.
