Just open up the “Issues” tab and see if they have any bugs that may make using the tool for you cumbersome or straight up unbearable. One tip I can give you here is to check those projects’ issues on github. I just feel like managing dotfiles with git bare repo is very straightforward and clean solution and I don’t want to rely on a tool other than git.īut if you feel like giving one of those tools a go, go ahead, they must not be bad as so many people are using them. There are dotfiles manager, such as chezmoi, dotbot, yadm, and some others. This is solvable, but in not a very straightforward way. This means, I’d like to commit the whole ~/.vim, but a single file into my git repo. Like I’m storing an intelephense lincence key in ~/.vim/coc-user-config.vim. Not only that, but some of your files may contain lincence keys. Some of those may contain sensitive data, or expose structural information about company’s infrastructure. Let’s say you are working for a company and you have company-specific configs, or scripts sitting in your ~/.scripts/ or something like that. Good luck with that if you are using symlinked dotfiles. And the reason for this is sometimes the contents of the directory may partially be not for the public access. Sometimes you want to have the whole directory in your github repo, but sometimes you want all the files but 1, or 2… or many. This method has a significant drawback though which comes with managing what can go and what can not go under the version control inside directories.
0 Comments
Leave a Reply. |