Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We are planning to introduce version control for our servers team so we can keep our config files and code neat.
The server base are mostly Windows with some Linux and spread across several continents. Since the main purpose of the project is to take control ( no pun intended) over config scripts spread and keep configfiles neat.
I am wondering if there are some existing best practices for structuring the repository. Unfortunately my google-fu fails me here. Apologies if this has been asked here already.

I can start with two repositories : 'scripts' and 'config files' , then create subdirectories as I go. However I am convinced this has been done before many many times and I would rather not repeat mistakes of others. Are there any good rules for organising data in 'scripts' and 'config files' directories?

As for choice of the source control system , I am leaning towards distributed VC system ( git, mercurial) that already have built in resilience for multisite deployment. Some other options are important too, i.e: authentication using groups in multiple LDAP servers (i.e. AD domains) and nice Windows GUI client to please windows users.

share|improve this question

1 Answer 1

I think, you can start from exploring etckeeper (Keep Configs Under Control With Etckeeper on ServerWatch as QuickStart) and select SCM-backend (from supported), which have strong LDAP-abilities (I'm out of ideas here)

share|improve this answer
    
Thank for the suggestion but unfortunately this does not tick any boxes.is it distributed?is I cross platform? Does it come with the documentation with ideas on how how to structure my scripts and config? –  Sergei Apr 9 '13 at 10:54

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.