Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Synchronize Chef nodes w/ Capistrano and other config
branch: master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
bin
lib
spec Trim ec2 json output to just public hostname.
.gitignore
.rspec
Gemfile
Gemfile.lock Adds config file, role config, and version 0.0.4.
LICENSE
README.md
Rakefile Adds chef-sync implementation and tests.
chef-sync.gemspec

README.md

chef-sync

Synchronize Chef nodes w/ Capistrano and other config

Installation

Add this line to your application's Gemfile:

gem 'chef-sync'

And then execute:

$ bundle

Or install it yourself as:

$ gem install chef-sync

Usage

$> chef-sync
$ Target: /src/your_project
$ ----------------------------------------------------------
$ - Synchronizing Cap config/stages.yml w/ Chef Node Set
$ ----------------------------------------------------------
$ - production/app web ...
$ - production/resque ...
$ - qa/app web ...
$ - qa/resque ...
$ - staging/app web ...
$ - staging/resque ...
$ ----------------------------------------------------------
$ - Synchronizing config/mongo.yml w/ Chef Node Set
$ ----------------------------------------------------------
$ - qa...
$ - staging...
$ - production...

Custom Role Mapping

You can customize the mapping of Chef to Capistrano roles by generating a per-project chef-sync config file.

$> chef-sync -i
Target: /src/your_project
----------------------------------------------------------
- Generating default config /src/your_project/.chef-sync/config
----------------------------------------------------------
$> cat /src/your_project/.chef-sync/config
{
  "roles": {
    "rails_server": [
      "app",
      "web"
    ],
    "rails_utility": "resque"
  }
}

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request
Something went wrong with that request. Please try again.