I want to store the configurations from a set of 50 servers deployed in the field. These configurations are like (/etc/my.cnf, /etc/httpd/conf/httpd.conf, etc..). Imagine that there are about 100 different files I want to keep track of (for each server). Also, imagine that there will be some changes in the configurations between servers (for some reasons, I cannot keep one version for all the servers).
I use bitbucket.org's account. I want to know the best way to organize the files..
A) As separate folders for each server in a single repository:
Like,
bitbucket.org/path/repository/server001/file1 to file100
bitbucket.org/path/repository/server002/file1 to file100
bitbucket.org/path/repository/server100/file1 to file100
Remember 'server001' and the likes are all folders. In server number 2, I don't need the folders of 'server001'. When I clone, I get all the folders in the repository (unless you teach me how to clone specific folders). As the servers increase, this increases complexity.
B) Each server as separate repository:
Like,
bitbucket.org/path/server-001-repository/folders_here
bitbucket.org/path/server-002-repository/folders_here
With this, I can retrieve files only from specific repository at a specific server.
C) Each server as a branch:
Like,
server-001 is a branch on one set of configuration files
server-002 is a branch on the same set of configuration files
I am yet to create all the repositories / folders / files.
Yours inputs will definitely help me.