Hi all,

     I prefer simple solutions, so raw git is better when I don't need 
any extra stuff like automagic commit, push etc...

Other way, is git good solution for maintenance /etc on test->prod env?
Using e.g branches for test changes and deploy those info production
environment?

---
Best regards (Pozdrawiam),
Jakub Juszczakiewicz
Krypto-IT

-------- Wiadomość oryginalna --------
Temat: Re: [DNG] Off topic: way for /etc
Data: 2024-06-18 13:36
Od: Olaf Meeuwissen <paddy-hack@???>
Do: Jakub Juszczakiewicz <jakub.juszczakiewicz@???>
Kopia: dng@???

Hi,

Jakub Juszczakiewicz via Dng <dng@???> writes:

> [[PGP Signed Part:Undecided]]
> Hi all,
>

>    Small off topic: are you using git for /etc maintenance as local
>    git repository? Are you this is that good way for make it easiest?

As already mentioned by others, there is etckeeper which can be used to
track much of /etc. I use it on almost all my systems as a way to find
out what I changed manually *and* what changed during upgrades. The
latter is especially useful if you follow the testing/unstable suite and
you end up with unexpected behaviour or breakage after an upgrade.

etckeeper includes lists of the upgrades packages in the commit message.

Recently I've been playing with git sparse-checkout to selectively track
parts of my $HOME directory. So far I like it and am inclined to give
it a try on / too ;-o

Hope this helps,
--
Olaf Meeuwissen