Inspiration for this gem was taken from meez. It creates an opinionated cookbook complete with testing suites.

Once cabinet has finished running, you will have a new cookbook complete with an initialized git repo, chefspec, serverspec, test-kitchen, guard (with notifications via inotify/fsevent/terminal-notifier), rubocop, foodcritic, berkshelf, and stove.

It will automatically create a Gemfile for you with different groups set up for development, testing, etc:

source 'https://rubygems.org'

gem 'berkshelf', '~> 2.0', '>= 2.0.14'
gem 'chef', '~> 11.8', '>= 11.8.0'

group :unit do
  gem 'foodcritic',       '~> 3', '>= 3.0.0'
  gem 'rubocop',          '~> 0.18', '>= 0.18.0'
  gem 'chefspec',         '~> 3.2', '>= 3.2.0'
end

group :integration do
  gem 'test-kitchen',    '~> 1.1', '>= 1.1.0'
  gem 'kitchen-vagrant', '~> 0', '>= 0.14.0'
end

group :release do
  gem 'rspec_junit_formatter'
  gem 'rubocop-checkstyle_formatter'
  gem 'thor-scmversion',  '~> 1.4', '>= 1.4.0'
  gem 'git',              '~> 1.2', '>= 1.2.6'
end

group :development do
  gem 'serverspec',       '~> 0.14', '>= 0.14.2'
  gem 'guard',            '~> 1.8', '>= 1.8.3'
  gem 'guard-rubocop',    '~> 0.2', '>= 0.2.2'
  gem 'guard-foodcritic', '~> 1.0', '>= 1.0.0'
  gem 'guard-kitchen',    '~> 0.0', '>= 0.0.0'
  gem 'guard-rspec',      '~> 3.1', '>= 3.1.0'
  gem 'rb-fsevent', :require => false
  gem 'rb-inotify', :require => false
  gem 'terminal-notifier-guard', :require => false
end

• The versions in the README may get out of date. Please look in lib/kitchen-cabinet/templates for the up-to-date Gemfile.

The goal of this project is to prevent any manual setup of the cookbook environment. We used to copy Gemfiles and other configurations from cookbook to cookbook, making changes as needed. That quickly gets messy as things get out of date! With cabinet, every project starts with the same templated base.

gem install kitchen-cabinet

• In order to accomodate the most different use types, kitchen-cabinet supports omnibus and gem installations of chef. As such, it does not manage chef installation for you. Please install chef yourself before trying to use kitchen-cabinet.

Usage: cabinet [options] <cookbook name>

Options
    -o, --cookbook-path PATH         The directory where the cookbook will be created.
    -C, --copyright COPYRIGHT_HOLDER The  name  of  the  copyright holder.
    -I, --license LICENSE            The type of license under which a cookbook is distributed: apachev2, gplv2, gplv3, mit, or none (default).
    -m, --email EMAIL                The  email  address  for the individual who maintains the cookbook.
    -u, --update                     Update the Gemfile, Chefignore, Guardfile, rubocop.yml, and the Rakefile.
    -h, --help                       help

If you do not specify any options, cabinet will assume you want the defaults - it will read these from your knife.rb if available.

If you do not specify -o for a path to the directory you want to create your cookbook in, cabinet will create the new cookbook in your current directory. Likewise, if you say cabinet update, it will look in your current directory (which should be inside the cookbook) for files to update.

➜  cabinet --cookbook-path ~/Desktop -C Taylor Price -I apachev2 -m tprice@onehealth.com test
* Initializing chef
Using chef from /opt/chef/embedded/lib/ruby/gems/1.9.1
** Creating cookbook test
** Creating README for cookbook: test
** Creating CHANGELOG for cookbook: test
** Creating metadata for cookbook: test
	Rewriting metadata.rb
	Rewriting recipes/default.rb
* Initializing git
* Initializing berkshelf
      create  /Users/tprice/Desktop/test/Berksfile
      create  /Users/tprice/Desktop/test/Thorfile
      create  /Users/tprice/Desktop/test/.gitignore
         run  git init from "/Users/tprice/Desktop/test"
      create  /Users/tprice/Desktop/test/Gemfile
* Initializing kitchen
      create  .kitchen.yml
      append  Thorfile
      create  test/integration/default
      append  Gemfile
      append  Gemfile
You must run `bundle install' to fetch any new gems.
* Initializing chefspec
* Initializing serverspec
this is the test cookbook.
Cookbook test created successfully
Next steps...
  $ cd /Users/tprice/Desktop/test
  $ bundle install
  $ bundle exec berks install
  ...

And so on!

Please look at the CONTRIBUTING.md file for contribution guidelines.

Taylor Price - tprice@onehealth.com

Copyright 2014 OneHealth Solutions, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.