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
We are exploring the following options, but want to know if anyone has a
better idea how to do it with Subversion:
1. Have another file called "Release.config" that gets renamed to
"Web.config" during the build process. Only release.config would be
under source control. Users would have a local web.config that they can
edit as they please. The only problem is that users would have to copy
release.config to get their local system running.
2. Change web.config locally, but don't check it in. The problem is
that people will accidently check it in.
You are all awesome.
Thanks,
Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 14 20:45:26 2005