4 ms·

I am a (happy) user of homeshick (https://github.com/andsens/homeshick https://github.com/andsens/homeshick), but this project really seems to top it by providi

by kiesel 8y ago

I am a (happy) user of homeshick (https://github.com/andsens/homeshick https://github.com/andsens/homeshick), but this project really seems to top it by providing the only feature that I've missed until now: - use the same source file with different results for different machines (eg. .gitconfig for home and office machines) - option to store secrets in a credentials database and extract them from there (because you wouldn't want to store them in a git repo - even if it's a private one) I'll definitively give it a try! (EDIT: formatting)

explainplease 8y ago
Homeshick is indeed great, been using it for years. Every time I've compared it to other solutions, it always comes out on top feature-wise. The other solutions are always missing something, like tracking either files and/or entire directories. Tracking whole directories is very important for e.g. storing an entire ~/.emacs.d in git, and tracking individual files is nice so I can just `homeshick track main ~/.config/some-config-file` without tracking all of ~/.config. > - use the same source file with different results for different machines (eg. .gitconfig for home and office machines) I do that by storing each machine's copy with its hostname as a suffix and symlinking it into place on each machine. e.g. ~/.config/anacrontab.systemA gets symlinked to ~/.config/anacrontab on systemA, and the repo contains both ~/.config/anacrontab.systemA and ~/.config/anacrontab.systemB. I can even modify one machine's file from the other machine, and it will be updated on the next push/pull. But having integrated support for this would be nice.