about summary refs log tree commit diff
path: root/secrets.json.secret (follow)
AgeCommit message (Collapse)AuthorFilesLines
2020-08-20 Prefer reading secrets.json to using pass showWilliam Carroll1-0/+0
I'm attempting to maintain a top-level secrets.json that defines all of the sensitive data that I'd like to version-control without exposing everything in cleartext to the world. To that end, I'm using `git secret`, which will use `gpg` to encrypt secrets.json everytime I call `git secret hide` and decrypt everytime I call `git secret reveal`. I'm going to try this until I don't like it anymore... if that day comes... I should write a blog post about my setup to solicit useful feedback and share my ideas with others.
2020-08-20 Testing git-secretWilliam Carroll1-0/+0
Adding a dummy, top-level secrets.json file using `git-secret`. It might be nice to have a mono-secrets file in json because then I can use it with `jq` like: ```shell $ jq '.secret' --join-output < ~/briefcase/secrets.json ```