Given that, what about incorporating something like DJ-Database-URL[1] into Django? It would be great if this could be the default if DATABASES was left unspecified.
[1] https://github.com/kennethreitz/dj-database-url Le mercredi 25 septembre 2013 19:45:20 UTC-4, Russell Keith-Magee a écrit : > > > On Thu, Sep 26, 2013 at 4:21 AM, VernonCole <verno...@gmail.com<javascript:> > > wrote: > >> I find myself using up lots of time and keystrokes explaining about the >> benefits and methods of a structured settings module in django. >> For example: >> Using-a-Structured-Settings-environment<https://github.com/modilabs/formhub/wiki/Using-a-Structured-Settings-environment> >> >> It occurs to me that life would be easier if django shipped already set >> up for structured settings, rather than having to retro-fit it. The pull >> request I sent to formhub could be a starting point for the conversion. ( >> formhub/pull/1240) <https://github.com/modilabs/formhub/pull/1240> The >> changes to core are simple enough that I could do it. >> >> Your opinions please, Would such a change be good for django 1.7? >> > > Based on conversations that I had at the sprints at DjangoCon US, I'd say > probably not -- because the winds are blowing in another direction. > > The primary reason to need structured settings like this is because your > development environment is different to your deployment environment (e.g., > different passwords, paths and so on). > > However, the emerging best practice for this sort of thing is best > described by the "12 factor" approach: > > http://12factor.net > > Factors 10 and 3 are the most relevant to this discussion -- 10 says that > development and production should be the same; 3 says that anything that > needs to vary should be set as an environment variable, and consumed from > there. > > So - I'd expect to see Django moving towards better support for a 12 > factor environment, rather than embedding separate settings files as a > deployment practice. > > Yours, > Russ Magee %-) > > -- You received this message because you are subscribed to the Google Groups "Django developers" 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 http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
