We use Paste Deploy configuration files [1] and we have a main/base configuration file under version control, which gets overridden with a non-versioned configuration file with holds all the sensitive information specific to that instance of the application.
This way, such information is not under version control and developers are free to use different credentials. It looks like this: ==== base-config.ini ==== [DEFAULT] debug = False django_settings_module = yourpackage.settings [app:main] DATABASE_ENGINE = postgresql_psycopg2 DATABASE_PORT = 5432 # ... many more settings ... ================= Then on the developer's machine: ==== custom-dev.ini ==== [app:main] use = config:/path/to/base-config.ini DATABASE_NAME = my_db DATABASE_USER = me DATABASE_PASSWORD = s3cr3t SECRET_KEY = this is not the actual secret key ================= Finally, on the server: ==== custom-deploy.ini ==== [app:main] use = config:/path/to/base-config.ini DATABASE_NAME = the_db DATABASE_USER = www-data DATABASE_PASSWORD = the secret SECRET_KEY = this IS the actual secret key =================== HTH, - Gustavo. [1] http://packages.python.org/twod.wsgi/manual/paste-factory.html On Mar 28, 9:50 pm, Guillermo <guillermo.lis...@googlemail.com> wrote: > Hi, > > I'm working on a project with multiple programmers for the first time, > and I'm not sure how I should go about commiting the Django project's > setting file to the public repo. Since it can contain sensitive data, > how's this done usually so everybody works with the same settings > during development? > > Cheers, > Guillermo -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
