Future i Information : Configuration in source control

Scope

We store config for apache, exim and bind in subversion, in the config repository. This is very much work in progress and I'd love to hear others' views on better ways to do it.

Quirks

There are some quirks that I'm trying to iron out:

Ownership: subversion doesn't know anything about the owner of a file, which causes us a problem for exim config where each domain is owned by the user responsbile for the domain
Permissions: when checking out, svn co creates files without honouring the umask, as ug=rwX,o=---, which exim complains about.

Checking out

Exim

# svn co file:///home/svn/config/trunk/youngs/exim /etc/exim
# chmod g-w /etc/exim/exim.conf

I haven't got a fix for the above file ownership problem yet

Apache

# svn co file:///home/svn/config/trunk/youngs/apache /etc/apache

Bind

# svn co file:///home/svn/config/trunk/youngs/bind /var/named/etc/bind

Policy

Please check in any changes of the above configs as soon as you've made a change. I'll be adding some kind of boot email soon to remind people to commit uncommitted changes.