Skip to content

Latest commit

 

History

History
66 lines (45 loc) · 1.51 KB

README.md

File metadata and controls

66 lines (45 loc) · 1.51 KB

Build Status Dependency Status Coverage Status

Capistrano::Env

Capistrano with Env via file

Installation

Add this line to your application's Gemfile:

gem 'capistrano-env'

And then execute:

$ bundle

Or install it yourself as:

$ gem install capistrano-env

Usage

1. set env names in deploy.rb

in Capfile

require 'capistrano/env'

in deploy.rb

# New
set :capenv, ->(env) {
  env.add /^MYAPP_/
  env.add /^MYAPP_/ do |key|
     key.gsub /^MYAPP_/, '' # replace keyname like MYAPP_DATABASE_URL => DATABASE_URL
  end
  env.add 'UNICORN_PROCESSES'
  env.add 'HOGE', 'hage'
  env.filemode = 0644 #=> default is 0640.
}

2. deploy

bundle exec cap production deploy
  • automaticaly create #{current_path}/.env
  • automaticaly load #{current_path}/.env if you use dotenv-rails
    • you should load manualy in other framework
  • you can use ENV['ENV_NAME'] in application

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request