On 11/7/22 09:06, Óscar García Amor wrote:
El dom, 6 nov 2022 a las 23:35, Joel (<j-archlinux@joel-hatsch.net>) escribió:
> On 11/2/22 14:23, ente wrote:

> Hi,

Hi again!

> many [..] of doing ?

My advice is that not all dotfiles are candidates for synchronization. Many of them are only interesting on a particular machine.

What I do is to have a .dot directory with the configurations I am interested in keeping on all machines and "sync" that directory in git. This allows you to have a good versioning of those configuration files and work only with those that can be ported from one machine to another.

You can take a look at it here: https://github.com/ogarcia/dot
The instructions to deploy it are in the repository wiki: https://github.com/ogarcia/dot/wiki. Basically what it does is to put this script as post-commit (so that if you make changes in the repository it will be executed) and run it. What this script does is to create symbolic links from your home to the .dot files with the same name (for example the .dot bashrc file is linked from your home as ~/.bashrc). This way you can have everything you need in the .dot directory without it being scattered all over your home.

Hi Oscar, Anthony,

that's a great idea !

At least for the dot*files* it should do the trick perfectly. For the dot*dirs* it could work for the ones with small amount of files and changes. And for the others with much more content, as Oscar said, not all are candidates for sync, so the amount could still be handled by setting up dedicated sync targets in syncthing (eg .ssh, .gnupg, .aqbanking etc)

Thanks again for the good hints