sig:sysadmin:projects:etckeeper
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
sig:sysadmin:projects:etckeeper [2016/02/15 17:31] walter ↷ Page moved from etckeeper to achive:etckeeper |
sig:sysadmin:projects:etckeeper [2016/02/15 20:41] walter ↷ Page moved from sigsysadmin:projects:etckeeper to sig_sysadmin:projects:etckeeper |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== EtcKeeper ====== | ====== EtcKeeper ====== | ||
| + | This system provides an easy way to push and pull a config from a repo. Most machines should be able to use a common etc repo. Evaluate a good organization strategy that takes role divergence into account. If the machine services will not remain the same then they should not be grouped. A good group to start with is the workstations. Under an etckeeper setup minor config updates can be pushed automatically to the machines without a full image clone and deploy. Admin access to Gitlab will likely be needed, try to use registered hooks and tokens instead of username/password combos for connecting to git. we should be able to have a common shared project without needed some kind of "local user" for auth. | ||
| ====== install stuff ====== | ====== install stuff ====== | ||
sig/sysadmin/projects/etckeeper.txt · Last modified: 2021/05/02 21:36 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
