about summary refs log tree commit diff
path: root/.gitsecret/paths/mapping.cfg
diff options
context:
space:
mode:
authorWilliam Carroll <wpcarro@gmail.com>2020-08-20T17·31+0100
committerWilliam Carroll <wpcarro@gmail.com>2020-08-20T17·31+0100
commit17c68d654ba7c4f01b730ceb804bdfa16c041174 (patch)
tree99984df70daf27730b2bf7cbbaf99c58e1e3e98f /.gitsecret/paths/mapping.cfg
parent392832a1ca492041bf9af4223b7049580e104bf3 (diff)
Prefer reading secrets.json to using pass show
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.
Diffstat (limited to '.gitsecret/paths/mapping.cfg')
-rw-r--r--.gitsecret/paths/mapping.cfg2
1 files changed, 1 insertions, 1 deletions
diff --git a/.gitsecret/paths/mapping.cfg b/.gitsecret/paths/mapping.cfg
index 2f89bb552ee8..fda2c84fb3d8 100644
--- a/.gitsecret/paths/mapping.cfg
+++ b/.gitsecret/paths/mapping.cfg
@@ -1 +1 @@
-secrets.json:9e05ae88de0df720ecc712b8e6bded3301bfd890cd13d0fb34d83bd37d14b594
+secrets.json:7d596a3ed16403040d89dd7e033a2af58e7aaabb6f246f44751b80a1863a2949