Environment variables will work with mod_wsgi about cookiecutter-django HOT 8 CLOSED

Full details here: https://gist.github.com/GrahamDumpleton/b380652b768e81a7f60c

The main issue appears to be that the default wsgi.py generated by Django is incomplete. So it's conceivable there may be an issue worth filing against Django as well, to add some hints about including environment variable configuration if desired.

from cookiecutter-django.

I think it would be better if @GrahamDumpleton opened the ticket. He's the subject matter expert for mod_wsgi. I would simply have to hand off the discussion of the topic immediately.

from cookiecutter-django.

Danny, Graham has already written up a detailed explanation of how to use
the WSGI launch file to set environment variables before launching the
Django application itself - that's in the gist I linked.

I don't care if you personally prefer not to use Apache, or mod_wsgi, or if
you just don't get on with Graham. I do care that your documentation is
currently actively misleading new users regarding mod_wsgi's capabilities,
which may lead them to unnecessarily rule out the use of the most widely
supported Linux web server ecosystem.

If you actually do want to steer your users away from Apache, that's also
fine (there are certainly many legitimate usability concerns with it - even
mod-wsgi express, which is now the easiest way to run development Python
services under Apache, requires the ability to build mod_wsgi locally), but
such guidance should be given explicitly on that basis, not implicitly
through inaccurate technical claims.

from cookiecutter-django.

@ncoghlan, First off, I think I get along grandly with @GrahamDumpleton. He's one of my favorite people in the python community, and it irks me that I haven't seen him since May of 2013. One of these days he needs to bring the family to Southern California so we can do Disneyland. 😄

As for the rest of your response, you are right. I'll get off my butt and file the issue with djangoproject.com,

from cookiecutter-django.

Thanks Danny - my apologies for getting a bit snarky. My irritation is
actually mostly with the Apache side of things, since it has suffered badly
from the open source community's historical lack of concern with usability
and approachability issues, and that's resulted in a lot of reinvented
wheels :P

from cookiecutter-django.

My apologies for not filing this on djangoproject.com. Last month was busy and a good chunk was spent off the grid. I'll try to submit this issue this week.

from cookiecutter-django.

Hi all!

I just marked the ticket @pydanny opened as needsinfo because it's not clear what action is being requested from Django. If anyone can help clarify that, the ticket is at https://code.djangoproject.com/ticket/24326 - feel free to reopen if you can provide some clarity.

I'm not entirely sure what @ncoghlan was referring to in terms of the default Django wsgi.py file being "incomplete", nor am I clear why @GrahamDumpleton 's gist recommends creating a new WSGI application file next to it, rather than editing the default one. The main issue I'm aware of where Django's default wsgi.py file interacts poorly with mod_wsgi is described in https://code.djangoproject.com/ticket/18518 (and related https://code.djangoproject.com/ticket/18559). This issue is already discussed in detail in our "hosting with mod_wsgi" docs: https://docs.djangoproject.com/en/1.7/howto/deployment/wsgi/modwsgi/

from cookiecutter-django.

Closing as it's being handled in Django itself, which is a more appropriate location for the discussion.

from cookiecutter-django.