#18622: Django. The web framework for perfectionists who really don't care about
deployment.
-------------------------------------+-------------------------------------
Reporter: jonathan.hayward@… | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.2
Severity: Normal | Resolution: invalid
Keywords: Deployment | Triage Stage:
usability major | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* needs_docs: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
In my experience, deploying a Django site with mod_wsgi by following the
documentation (either Django's on mod_wsgi's) is a matter of minutes.
Since you didn't provide any information about what didn't work for you,
it's hard to convert your message into a bug in Django that we could fix.
It could be considered a feature request, but as you noticed, writing a
WSGI app server is outside the scope of Django. At least three modern and
solid solutions are commonly available (mod_wsgi, uwsgi, gunicorn). So the
answer to that feature request would be "wontfix".
I suggest you try our [TicketClosingReasons/UseSupportChannels support
channels].
PS: linking to LMGTFY, especially behind an URL shortener, is considered
offensive in this community. It reduces your chances of getting help to
zero. Avoid that kind of humor here.
--
Ticket URL: <https://code.djangoproject.com/ticket/18622#comment:1>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
