On 11/01/2015 14:25, Rich Freeman wrote: > On Sun, Jan 11, 2015 at 3:22 AM, Alan McKinnon <alan.mckin...@gmail.com> > wrote: >> The reason I'm recommending to keep all of /etc in it's own repo is that >> it's the simplest way to do it. /etc/ is a large mixture of >> ansible-controlled files, sysadmin-controlled files, and other arbitrary >> files installed by the package manager. It's also not very big, around >> 10M or so typically. So you *could* manually add to a repo every file >> you change manually, but that is error-prone and easy to forget. Simpler >> to just commit everything in /etc which gives you an independant record >> of all changes over time. Have you ever dealt with a compliance auditor? >> An independant change record that is separate from the CM itself is a >> feature that those fellows really like a lot. > > If you're taking care of individual long-lived hosts this probably > isn't a bad idea.
Yes, this is what I do. I do have cattle, not pets. But my cattle are long-production dairy cows, not beef steers for slaughter. And I have a stud bull or two :-) > If you just build a new host anytime you do updates and destroy the > old one then obviously a git repo in /etc won't get you far. -- Alan McKinnon alan.mckin...@gmail.com
