Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

59 lines (38 sloc) 2.139 kB

capistrano-config

a capistrano recipe to manage configurations files.

Installation

Add this line to your application's Gemfile:

gem 'capistrano-config'

And then execute:

$ bundle

Or install it yourself as:

$ gem install capistrano-config

Usage

This recipes will try to update application config during Capistrano deploy tasks.

To enable this recipe, add following in your config/deploy.rb. The template of config/config.yml will be read from either ./config/templates/config/config.yml or ./config/templates/config/config.yml.erb by default.

# in "config/deploy.rb"
require 'capistrano-config'
set(:config_files, %w(config/config.yml))

Following options are available to manage your configuration files.

  • :config_update_remotely - specify whether update config files on remote machines or not. true by default.
  • :config_update_locally - specify whether update config files on local machines or not. false by default.
  • :config_path - specify configuration base directory on remote machines. use release_path by default.
  • :config_path_local - specify configuration base directory on local machine. use . by default.
  • :config_template_path - specify configuration template directory on local machine. use ./config/templates by default.
  • :config_files - specify list of configuration files in relative path. empty by default.
  • :config_readable_files - list of files which should be readable. empty by default.
  • :config_writable_files - list of files which should be writable. empty by default.
  • :config_executable_files - list of files which should be executable. empty by default.
  • :config_remove_files - list of files which should be removed. empty by default.

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

Author

License

MIT

Jump to Line
Something went wrong with that request. Please try again.