On Sat, Aug 26, 2017 at 06:02:07AM -0700, ray wrote: > On Saturday, August 26, 2017 at 5:10:05 AM UTC-5, Dan Ritter wrote: > ... > > For a single system, etckeeper is an excellent choice. It stores > > changes anywhere in /etc (and optionally in other places) in > > git or subversion. > > > > You can go a little farther easily by learning git directly. > > https://try.github.io/levels/1/challenges/1 is a good resource. > > > > If you have multiple systems that need to be handled in similar > > ways, you want to learn an advanced configuration management > > system like chef, puppet, ansible, salt... > > > > -dsr- > > Dan, > > Thank you for the list of solutions. It is interesting that SVN can be used > with etckeeper. It looks like I should learn git. I have used SVN for other > things, but I am easily pulled from my comfort zone for value. > > There is an interesting challenge here on where/how to keep repositories on a > laptop. It is valuable to have them locally as often my problems are > networking; if the repositories are local, I can use another box to view > them, but sometimes it may be a challenge to move files when connectivity is > lost. I am sure there is an architecture that will be suitable.
Sure. git is distributed; you can easily check it out on another system, and thus have backups anytime you are connected to a network, while having a complete local record as well. > It seems like there may be value in using both a config mgr and a version control system. I will start checking into these to better understand. They are complementary solutions; config management solves "how to get things in the right shape" problems, and version control solves "what did this look like before?" problems. -dsr-
