On 12 April 2016 at 05:35, Martin Owens <docto...@gmail.com> wrote: > There is a difference between settings intended by developers to be used by > other developers /../ And settings used by systems administrators to define > the environment they are deployed to as well as any deployment specific > controls. > > Django has always mixed the two into one file, and it causes problems. I've > seen keys and passwords committed to github, extravagant json or os.env > based solutions with piles of lines of messy code to what I see most which > is a local_settings.py with a template version which is copied in at runtime > with sane defaults.
I used to use extravagant json messes[*] but have (on non-PaaS) switched to having a directory /etc/django-sites.d, which is on the python path, containing one python package per site on that host: /etc/django-sites.d/MyProjectConf/sitetype.py MyProject.settings.sitetype is referenced by wsgi-scripts. It first star-imports MyProject.settings.base, then star-imports MyProjectConf.sitetype inside a try/except. That way I can have have important overrides/option-merging for a sitetype in version control, and still have puppet/chef/ansible/whatever control deploy-and-site-specific options without touching anything inside the source tree. > I'd be happy to see a canonical decision made for django, but I'd focus on > "who should be editing this setting" not just what it's for, if it's a > secret or if it should be different or the same per instance. A tag in the settings-docs would be a good start, or a check list of more site dependent settings. Hey, the docs are restructured text; the tag could generate an extra index, et voila :) -- HM [*] I *know* why json doesn't survive that spurious comma at the end of a list/dict, but I like me that comma so much that I no longer use json for hand-written config in new stuff. -- 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/CACQ%3Drrd3GyFgpxkCJkNegnk62EmR1VzVvS5OToeV6Prns4qWeA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
