Capistrano::SecretsYml

Capistrano tasks for handling secrets.yml when deploying Rails 4+ apps.

Add this to Gemfile:

group :development do
  gem 'capistrano', '~> 3.10.0'
  gem 'capistrano-secrets-yml', '~> 1.1.0'
end

And then:

$ bundle install

Make sure your local config/secrets.yml is not git tracked. It should be on the disk, but gitignored.
Populate production secrets in local config/secrets.yml:
```
  production:
    secret_key_base: d6ced...
```
Add to Capfile:
```
  require 'capistrano/secrets_yml'
```
Create secrets.yml file on the remote server by executing this task:
```
  $ bundle exec cap production setup
```

You can now proceed with other deployment tasks.

add it to local config/secrets.yml:

  production:
    secret_key_base: d6ced...
    foobar: some_other_secret

if you're working in a team where other people have the deploy rights, compare you local secrets.yml with the one on the server. This is to ensure you didn't miss an update.
copy to the server:

if you only need to update secrets.yml
```
  $ bundle exec cap production secrets_yml:setup
```
or if other Capistrano plugins need to be setup
```
  $ bundle exec cap production setup
```
notify your colleagues that have the deploy rights that the remote secrets.yml has been updated so they can change their copy.

When you execute $ bundle exec production setup:

secrets from your local secrets.yml are copied to the servers in your config/deploy/{environment}.rb files using the user: value. a.
only "stage" secrets are copied: if you are deploying to production, only production secrets are copied there
on the server secrets file is located in #{shared_path}/config/secrets.yml

On deployment:

None.

Check out capistrano-plugins github org.

capistrano-secrets-yml