Sometimes, when a topic comes up over and over, it means something is wrong. Maybe not the original decision; it could be the documentation, or the perception of the user base, or whatever. I understand the need to not revisit old decision ad nauseum, but Carl has an interesting point: whoever put that "don't share it" comment in the original settings.py file put in on a single setting, not the entire file. This hints at a distinction in the author's mind. Maybe our understanding of settings has moved on since then, or maybe we need to honor that distinction in some way.
And some settings are important for the functioning of the application (for example, the list of middleware). Changes made there have to be propagated somehow to all deployments. In the real world, a single non-shared settings file simply doesn't work well. Here's a modest proposal: at the top of the generated settings file, include this comment along these lines: # This file contains settings which should be kept secret. # For ideas on how to manage complex settings files, # see: http://code.djangoproject.com/wiki/SplitSettings --Ned. Malcolm Tredinnick wrote: > On Thu, 2007-11-01 at 23:02 -0500, Carl Karsten wrote: > [...] > >> Support for the local_settings file is there, I just think it should be >> changed >> from an "If it exists" to assuming it exists, and seed it with the values >> that >> have been singled out as "secret." >> > > This is one of those cases where searching the archives will reveal that > we've already had this conversation a few times previously. Each time > the decision has been that the current very simple, single file setup > isn't going to change because it doesn't need a change. That is your > settings file. Don't distribute it. There's one file you shouldn't > distribute. > > If you want something more complicated for your own setups, you are free > to do so. That's the other thing we've repeated over and over: it's a > Python file, so feel free to use the full power of the language as you > wish. > > Because of those two results -- it's hardly a snap decision and you have > full flexibility for doing whatever you want -- this really isn't a > decision we need to revisit. Let's move on. > > Thanks, > Malcolm > > -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
