How to work for web.config with Subversion?

[Samnang]

Hi,

We would like to have a file that users will have on their machine
(web.config) that should be different than the master copy under source
control. Basically, that file specifies which database to connect to,
and users want to be able to connect to other databases. However, in
the "master" copy, we need to connect to a specific database every time.

I thought that using "svn:ignore" would do the trick, but it only works
for files. Also, in theory, that would make it difficult to actually
change the file if we wanted to.

Goals:
------
- Be able to simply get the source files and be able to run the system.
- Not prone to user error

Cheers,
Samnang

[RedSon]

Hi,

We would like to have a file that users will have on their machine
(web.config) that should be different than the master copy under source
control. Basically, that file specifies which database to connect to,
and users want to be able to connect to other databases. However, in
the "master" copy, we need to connect to a specific database every time.

I thought that using "svn:ignore" would do the trick, but it only works
for files. Also, in theory, that would make it difficult to actually
change the file if we wanted to.

Goals:
------
- Be able to simply get the source files and be able to run the system.
- Not prone to user error

Cheers,
Samnang

svn:ignore only works for files that are not already being versioned. Just tell you users to not commit changes to their local web.config copy, then each user can have a different web.config. It doesn't seem that difficult. If you don't want people to be able to touch the master web.config you can try locking it but since others can force open the lock, you can protect it using normal apache permissions.