You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've put together a script, git-dot that wraps git and git-crypt, allowing in-place dotfile management without symlinks that allows sensitive files to be encrypted.
I'm using it myself. It's had limited testing but just mentioning it in case anyone would like to try it. Feedback welcome.
@johnlane, in general, it's a terrible idea to allow secrets to be committed regardless of their encrypted state. I find the concept to be interesting, but implore anyone reading this to keep in mind that a lot of noobies use dotfiles to set up their environment, so any suggestion that it's OK to upload secrets is not a good one. It's a super cool concept, but I think putting it here might not be a good idea. Just be careful about this one, it seems like it could be teaching bad practices.
@Plazmaz sure there are issues with storing encrypted secrets in a vcs due to the fact that they are there forever, and I wouldn't recommend one makes such repos public. But in a private repo of a personal nature (which one's dotfiles typically would be) I'm not sure its such an issue.
Also I am not the first to do this and there are many other examples that do, such as yadm which is linked from the dotfiles front page. I don't think I am setting any precedent here :)
I might add some notes to my package about this though.
I've put together a script,
git-dot
that wrapsgit
andgit-crypt
, allowing in-place dotfile management without symlinks that allows sensitive files to be encrypted.I'm using it myself. It's had limited testing but just mentioning it in case anyone would like to try it. Feedback welcome.
http://git-dot.johnlane.ie
The text was updated successfully, but these errors were encountered: