howto version control server-specific config files?

I haven't seen a post directly on this, and I'm wondering if some of you
could share your strategies for doing the following:

Suppose I have a web application that I like to jar up into a .war file.
Now, this product relies on a property file that changes very specifically
to the server that the webapp is deployed on.

For example, let's say I have a 3rd party product that I can customize. I
have a license key specific to each installation of this application that
must contain the name of the server that the app is installed on.

This hypothetical file also contains lots and lots of other settings that
are not server-specific, and can and will be shared with other servers.

I'd like to keep as few copies of this file as possible. For instance, if
this file is called myserver_stuff.properties, I want to avoid things like
myserver_stuff.properties.server1 and myserver_stuff.properties.server2.

I'm especially interested in keeping all the non-server specific settings
in this file in sync between the copies that I must have. I also must
version control both the non-specific and server-specific settings.

Any thoughts on this? I have a process now but I think it sucks, so I'm
looking to improve it.

Thanks,

Ed.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 17 20:43:36 2005