Skip to content
This repository has been archived by the owner on Jul 11, 2020. It is now read-only.

Commit

Permalink
Add info about ChefDK and other option for getting environment setup
Browse files Browse the repository at this point in the history
Sam Kottler committed Jun 21, 2014

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
1 parent f43ef19 commit a0e832e
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -6,9 +6,11 @@ This repository contains chef artifacts used to deploy all the different pieces
2. Unless a wrapper cookbooks requires a cookbook for the same software which is different than what's on the Chef community site, all dependencies should be in a wrapper cookbook's `metadata.rb`, rather than in the `Berksfile` located in the root of this repo.
3. No binaries ever go into this repo. They should all live in an apt repository or in S3.

## Development Setup
### Development Setup

You will need **ruby 2.0** and **bundler** installed. Run `bundle install --local`.
[ChefDK](http://www.getchef.com/downloads/chef-dk) is the recommended way to get the different tools necessary to manage, install, and test our chef deployment. It includes things like an embedded Ruby, [Berkshelf](http://berkshelf.com/), and [Test Kitchen](http://kitchen.ci/). After you've download and installed the necessary ChefDK package for your platform, run `/opt/chefdk/embedded/bin/bundle install --local` to add a few tools we use which are not included in the ChefDK packages.

If you'd prefer to avoid ChefDK, then you will need to have Ruby 2.0 and Bundler installed. Then run `bundle install --local` to install all the gems required for development.

### License

0 comments on commit a0e832e

Please sign in to comment.