RE: Dealing with Server Configuration

 
We're doing something similar here.

First of all, we have to be careful that each config file does not have
sensitive information in it (this is a harsh environment from a security
perspective). Some files will even have passwords in plaintext in them!

Secondly, we're aliasing all our boxes so that there is no specific IP
address, but we do have to deal with the alias having to change
(proj-dev-web talks to proj-dev-db, but test-web talks to test-db) - what
would be nice would be if there was a way to promote the file and have the
specific string "proj-dev" replaced with "proj-test" and then "proj-prod"
for those specific files.

Thankfully, however, we are finding that in practice, there are not many
configuration changes made to our 10-server 3-environment setup. So, we keep
the configurations in different branches of the repository, as you are
thinking about. I.e., project/config/dev/web and project/config/test/web
(below this, we replicate the full path to the file so that it can be copied
back to the server easily in an emergency). This does mean that we have to
disseminate any config changes ourselves, but at least it can be done
centrally.

HOWEVER, I am not 100% sure this is the best approach, and would be in how
others are solving this problem.

Cheers,

          :D

--------------------------------------------------------------------
Daragh Fitzpatrick Daragh@UChicago.edu (773) 702-8976

Solutions Architect NSIT Administrative Systems
Renewal Projects and Architecture University of Chicago
--------------------------------------------------------------------
-----Original Message-----
From: Chris Jensen [mailto:cjensen@edex.com.au]
Sent: Tuesday, June 01, 2004 9:06 PM
To: Subversion Users
Subject: Dealing with Server Configuration

Hi,
We're implementing version control here for the first time with subversion.
And I'm wondering if anyone can suggest ways of dealing with server specific
configuration files.
In our case we have the developers desktops, a development server, and a
  production server.
In some projects we have a file that stores configuration settings specific
to that server (eg IP addresses, file paths, etc)

What's the best way to deal with such files? At the moment I'm finding that
I'm continually accidentally commiting the version that I use on my dekstop
and then deploying that to the development server accidentally.

I was thinking of simply putting the file in its own directory and pointing
that directory on the different machines to different branches.
Has anyone got a better solution?

--
---------------------------------------------------------------------
Chris Jensen cjensen@edex.com.au
Educational Experience (Australia)
Postal Address: PO Box 860, Newcastle NSW 2300
Freecall:       1-800-025 270      International: +61-2-4923 8222
Fax:            (02) 4942 1991     International: +61-2-4942 1991
Visit our online Toy store! http://www.toysandmore.com.au/
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org