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


chefdk_bootstrap (51) Versions 2.0.0

Bootstrap a developer workstation for local Chef development using the ChefDK

cookbook 'chefdk_bootstrap', '= 2.0.0', :supermarket
cookbook 'chefdk_bootstrap', '= 2.0.0'
knife supermarket install chefdk_bootstrap
knife supermarket download chefdk_bootstrap
Quality 100%

ChefDK_Bootstrap Build Status Build status

Setup your laptop for Chef development in minutes

Run one simple command to easily set up your Windows or Mac machine
for Chef cookbook development in about 20 minutes.

Before You Begin

Windows Quickstart

Copy the PowerShell command below and paste them into a PowerShell Admin console. This will download and run the bootstrap
script on your workstation.

 Invoke-WebRequest -UseBasicParsing | Invoke-Expression

Mac Quickstart

Copy the command below and paste it into a terminal. This will download and run the bootstrap script on your workstation.

ruby -e "$(curl"

Mac ChefDK profile setup

Follow the instructions in the ChefDK README to complete the Chef workstation setup.

If you are behind a proxy


Set Proxy Environment Vars

Copy/paste these environment variables into your terminal.

# change these values to your proxy address
# don't go through the proxy for these addresses.
# change to your corporate DNS domain

Use this proxy-aware bootstrap script

Copy the PowerShell command below and paste them into a PowerShell Admin console. This will execute the bootstrap
script on your workstation.

 Invoke-WebRequest -UseBasicParsing -ProxyUseDefaultCredentials -Proxy $env:https_proxy | Invoke-Expression

The ChefDK_bootstrap script will write your environment variables to your Profile.ps1.


Copy/paste these environment variables into your terminal.

# change these values to your proxy address
export http_proxy=
export https_proxy=$http_proxy
# don't go through the proxy for these addresses.
# change to your corporate DNS domain
export no_proxy='localhost,,'

The ChefDK_bootstrap script will write your environment variables to your ~/.bash_profile.

If you are using a different shell, you will need to export these environment variables in your shell startup file (e.g. .zshrc).

Now run the Quickstart for Mac


If you want to use your own custom wrapper cookbook, add the name of your cookbook and your private supermarket source to these commands instead of the original Quickstart (examples included below).

JSON attributes

You can pass in attributes via URL/path to a JSON file (see the --json-attributes option in chef-client ). For Windows, json_attributes is a named parameter of the bootstrap PowerShell script. For Mac, json-attributes is a named parameter of the bootstrap Ruby script.


$CHEFDK_BOOTSTRAP_JSON_ATTRIBUTES = "http://server/attributes.json"

Invoke-WebRequest -UseBasicParsing | Invoke-Expression
install -json_attributes $CHEFDK_BOOTSTRAP_JSON_ATTRIBUTES


ruby -e "$(curl" - --json-attributes http://server/attributes.json

Custom cookbook

Deprecated. If you would like to use a custom cookbook, please use an earlier version of ChefDK_bootstrap.

ChefDK Version

You can specify the version of chefdk to install as a named parameter in the bootstrap script. By default, the bootstrap script will install the latest version of chefdk. The script will not re-install chefdk if the target version is already installed.


Invoke-WebRequest -UseBasicParsing | Invoke-Expression

install -version <target version>


ruby -e "$(curl" - --version <target version>

What does it do?

This cookbook installs these tools:


Atom, a free, general purpose, cross-platform, open source,
text editor. Out of the box, Atom supports all the languages you will need
for Chef development: Ruby, PowerShell, Bash, XML, JSON, etc.

Source Control

Git - command line git client and tools.

Local Virtualization

Virtualbox - Oracle's free, open source virtualization tool for local cookbook testing.

