Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

ZenOps Chef Cookbooks

branch: master

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 .chef
Octocat-spinner-32 .vagrant add lab VM March 03, 2014
Octocat-spinner-32 bin fix empty string argument February 23, 2014
Octocat-spinner-32 ca
Octocat-spinner-32 config fix missing config in rake tasks February 23, 2014
Octocat-spinner-32 cookbooks ohai: improve plugins for ohai 7 April 11, 2014
Octocat-spinner-32 data_bags remove obsolete README February 23, 2014
Octocat-spinner-32 documentation
Octocat-spinner-32 environments
Octocat-spinner-32 nodes
Octocat-spinner-32 roles
Octocat-spinner-32 scripts
Octocat-spinner-32 site-cookbooks remove cookbook versions March 03, 2014
Octocat-spinner-32 tasks add changes from liquidm April 11, 2014
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .kitchen.yml fix loads of foodcritic issues December 27, 2013
Octocat-spinner-32 .ruby-version upgrade to ruby-2.1.0 January 12, 2014
Octocat-spinner-32 .tailor fix tons of tailor warnings December 25, 2013
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Gemfile.lock update for ohai 7 April 11, 2014
Octocat-spinner-32 cleanup February 23, 2014
Octocat-spinner-32 Rakefile
Octocat-spinner-32 Vagrantfile


Every Chef installation needs a Chef Repository. This is the place where cookbooks, roles, config files and other artifacts for managing systems with Chef will live. We strongly recommend storing this repository in a version control system such as Git and treat it like source code.


Please refer to the documentation.


  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.