My backup strategy for dotfiles is to have a separate folder with the actual files (and back it up as a Github repo). Then I have an install script that adds symlinks in the right places. Right now I just specify the location for all files. But I'm probably gonna change so they are relative to the home dir. E.g., files in the backup/ go in ~/. Files in backup/.config/ go in ~/.config/.
The only tricky part is remembering to add it to the backup folder + make symlink when you get a new config file.
Though, I also have a huge mess with dotfiles that I don't know what they do or know whether I can remove, and I hate it. The output of your counting command was 52.
It can be an admin task when you use symlinks. I dont know if there is a truly simple and elegant solution. Atm I just backup my entire home directory. It is something I will look into later. Thanks for sharing!
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My backup strategy for dotfiles is to have a separate folder with the actual files (and back it up as a Github repo). Then I have an install script that adds symlinks in the right places. Right now I just specify the location for all files. But I'm probably gonna change so they are relative to the home dir. E.g., files in the
backup/go in~/. Files inbackup/.config/go in~/.config/.The only tricky part is remembering to add it to the backup folder + make symlink when you get a new config file.
Though, I also have a huge mess with dotfiles that I don't know what they do or know whether I can remove, and I hate it. The output of your counting command was 52.
It can be an admin task when you use symlinks. I dont know if there is a truly simple and elegant solution. Atm I just backup my entire home directory. It is something I will look into later. Thanks for sharing!