Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


makenew-chef_cookbook (7) Versions 3.3.3

Chef cookbook skeleton.

cookbook 'makenew-chef_cookbook', '~> 3.3.3', :supermarket
cookbook 'makenew-chef_cookbook', '~> 3.3.3'
knife supermarket install makenew-chef_cookbook
knife supermarket download makenew-chef_cookbook
Quality 33%

Chef Cookbook Skeleton

Chef cookbook
[GitHub license](./LICENSE.txt)

Built from makenew/chef-cookbook.

wercker status


Chef cookbook skeleton.

Bootstrap a new Chef cookbook in less than a minute.


Bootstrapping a New Project

  1. Clone the master branch of this repository with
   $ git clone --single-branch new-chef-cookbook
   $ cd new-chef-cookbook

Optionally, reset to the latest release with

   $ git reset --hard chef-cookbook-v3.3.3
  1. Run
   $ ./

and follow the prompts.
This will replace the boilerplate, delete itself,
and stage changes for commit.
This script assumes the project repository will be hosted on GitHub.
For an alternative location, you must update the URLs manually.

  1. Fill in the README Description section
    and add (or remove) your own wercker badge to doc/
    (you will need to create a new wercker application).

  2. If choosing a license other than the one provided:
    update LICENSE.txt, the README License section,
    metadata.rb, attributes/default.rb,
    and recipes/default.rb with your chosen license.

  3. Regenerate with $ rake readme.
    Do not edit directly: it will be generated
    from using data from
    metadata.rb, and the .md files in /doc.

  4. Optionally, set require_chef_omnibus in .kitchen.yml
    to a specific Chef version.
    You may also set the Ruby versions to test against
    in .travis.yml and wercker.yml.
    If using codecov and wercker,
    you must set the CODECOV_TOKEN environment variable.


If you want to pull in future updates from this skeleton,
you can fetch and merge in changes from this repository.

If this repository is already set as origin,
rename it to upstream with

$ git remote rename origin upstream

and then configure your origin branch as normal.

Otherwise, add this as a new remote with

$ git remote add upstream

You can then fetch and merge changes with

$ git fetch upstream
$ git merge upstream/master


Note that is just a template for this skeleton.
The actual changes for this project are documented in the commit history
and summarized under Releases.


  • Chef 12.


Add this as a dependency in your cookbook's metadata.rb with

depends 'makenew-chef_cookbook'

Alternatively, add this to your Berksfile with

cookbook 'makenew-chef_cookbook'

and update your cookbooks with

$ berks

Platform Support

  • ubuntu (~> 14.04)


  • makenew-chef_cookbook::default - Default recipe.

Development and Testing


You will need Ruby with Bundler.

VirtualBox and Vagrant are required
for integration testing with Test Kitchen.

The following Vagrant plugins are recommended:
vagrant-berkshelf, vagrant-cachier, vagrant-ohai and vagrant-omnibus.

Install the development dependencies with

$ bundle

Source Code

The makenew-chef_cookbook source is hosted on GitHub.
Clone the project with

$ git clone


Run rake -T to see all Rake tasks.

rake all                          # Run all tasks
rake doc                          # Build documentation
rake foodcritic                   # Lint Chef cookbooks
rake kitchen:all                  # Run all test instances
rake kitchen:default-ubuntu-1404  # Run default-ubuntu-1404 test instance
rake publish                      # Publish this cookbook
rake readme                       # Generate from
rake rubocop                      # Run RuboCop
rake rubocop:auto_correct         # Auto-correct RuboCop offenses
rake spec                         # Run RSpec code examples
rake test                         # Run kitchen integration tests
rake yard                         # Generate YARD Documentation


Run thor -T to see all Thor tasks.


Guard tasks have been separated into the following groups:
doc, lint, unit, and integration.

By default, Guard will generate documentation, lint, and run unit tests.
The integration group must be selected manually with guard -g integration.


Please submit and comment on bug reports and feature requests.

To submit a patch:

  1. Fork it (
  2. Create your feature branch (git checkout -b my-new-feature).
  3. Make changes. Write and run tests.
  4. Commit your changes (git commit -am 'Add some feature').
  5. Push to the branch (git push origin my-new-feature).
  6. Create a new Pull Request.

This software can be used freely, see The Unlicense.
The copyright text appearing below and elsewhere in this repository
is for demonstration purposes only and does not apply to this software.


Copyright 2016 Evan Sosenko

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

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.


This software is provided "as is" and without any express or
implied warranties, including, without limitation, the implied
warranties of merchantibility and fitness for a particular

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Change Log

All notable changes to this project will be documented in this file.
This project adheres to Semantic Versioning.
This change log follows the conventions of


Collaborator Number Metric

3.3.3 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric

3.3.3 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Foodcritic Metric

3.3.3 passed this metric

No Binaries Metric

3.3.3 passed this metric

Testing File Metric

3.3.3 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Version Tag Metric

3.3.3 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must include a tag that matches this cookbook version number