Here is some past work on "Minimize the risk of SECRET_KEY leaks" [0] that was never completed: https://github.com/django/django/pull/2714
[0] https://code.djangoproject.com/ticket/20081 On Monday, April 11, 2016 at 6:51:38 AM UTC-4, Josh Smeaton wrote: > > I kind of like the idea of making all settings configurable via the > environment by prefixing with DJANGO_SETTINGNAME. Sort of like how click > allows environment variables for options: > http://click.pocoo.org/5/options/#values-from-environment-variables. > Ideally configuring settings from the environment should be as transparent > as possible to the settings file, so that users aren't required to > os.getenv('NAME', 'default') all over the place to derive value. > > Django uses quite a few dicts and lists though, so consideration would > need to be made for those. Perhaps double underscores could represent keys > within a dict? > > DJANGO_CACHES__default__BACKEND='redis' > > For lists we could split on whitespace (again like Click): > > DJANGO_INSTALLED_APPS="contrib.admin contrib.auth". > > This does not address the type of the value though. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a334c7ec-5b60-43c9-8fe5-6d476e33debb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
