Opened 17 years ago
Closed 17 years ago
#6798 closed (wontfix)
documentation should assume Apache
| Reported by: | aeu | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Its 2008, not 1995. Just make the documentation assume Apache + mod_python. Or at least add an alternate path through the documentation.
You're really, really, really, really not saving anyone any time by including a small webserver. If anything, you're making my startup time longer, because now I have to a) figure out Django, b) figure out how to pull your web server out of the loop and switch to Apache, meaning I'll have to go through the web server setup twice, which means less time writing python and more time messing around with web servers and their configuration.
Note:
See TracTickets
for help on using tickets.
The built-in server is quite handy for personal and offline development and it saves the new user from becoming an expert in deployment before running through their first tutorial. In addition to mod_python, FastCGI, SCGI, and AJP are also covered in the documentation. Many people are also deploying Django on NGINX, mod_wsgi, lighttpd and others. If anything the Django documentation needs to cover more deployment targets.