Timeline for Using git to manage /etc?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 26, 2017 at 21:18 | answer | added | user26053 | timeline score: 12 | |
| Aug 3, 2014 at 17:34 | vote | accept | peterh | ||
| Aug 3, 2014 at 13:06 | answer | added | Volker Siegel | timeline score: 13 | |
| Jun 25, 2014 at 19:54 | comment | added | try-catch-finally | What files are you interested in or what files have been changed unwanted in the past? I ask because I think Git is not the right way to solve problems caused at another point in your workflow. Further: if someone forgets to commit multiple changes Git is worthless. Could you please explain your environment? Do you have test and QA envrionments identical to production? Do you have much more than two or three hosts of the same type/purpose or is it heterogenous? What is more important: compare hosts configurations or track one hosts config over time? | |
| Jun 25, 2014 at 17:16 | history | edited | Raphael Ahrens | CC BY-SA 3.0 |
improved the format
|
| Jun 25, 2014 at 16:48 | history | tweeted | twitter.com/#!/StackUnix/status/481841260270211072 | ||
| Jun 23, 2014 at 8:39 | comment | added | jofel |
There is etckeeper which is already used on many systems. It does not offer all features you asked for. E.g. it has one repository per host, not a central one.
|
|
| Jun 23, 2014 at 8:30 | history | asked | peterh | CC BY-SA 3.0 |