[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Using subversion to manage system config files

From: Paul Moore <pf_moore_at_yahoo.co.uk>
Date: 2004-06-21 21:41:20 CEST

I've just started to use Subversion to manage source code, and overall
I like the feel of it. However, a significant portion of my job is
managing configuration files (Apache httpd.conf, Oracle init.ora,
etc). I'd like to keep these files under some form of version control,
as well.

It's not immediately clear to me how, or if, I could use Subversion
for this. I can put (copies) of all the config files in a central
directory, and treat that as a working copy and put it under version
control. But I can't see a good way that I can automate the process of
ensuring that the "real" copies are in line with the latest revision
from Subversion. I suppose this is a similar sort of issue to that of
program releases, and hence somewhat outside the scope of Subversion.
But has anyone tried to manage this sort of data with Subversion, and
if so do you have any tips?

I guess that I could use a post-commit script, along with a per-file
property for the "release location" of the file, to copy any changed
files to their correct location on a commit. Maybe a second property,
to specify a command to run after a change (eg, restart Apache). And
maybe a pre-commit hook to confirm (somehow!) that the change is
authorised. Is this type of approach plausible?


This signature intentionally left blank
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 21 21:52:46 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.