rezzza/vaultage

Keep secrets secret

Vaultage

Securize your files easily by defining a key on local machine. A passphrase can increase security., _(*1)

You'll be able to version files containing critical data., _(*2)

Fits well with automated deployment tools., _(*3)

Installation

wget --no-check-certificate https://github.com/rezzza/vaultage/raw/master/vaultage.phar, _(*4)

or, _(*5)

curl -O -sL https://github.com/rezzza/vaultage/raw/master/vaultage.phar, _(*6)

via composer, _(*7)

composer global require "rezzza/vaultage=~1.0", _(*8)

Vaultage binary path: ~/.composer/vendor/bin/vaultage, _(*9)

Commands

$ ./vaultage.phar init
$ ./vaultage.phar self-update

$ ./vaultage.phar encrypt
$ ./vaultage.phar encrypt --files=myfile.yml
$ ./vaultage.phar decrypt
$ ./vaultage.phar decrypt --files=myfile.yml.gpg

$ ./vaultage.phar diff --files=a.gpg,b.gpg
$ ./vaultage.phar diff --files=a.yml,a.gpg

Options

• configuration-file: define a specific configuration file (default is .vaultage.json).
• files: apply encryption or decryption on defined file(s), you can define many file by using comma separator.
• verbose: output the encrypted/decrypted data.
• write: write on the output file.

Crypto Backends

• Basic: packed by default, without any requirements.
• GPG: for serious guys ;)

Capifony integration

Just hook in the right place with this kind of recipe:, _(*10)

before "deploy:share_childs" do
    origin_file = "app/config/parameters/"+rails_env+".yml"
    system "vaultage decrypt --write"

    destination_file = latest_release + "/app/config/parameters.yml" # Notice the
    latest_release
    top.upload(origin_file, destination_file)
end