limodou wrote: > On 8/7/06, Kevin Menard <[EMAIL PROTECTED]> wrote: >> On 8/7/06, Joe <[EMAIL PROTECTED]> wrote: >>> Wouldn't you want to put your database settings (Username and password) >>> in another file as well? >> I would be all for this. I never liked that the settings file >> contains both project-wide and user settings. Since it's >> project-wide, it gets added to the SCM. Since it contains user >> settings, users really shouldn't commit it back. I realize it's >> Python code and all that, but it seems to be a flaky default to me. >> > So I think secure data should be stored separately from project > settings. Maybe usename and password should be stored in separate file > also. But others don't need to do so. And if username and password > also be stored with secure key together, maybe the appoach what > Michael Radziej suggested need to be considered.
In reality, you will have multiple deployments: production, staging, development, demonstration, depending on your company's policy and what your project is about. For each of these you want to use different databases, might have different middlewares (e.g. for different logging levels, or you might want the CSFR middleware not with your development server), etc. I strongly disbelieve that any fixed scheme of storing some settings separately will cover everybody's needs. It's easy enough to code your own thing in your settings.py. Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
