.env file in the same directory as your Capfile. Entries are automatically loaded as environment variables and can be accessed in Capistrano as
# .env GITHUB_TOKEN='foobar' # deploy.rb set :scm, 'git' set :branch, 'master' set :repo_url, 'https://github.com/rjocoleman/capistrano-env-config' set :git_http_username, ENV['GITHUB_TOKEN']
Also supports stages e.g.
.env files are loaded sequentially with the current stage first i.e.
.env.staging first and then
.env. If variables exist in both the stage and generic env file only the first is loaded (the stage) and not overwritten.
Compatible with Capistrano 3+ only.
Add this line to your application's Gemfile:
gem 'capistrano', '~> 3.1' gem 'capistrano-env-config'
And then execute:
$ bundle install
# Capfile require 'capistrano/env-config
- Fork it
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Add some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request