Handles bootstrapping, running chef solo, rsyncing cookbooks etc

Run minitest suites after your Chef recipes to check the status of your system.

Provides a CLI tool for generating knife commands to build Chef-managed infrastructure from a simple JSON or YAML file.

An orchestrator for Chef

A CLI for managing Chef Environments using Berkshelf and the Environment Cookbook Pattern.

`Meez` (slang for `mise en place`) will create an opinionated chef cookbook skeleton complete with testing suite including: berkshelf, chefspec, test kitchen, foodcritic, server spec

Makes all the stuff usually you or your DevOps does before first deploy

A Chef cookbook for managing the Monit process manager.

Builderator automates many of the common steps required to build VMs and images with Chef. It provides a common configuration layer for Chef, Berkshelf, Vagrant, and Packer, and tasks to orchestrate the usage of each. https://github.com/rapid7/builderator

Utilities for working with OpsWorks apps in the style of Artsy Engineering.

Vendor everything. Stay sane.

Extenstions for berkshelf

A Berkshelf plugin that adds support for downloading Chef cookbooks from Mercurial (hg) locations.

Chef-Berksfile-Env ================== A Chef plugin which allows you to lock down your Chef Environment's cookbook versions with a Berksfile. This is effectively the same as doing `berks apply ...` but via `knife environment from file ...`. View the [Change Log](https://github.com/bbaugher/chef-berksfile-env/blob/master/CHANGELOG.md) to see what has changed. Installation ------------ /opt/chef/embedded/bin/gem install chef-berksfile-env Usage ----- In your chef repo create a Berksfile next to your Chef environment file like this, chef-repo/environments/[ENV_NAME]/Berksfile This is the default location that will used by the plugin. We have to put the Berksfile in its own directory since [multiple Berksfiles can't exist in the same directory](https://github.com/berkshelf/berkshelf/issues/1247). The berksfile should include any cookbooks that your nodes or roles explicitly mention for that environment, source "https://supermarket.getchef.com" cookbook "java" cookbook "yum", "~> 2.0" ... Next we need to generate our Berksfile's lock file, berks install Your environment file must by in `.rb` format and look like this, require 'chef-berksfile-env' # The name must be defined first so we can use it to find the Berksfile name "my_env" # Load Berksfile locked dependencies as my environment's cookbook version contraints load_berksfile ... Now our environment will use the locked versions of the cookbooks and transitive dependencies generated by our Berksfile. Upgrading to the latest dependecies is now as simple as, berks install Our Berksfile also provides an easy way to ensure all the cookbooks and their versions that our environment requires are uploaded to our chef-server, berks upload How the Plugin Finds the Berksfile ---------------------------------- If you are curious how the plugin knows to find the Berksfile in `chef-repo/environments/[ENV]/Berksfile`, you want to put your Berksfile somewhere else or you have run into this error `Expected Berksfile at [/path/../Berksfile] but does not exist`, this section will explain how this works and ways to tweak the path or fix your error. `load_berksfile` has an optional argument which represents the path to your Berksfile. This path can be pseduo relative (explained in a moment) or absolute. By default the value is `environments/[ENV_NAME]/Berksfile`. By pseduo relative I mean that its a relative path but the plugin will check to see if the directory we are executing from partially matches our relative path. So if we are running knife from `/home/chef-repo/environments` and our relative path is `chef-repo/environments/dev/Berksfile` the plugin will see that the relative path is partially included in our execution directory and will attempt to merge the two to come up with `/home/chef-repo/environments/dev/Berksfile`. If we can't make any match at all we attempt to guess the path by just joining the relative path with our execution directory. So why do we do this? Well the only way to use this plugin is if your environment is in Ruby format. Chef's `knife from file ...` uses Ruby's `instance_eval` in order to do this. This means the code on Chef's end effectively looks like this, env.instance_eval(IO.read(env_ruby_file)) which means that any context about the location of the environment file is lost. So we have no great way to discern the location of our environment Ruby file, so instead we guess.

Ruby gem for managing a chef stack. Primarily targetted towards rails stacks and is designed to be easy to use like Heroku CLI

This gem checks if updated versions of dependent cookbooks are available for the cookbook

Provides versioning and promotion logic for chef artifacts.

Configures and installs docker to Hetzner server in\ default bootstrap mode, yet has some server management\ modes like rescue mode, CentOS and CoreOS installation

A collection of scripts useful for monitoring servers and services with Instrumental (instrumentalapp.com)

Plugin for test-kitchen that extends the chef_zero provisioner allowing berkshelf to use cookbook restrictions loaded from chef environment files. This way, Berkshelf will always vendor the cookbook versions specified in the chef environment.