Table of Contents
This project contains two magical spells to encrypt and decrypt secret files in your repository, using Keybase to handle the private keys to sign and allow you to use the teams feature to distribute secrets in your work team.
You will need to have setup your keybase account and the keybase CLI installed. Read more
npm install --location=global @jparadasb/charms
Imagine you have all your secrets or env files ignored in your project
you should run
fidelius --user <keybase_username>
or
fidelius --team <keybase_teamname>
Now you will see the encrypted files which you are secure to commit.
- --force [By default, the command will skip the generated encrypted files. To regenerate it use this flag]
- --user [If you are using your own user to encrypt]
- --team [If you are using the name of a team to encrypt]
- --paterm [the pattern of the secrets files to encrypt. default: *.env]
Assuming you are cloning a repository and that you are already a member in (keybase) of the team in charge of that repository and you want to decrypt the secrets file there, you have to run:
revelio
Now you have the secrets files decrypted and can run your project without hesitate
- --force [By default, the command will skip the generated decrypted files. To regenerate it use this flag]
- --paterm [the pattern of the secrets files to encrypt. default: *.env]
Distributed under the MIT License. See LICENSE
for more information.