monkeys

Sharing a profile

A project's secrets travel as one encrypted file: pack on one machine, unpack on the other. The file is safe to send over whatever you already use; the…

A project's secrets travel as one encrypted file: pack on one machine, unpack on the other. The file is safe to send over whatever you already use; the passphrase goes another way.

On the machine that has the secrets, inside the checkout:

monkeys pack --only @test
Passphrase:
Again:
wrote /tmp/a.monsecrets: +foo @test, 2 secrets

Send that file. On the other machine, anywhere inside their checkout:

monkeys unpack ~/Downloads/a.monsecrets
Passphrase:
wrote .monkeys: +foo @test, 2 keys
stored foo.test/DATABASE_URL, foo.test/STRIPE_SECRET_KEY
removed /Users/them/Downloads/a.monsecrets

Their vault now holds the secrets under the same profile, and monkeys run ./hello.sh works for them the way it works for you. When they cloned the repository, the .monkeys file was already there, and unpack leaves it as it was, adding only keys it does not list.