Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I want to place the config files of all my servers under version control using subversion. I have maybe 100 servers and was wondering if anyone else had done this?
What is the best way of structuring the repository? The servers will share some files '/etc/hosts' for instance but other files will differ. Should I configure a repo for each server? or place all config files in one repo and then distribute them with puppet?
I'm thinking that these files are all text and further that they're not revised like source or libraries, however you may have scripts which are unique per server. I'd tar/zip up all relevant files on a per server basis and then name the resultant output file "per server", "per date archived", and then add those resultant files to your sccs; I'd probably use one repository reserved for the server configurations to keep it separate from other controlled sources.
I would suggest that there are three main options as I see it:
1) Prefix all files before adding them with the server name for all files that are duplicated
2) Use a different sub-directory for each server
3) Use a different repository
1) Needs you to remember to make a copy before adding, a pain of you forget one day.
2) (I have not tried, so YMMV) If you use a unique named directory on each server, copy the file in, then commit it. May need to get all files when reverting, but not a big issue.
3) is the easiest as you can just place updated files straight in.
Just some suggestions. I would tend to 3), possibly 2) myself, but that is only because I would be likely to forget to get it right, and would add things wrongly
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.