Vagrant - ChefDK's included Test Kitchen tool uses Vagrant to spin up local VMs for cookbook testing.



  • Installs Chocolatey for a Windows machine and homebrew for a Mac machine. Both of these are package managers, similar to apt-get on Ubuntu. Chocolatey is used to install packages like posh-git and kdiff3, while homebrew is used to install packages like iterm2.

  • Installs all the other tools marked true in the
    node['chefdk_bootstrap']['package'] hash.

  • On Windows, includes the Powershell profile configuration recipe.


  • Installs the Atom editor


  • On Windows, installs ConEmu (a console replacement)


  • Installs git.
  • On Windows, installs git-credential-winstore, and posh-git.


  • On Windows, installs gitextensions, a GUI git client.


  • On Windows, installs the free, open-source diff/merge tool, kdiff3.


  • Configures a global PowerShell profile to correct the $env:HOME environment variable and run chef shell-init powershell.


  • Installs Vagrant.


  • Installs Virtualbox.


  • On Mac, installs iterm2.


The attributes defined by this recipe are organized under the
node['chefdk_bootstrap'] namespace.

Attribute Description Type Default
['atom']['source_url'] Windows: Atom installer package source URL URL String
['atom']['source_url'] Mac: Atom installer package source URL URL String
['package']['atom'] Whether to install Atom or not boolean true
['package']['kdiff3'] Whether to install kdiff3 or not boolean true
['package']['vagrant'] Whether to install Vagrant or not boolean true
['package']['virtualbox'] Whether to install Virtualbox or not boolean true
['package']['git'] Whether to install git and related packages or not boolean true
['package']['gitextensions'] Whether to install gitextensions or not boolean true
['package']['iterm2'] Whether to install iterm2 or not boolean true
['package']['chefdk_julia'] Whether to install chefdk_julia or not boolean false


Nordstrom, Inc.


Copyright 2015 Nordstrom, 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

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.

Dependent cookbooks

atom ~> 0.2.0
chocolatey ~> 1.0
homebrew ~> 2.0
line ~> 0.6
vagrant ~> 0.5
windows ~> 1.39

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Revision History for chefdk_bootstrap


  • Fix #96 Consider rewriting bootstrap shell script in Ruby
  • Fix #74 chefdk_bootstrap 2.0: use named parameters for <your cookbook name> <your private supermarket url>
  • Fix #69 On Mac, set proxy env vars in bash profile
  • Fix #123 Bootstrap script should install latest ChefDK available by default
  • Fix #142 Add fix_profile and remove posh-git install for kitchen tests to avoid hanging
  • Fix #143 Remove support of custom cookbooks and private supermarkets
  • Add Appveyor for windows integration testing
  • Add version as a named parameter


  • Fix #134: Put SSH on the path so kitchen login works
  • Fix #132: Add comments to $Profile.CurrentUserAllHosts PowerShell profile
  • Fix #63: Dry up the cleanup in the Windows bootstrap
  • Fix #133: Clean up berkshelf environment variable from Windows bootstrap
  • Fix #47: Add kitchen config.yml file to pass through proxy settings (when needed)


  • Fix #130:
    Move PowerShell Profile customizations to a PowerShell module on the $env:PSModulePath

  • Fix #75:
    Write PowerShell profile customizations to $Profile.CurrentUserAllHosts

Upgrading from 1.7

