How to store server configs in svn and roll them out?

1

1nd1go2012-01-26 17:28:08

System administration

1nd1go, 2012-01-26 17:28:08

Greetings!
There is such a problem. There is a server, Apache, Tomcat and applications are installed on it. Apache configs are extensive, in addition to httpd.conf there are sites.d / * .conf, Tomcat configs are understandably in another place and there are also a bunch of them.
In addition, two servers are test, and n more are in production. They differ slightly (in particular, the number of applications and the corresponding configs for them).
I would like to maintain all this junk in a controlled manner. Namely, to have a history of edits (svn comes to mind) and be able to roll it all out centrally, preferably in some kind of automatic mode.
I don’t have a good idea of how this process should look like, so I’ll keep my wishes to myself, but I really want to know how true admins do in this case?

Reply

Answer the question

In order to leave comments, you need to log in

6 answer(s)

E

ergil, 2012-01-26
@ergil

For the history of edits, see etckeeper, for this purpose it is quite.

M

m0ps, 2012-01-27
@m0ps

I advise you to take a closer look at puppet (chef/cfengine) + git.

C

cat_crash, 2012-01-26
@cat_crash

The most labor admins do Full Backup + daily backups to tapes.
SVN is not really the right solution for this sort of thing from the start. As a crutch - make a folder in which you add the necessary configs with symlinks.
Drive the folder itself into SVN

P

phasma, 2012-01-26
@phasma

svn has hooks.

V

Vlad Zhivotnev, 2012-01-26
@inkvizitor68sl

Roll out deb-packages, definitely.

I

IDDQD, 2012-01-26
@IDDQD

Try Apache Ant.