Manage Chef Infra cookbooks and cookbook dependencies
Berkshelf is effectively deprecated. There is no ongoing maintenance and triage of issues. No active work is being done on bugfixes. The only work being done is to maintain it so that it continues to ship and run in its existing state.
Existing users should strongly consider migrating to Policyfiles and new users should avoid using Berkshelf.
Berkshelf is now included as part of the Chef Workstation. This is fastest, easiest, and the recommended installation method for getting up and running with Berkshelf.
note: You may need to uninstall the Berkshelf gem especially if you are using a Ruby version manager you may need to uninstall all Berkshelf gems from each Ruby installation.
If you are a developer or you prefer to install from Rubygems, we've got you covered.
Add Berkshelf to your repository's Gemfile:
gem 'berkshelf'Or run it as a standalone:
$ gem install berkshelfSee docs.chef.io for up-to-date usage instructions.
Berkshelf is intended to be used as a CLI tool. It is not intended to be used as a library. Other ruby code should shell out to the command line tool to use it.
Berkshelf is tested and supported on Ruby 2.4 and later.
Berkshelf will search in specific locations for a configuration file. In order:
$PWD/.berkshelf/config.json
~/.berkshelf/config.json
You are encouraged to keep project-specific configuration in the $PWD/.berkshelf directory. A default configuration file is generated for you, but you can update the values to suit your needs.
Please see Plugins page for more information.
- If you have an issue: report it on the issue tracker
- If you have a question: visit the #chef or #berkshelf channel on irc.freenode.net
Thank you to all of our Contributors, testers, and users.
If you'd like to contribute, please see our contribution guidelines first.