This cookbook no longer writes C:\WINDOWS\System32\WindowsPowerShell\v1.0\profile.ps1.
If you are upgrading from 1.7 or earlier you will need to remove the lines added by the chefdk_bootstrap in v1.7.0
or delete the file.


  • Install ChefDK 0.13.21 via bootstrap script
  • Add InSpec integration tests for each (Windows) component
  • Recommend PowerShell 5.0 instead of 4.0 in README
  • Add ConEmu on Windows (Issue #115)
  • Fix PowerShell color contrast issues (Issues #40, #117)



  • Fix Atom install on Windows. Fixes #109.


  • Switch from chocolatey resource in Chocolatey cookbook to chocolatey_package resource in Chef 12.7
  • Install Virtualbox on Mac via dmg_package resource instead of homebrew. Fixes #97.


  • Use sudo to remove temporary directory
  • Switch .kitchen.yml to use @mwrockx's Windows2012R2 Atlas Vagrant box.
  • Mac: Fix #81 by hiding script download progress from cURL
  • Improve spec coverage from 46% to 87%
  • Bootstrap now writes correct Ohai disabled_plugins syntax to remove deprecation warning.


  • Mac: Don't create directories which homebrew cookbook already creates
  • Bootstrap: create temporary directory using mktemp -d
  • Stop creating ~/.chef, ~/chef, and ~/chef/cookbooks directories in bootstrap script since creating these directories has been moved to the cookbook.


  • Bump homebrew dependency to ~> 2.0 because Homebrew cookbook v2.0.4 fixes chef-cookbooks/homebrew#87. This will fix the bootstrap for Mac users.
  • Update Windows cookbook dependency


  • Fix the chefdk_julia install attribute to match others and document it


  • Install 64-bit git 2.7
  • Install Git Credential Manager for Windows, which replaces the deprecated git-credential-winstore.
  • Add option to install chefdk-julia
  • Refactor specs. Use shared_context for Windows and Mac Chef runs. Fix broken tests by setting node['vagrant']['checksum'] attribute in Chef runs.


  • Install Vagrant via community Vagrant cookbook


  • create ~/.chef, ~/chef, ~/chef/cookbooks
  • fixes #43


  • Mac OS X: create /opt/homebrew-cask directory
  • fixes #60


  • Windows: Check for Admin rights or exit
  • Windows: Use omnitruck ChefDK installation, selecting specific version
  • Windows: Check installed ChefDK version, do the right thing.
  • Windows: Check for error status after various commands
  • fixes #56
  • fixes #49
  • fixes #33


  • Switch from brew-cask to omnitruck chefdk installation for Mac OS X
  • Make bootstrap incrementally more robust on Mac OS X
  • fixes #33
  • Fixes #45
  • fixes #56 on mac osx, still an issue on windows


  • Depend on chocolatey 0.5.0 to improve installation behind a proxy
  • Install Git v2.5.1 instead of v1.9.5

Dev environment changes

  • Travis CI builds use ChefDK built-in gems instead of Gemfile + bundler
  • Rakefile defines default task of :style, :spec


  • Minor edits to README for clarity


  • Make non-proxy README instructions work for Windows. Fixes #35
  • Clear screen as first step in bootstrap script. Fixes #34


  • Add Apache 2.0 license header.


  • Add Travis CI support to run style and unit tests
  • Recommend PowerShell 4.0 instead of PowerShell 3.0 because 4.0 supports DSC.


  • Update bootstrap script to take a private source and cookbook name and add it to the Berksfile.
  • Update README.


  • Add guards around file deletions.


  • Edit README to clarify proxy instructions.


  • Add instructions for no_proxy environment variable in the README.


  • Set proxy environment variables in powershell_profile.
  • This enables command-line tools like git, cURL, and Test Kitchen to work behind a proxy.


  • Fix bug in Atom setup for Windows


  • Edited the README to make the markdown for Chef Supermaket consistent.


  • Clarified Windows bootstrap instructions.


  • Added Mac bootstrap functionality.


  • Add ability to set http_proxy, https_proxy, and no_proxy env vars.

These env vars allow Chef related command line tools, e.g. git, berkshelf, to
work via a web proxy.


  • Add proxy support to bootstrap script.


  • Update README
  • Add introduction to bootstrap script.
  • Add Atom source URL for Mac platform


  • Bootstrap script bug fixes


  • Add PowerShell bootstrap script


PuTTY is difficult to configure and outside the scope of what this cookbook is
trying to do. Furthermore the Github for Windows client doesn't use PuTTY



  • Initial version

Collaborator Number Metric

2.0.0 passed this metric

Foodcritic Metric

2.0.0 passed this metric