Originally Posted by NotionCommotion
I know there are fancy server management packages available, but I don't think I am ready for one.
Instead, I am thinking of just tracking configuration files with Git. My thoughts are to track everything in /etc/. Good idea? Any other folders which I should consider? I will probably do a fresh install, and do my first commit. Then maybe another commit directly after installing a major application (i.e. after installing Apache, then after installing MySQL, etc).
Please provide any comments and/or advice.
Sounds a bit dangerous, but probably depends on how you plan to use it. Say you commit after installing package xy. Then you realize the installation broke something. What then?
What I am getting at: If you now just revert to the previous commit all you will achieve is getting /etc back to the preinstallation state. What if other directories were changed during the install? What if the regular repair procedure would require the /etc to actually be in the state it was left in by the installation?
I have broken stuff in my system several times by installing packages. More often than not just uninstalling these packages and reinstalling packages that were removed during install repaired everything. You may not have this option anymore if you confuse your system by manually reverting /etc.
Long story short: I think this is a bad idea except if you only want to use git in order to track changes that you made to config files yourself manually, and be able to view older versions of such config files... I might be missing something though...