Configure Your Chef Development Environment - Learning Chef - page 33

NOTE
If you do not want to change your $PATH , you could specify the full path to each embed-
ded binary on the command line, such as
/opt/chefdk/embedded/bin/ruby
Going forward, so the command line entries fit better on our printed pages, this topic will
assume that you modified your $PATH .
Verify that the basic Chef Client tools are present by checking /opt/chefdk/bin or /opt/chef/
bin depending on whether you installed the Chef Development Kit or the Chef Client. You
should see the following with the Chef Development Kit installation:
$ ls /opt/chefdk/bin
berks chef-service-manager fauxhai nokogiri ruby-rewrite
chef chef-shell foodcritic ohai shef
chef-apply chef-solo kitchen rubocop tt
chef-client chef-vault knife ruby-parse
and with the Chef Client installation:
$ ls /opt/chef/bin
chef-apply chef-service-manager chef-solo erubis ohai restclient
chef-client chef-shell cher-zero knife rackup shef
Run chef-client --version to ensure the chef-client command works properly. If your
version differs, make sure that you have chef-client version 11.10.0, or higher to follow
the hands-on exercises in this topic:
$ chef-client --version
Chef: 11.14.6
If you installed the Chef Development Kit, you have now successfully installed the Chef de-
velopment tools on Mac OS X. Skip ahead to Summary . If you installed the Chef Client,
you'll need to perform a few more installation steps, so keep reading.