Skip to content

Make Heroku and transcrypt (elasticdog/transcrypt) play nicely with each other.

License

Notifications You must be signed in to change notification settings

perplexes/heroku-buildpack-transcrypt

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

36 Commits
 
 
 
 
 
 

Repository files navigation

heroku-buildpack-transcrypt

Decrypt your transcrypt-encrypted files on deploy.

Best practices

Rails now has a secrets.yml, which is actually some ERB that can grab variables out of your ENV. Setting environment variables on Heroku is the recommended way for passing secrets.

However in some situations you need to put secrets into app.json like if you're driving deploys via API. This is a good file to encrypt.

Other good files to encrypt are SSL certificates, and API keys that libraries use that you can't modify to use environment variables.

Usage

Assuming you have a repo that you had set up with transcrypt and encrypted some files...

heroku config:set TRANSCRYPT_CMD="$(transcrypt -d | grep "transcrypt -c" | sed 's/^  //')"
heroku buildpacks:add --index 1 https://github.com/perplexes/heroku-buildpack-transcrypt

<3

About

Make Heroku and transcrypt (elasticdog/transcrypt) play nicely with each other.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages