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

Re: REQ: using svn for sysadmin, best practice

From: Kalin KOZHUHAROV <kalin_at_thinrope.net>
Date: 2005-09-08 20:17:04 CEST

Rhesa Rozendaal wrote:
> Kalin KOZHUHAROV wrote:
>> Rhesa Rozendaal wrote:
>>> Since I have to manage a fair number of servers as part of my job,
>>> I'm contemplating storing config files and such in subversion as
>>> well. But I'm not sure what the best way is to go about this. Can you
>>> guys give me some pointers? Google only seems to serve up links to
>>> svn administration...
>> Keeping Your Life in Subversion
>> http://www.onlamp.com/pub/a/onlamp/2005/01/06/svn_homedir.html
>> Keeping $HOME (or /etc) in Subversion
>> http://toykeeper.net/tutorials/svnhome
> Thanks for those links! I've seen that first one once, but forgot about it.
>> I have pretty much run along those two articles and have a system about
>> 10 Gentoo boxen subversioned more or less completely.
>> Might write a page for that someday, but feel free to ask here.
> If I run into issues, I'll take you up on that :)
> I have a mixture of Fedora Core, Trustix and Debian boxes, so one
> question I'd like to ask right now is: do you keep repos per machine, or
> per "service" (i.e. what the box does)?

Well I tend to keep server related things per service.

Some configs for vsftpd, dhcpd, apache2, qmail, kernel-configs,
/var/supervise (for daemontools related scripts), courier-imap ...

Then I might have branches per host (branches/www13.tar.bz, branches/www.example.com, etc.)
and try to stay in sync at all branches and trunk.

My $HOME and /root is mostly in subversion as well.


|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 8 20:19:35 2005

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.