Opened 16 years ago
Closed 14 years ago
#8711 closed (wontfix)
Add documentation about deploying Django under SCGI and AJP
Reported by: | vizualbod | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | deployment | |
Cc: | Triage Stage: | Someday/Maybe | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
- This document primarily focuses on FastCGI. Other protocols, such as SCGI and AJP, are also supported, through the flup Python package.
- Before you can start using FastCGI with Django, you’ll need to install flup.
Do I need flup for FastCGI or is it just needed to use SCGI and AJP? The first note needs reformulate.
It would be also good to add a few notes about Django + CherryPy WSGI server + Nginx as a proxy.
I can provide some materials for this if there is interest as I find it a rock solid setup better than mod_python.
Frantisek Malina, http://vizualbod.com
Change History (3)
comment:1 by , 16 years ago
Summary: | /documentation/fastcgi/ → Add documentation about deploying Django under SCGI and AJP |
---|---|
Triage Stage: | Unreviewed → Someday/Maybe |
comment:2 by , 14 years ago
Keywords: | deployment added |
---|
comment:3 by , 14 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
It suddenly strikes me that requesting a guide for a specific deployment strategy is much like requesting a translation, and Jacob's answer would be every bit as true if he were talking about the local dialect rather than server technologies.
Thereby it seems reasonable to hold a similar policy: tickets should be opened when a deployment guide is provided, not when one is requested (see Russ' succinct answer on #13286).
I'm not sure we need to exhastively document deploying Django in all the various ways it could be done, but if someone writes a SCGI, AJP, or whatever doc there's no reason not to include it.