Project

saucier

0.0
Repository is archived
No commit activity in last 3 years
No release in over 3 years
A Capistrano Extension that uses librarian and chef-solo to track your project cookbook dependencies. Use capistrano stages to quickly provision servers for your project. Version control your chef runlist, node configuration and cookbook dependencies.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 2.12.0
~> 0.9.2.2

Runtime

>= 2.0.0
 Project Readme

saucier

saucier is a Capistrano Extension that uses librarian and chef-solo to manage project dependencies and provision servers for your project.

Use Capistrano Multistage to manage your servers and environments.

Use with cap-strap to bootstrap new servers.

A sample project using saucier may be found

Installation

Add this line to your application's Gemfile:

gem 'saucier'

And then execute:

$ bundle

Usage

Make sure your project has a Cheffile with required chef cookbooks.

###Configuration:

  • set :user, "<user that will be executing chef-solo>" - default: "deploy"
  • set :group, "<group for deploy user. keep as rvm if using rvm>" - default: "rvm"
  • set :chef_deploy_to, "<set path for deploying chef-solo>" - default: "/etc/chef"
  • set :chef_ruby, "<ruby you'd like to run librarian and chef-solo>" - default: "default"
  • set :chef_gemset, "<gemset for chef>" - default: "global"
  • set :chef_solo_config, "<relative path to the chef solo config>" - default ".chef/solo.rb"
  • set :chef_node_config, "<relative path to your node config>" - default ".chef/node.json"

Testing

We're https://github.com/fnichol/minitest-capistrano for testing the capistrano configuration.

Running Tests:

  • rake test - manually run the tests
  • bundle exec guard start - Use guard to watch for changes and run tests automatically.

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