On 12/18/06, atstake atstake <[EMAIL PROTECTED]> wrote: > > Not directly OpenBSD related but I thought I'd ask. I'd like to use > a revision control system to manage files on 25-30 > servers but I'm not sure whether I'd use a centralized repository or > have a separate revision control system on each box. It would also be good > to know how much leverage can a revision control system can give > over a "make-backup-before-change" policy in the long run and also > what files and directories should I add to it. Anything else anyone > would like to add from experience would be much appreciated.
Our (fairly small) organization uses our CVS repository like this in small ways. I really detest having everything in CVS for obvious reasons, but it can be useful in some situations. For example, redundant OpenBSD firewalls may share some configuration files for custom Snort rules. Update them in CVS, and use a shell script on the hosts to pull the updated configuration files via CVS+SSH. If multiple people are managing the rules, it is nice to see what people changed. Probably not so useful in the case of relatively static configuration files like pf.conf which shouldn't be modified much anyway. I wouldn't advise using it simply as a storage place in case you delete the local copy (that's what backups are for!), but you might find it useful serving identical configuration files to multiple hosts (as opposed to actual network file shares). Your comment about "make-backup-before-change" is somewhat frightening though :) If you don't have one already, you should set up a system that does daily+ backups, depending on how often things change. -- Kian Mohageri
