Question

I am working on a SVN controlled project that I had checkout from server at the beginning.

In one of the SVN controlled directory, there is a configuration file (settings.py) which I had to edit to suit my local setup.

I have created a local backup of my own configuration file. In order not to update this file to server, I always revert “settings.py” before committing to the server. After committing, I move my own “settings.py” from my local backup.

I will appreciate if somebody can guide me how to exclude this file from SVN without any side effects; so that I don’t have to revert and recopy by hand.

Answer 1

A common way to do this is to store an example file such as settings.py.template in source control, but not settings.py. That way, you can change settings.py as needed locally, without Subversion prompting you to commit it.

When you make a new checkout, you would copy settings.py.template to settings.py to get things started. If you make any changes that affect the default configuration file, change settings.py.template and commit the change.