4 ms·
Or make sure your secrets are transparently en/decrypted with GPG using: https://github.com/AGWA/git-crypt https://github.com/AGWA/git-crypt if you really have
by aequitas 8y ago
Or make sure your secrets are transparently en/decrypted with GPG using: https://github.com/AGWA/git-crypt https://github.com/AGWA/git-crypt if you really have to (and use https://rtyley.github.io/bfg-repo-cleaner/ https://rtyley.github.io/bfg-repo-cleaner/ to cleanup any history of commited secrets).
An .envrc file with https://pypi.org/project/keyring/#using-keyring https://pypi.org/project/keyring/#using-keyring also provides a nice solution for keeping secrets out of git for local development. Requires no central server, only your local key storage (eg: keychain for macOS).
- bbatha 8y ago> f you really have to (and use https://rtyley.github.io/bfg-repo-cleaner/ https://rtyley.github.io/bfg-repo-cleaner/ to cleanup any history of commited secrets). Don't bother. If you push a secret: Do not pass go. Do not collect $200. Just rotate your secrets and move on. If you push your repo you should treat the contents as public information.
- aequitas 8y agoCorrect, if you know it is public exposed. Our team had a private repo which we wanted to make open source inside our company without exposing the secrets stored there. In our case BFG saved us a lot of trouble and we could get this feature out quickly instead of postponing it while waiting to rotate all keys.