Constraints, Environment Variables, Apache/mod_wsgi about cookiecutter-django HOT 4 CLOSED

@schacki Alas, there are no workarounds for this issue, and it's one reason (of several) why we used to lean so heavily on the local_settings.py anti-pattern. While Apache does have environment variables (http://httpd.apache.org/docs/2.2/env.html), they don't serve the same purpose.

In Two Scoops of Django 1.6 we address the issue via the use of a secrets file in json, config, yaml, etc formats, rather than an unversioned python module.

Are we happy about this? Heck no. We wish we could provide a fix for this, but that's beyond our capacity: Apache, as far as I know, just works this way.

Pitching this downstream, what might be interesting is if a package like @jezdez's django-configurations could enhanced to support loading a secrets module. That would be interesting to see, but perhaps out of scope for his project.

Speaking of scope, because this is possibly in the domain of django-configurations, and definitely in the domain of Apache itself, I'm closing this as an issue. If a downstream solution emerges that almost/nearly seamlessly works with this project, I'll be happy to incorporate it in.

from cookiecutter-django.

Just for reference: opened a ticket with django-configuraitons: jazzband/django-configurations#53

from cookiecutter-django.

Thanks for raising this issue, Apache with mod_wsgi is indeed still important enough to consider fixing this by documenting workarounds.

@pydanny I think it's reasonable to think about a contrib package inside of configurations that has extended features like an improved version of the SecretValue class (http://django-configurations.readthedocs.org/en/latest/values/#configurations.values.SecretValue). E.g. a KeyringValue that uses the keyring library for secure cross-platform data storage (https://pypi.python.org/pypi/keyring/3.5).

from cookiecutter-django.

I commented in the configurations issue as well, btw.

from cookiecutter-django.