chef 0.10.0.beta.8 → 0.10.0.beta.9

data/distro/common/markdown/man1/knife-bootstrap.mkd

@@ -28,12 +28,13 @@ __knife__ __bootstrap__ _(options)_
   * `-d`, `--distro DISTRO`:
     Bootstrap a distro using a template
 
+## DESCRIPTION
+
 Performs a Chef Bootstrap on the target node. The goal of the bootstrap
 is to get Chef installed on the target system so it can run Chef Client
 with a Chef Server. The main assumption is a baseline OS installation
 exists. This sub-command is used internally by some cloud computing
-server create commands and the others will be migrated in a future
-version of Chef.
+plugins.
 
 The bootstrap sub-command supports supplying a template to perform the
 bootstrap steps. If the distro is not specified (via `-d` or `--distro`
@@ -47,22 +48,34 @@ sub-command looks in the following locations for the template to use:
 * `bootstrap` directory in the `$PWD/.chef`.
 * `bootstrap` directory in the users `$HOME/.chef`.
 
-The default bootstrap templates are scripts that get copied to the target node (FQDN). As of Chef 0.9.8, the following distros are supported:
+The default bootstrap templates are scripts that get copied to the
+target node (FQDN). The following distros are supported:
 
 * centos5-gems
 * fedora13-gems
 * ubuntu10.04-gems
 * ubuntu10.04-apt
 
-The gems installations will use RubyGems 1.3.6 and Chef installed as a gem. The apt installation will use the Opscode APT repository. The RubyGems installation requires installing gems with native extensions, so development related packages (ruby-dev, build-essential) are installed. These are not installed with the apt installation, as native extensions are already compiled in the required packages.
+The gems installations will use RubyGems 1.3.6 and Chef installed as a
+gem. The apt installation will use the Opscode APT repository. The
+RubyGems installation requires installing gems with native extensions,
+so development related packages (ruby-dev, build-essential) are
+installed. These are not installed with the apt installation, as native
+extensions are already compiled in the required packages.
 
-In addition to handling the software installation, these bootstrap templates do the following:
+In addition to handling the software installation, these bootstrap
+templates do the following:
 
   - Write the validation.pem per the local knife configuration.
   - Write a default config file for Chef (`/etc/chef/client.rb`) using values from the `knife.rb`.
   - Create a JSON attributes file containing the specified run list and run Chef.
 
-In the case of the RubyGems, the `client.rb` will be written from scratch with a minimal set of values; see __EXAMPLES__. In the case of APT Package installation, `client.rb` will have the `validation_client_name` appended if it is not set to `chef-validator` (default config value), and the `node_name` will be added if `chef_node_name` option is specified.
+In the case of the RubyGems, the `client.rb` will be written from
+scratch with a minimal set of values; see __EXAMPLES__. In the case of
+APT Package installation, `client.rb` will have the
+`validation_client_name` appended if it is not set to `chef-validator`
+(default config value), and the `node_name` will be added if
+`chef_node_name` option is specified.
 
 When this is complete, the bootstrapped node will have:
 
@@ -70,8 +83,45 @@ When this is complete, the bootstrapped node will have:
   - Be validated with the configured Chef Server.
   - Have run Chef with its default run list if one is specfied.
 
-Additional custom bootstrap templates can be created and stored in `.chef/bootstrap/DISTRO.erb`, replacing __DISTRO__ with the value passed with the `-d` or `--distro` option. See __EXAMPLES__ for more information.
+Additional custom bootstrap templates can be created and stored in
+`.chef/bootstrap/DISTRO.erb`, replacing __DISTRO__ with the value passed
+with the `-d` or `--distro` option. See __EXAMPLES__ for more
+information.
+
+## EXAMPLES
+Setting up a custom bootstrap is fairly straightforward. Create a
+`.chef/bootstrap` directory in your Chef Repository or in
+`$HOME/.chef/bootstrap`. Then create the ERB template file.
+
+    mkdir ~/.chef/bootstrap
+    vi ~/.chef/bootstrap/debian5.0-apt.erb
+
+For example, to create a new bootstrap template that should be used when
+setting up a new Debian node. Edit the template to run the commands, set
+up the validation certificate and the client configuration file, and
+finally to run chef-client on completion. The bootstrap template can be
+called with:
+
+    knife bootstrap mynode.example.com --template-file ~/.chef/bootstrap/debian5.0-apt.erb
+
+Or,
+
+    knife bootstrap mynode.example.com --distro debian5.0-apt
+
+The `--distro` parameter will automatically look in the
+`~/.chef/bootstrap` directory for a file named `debian5.0-apt.erb`.
+
+Templates provided by the Chef installation are located in
+`BASEDIR/lib/chef/knife/bootstrap/*.erb`, where _BASEDIR_ is the
+location where the package or Gem installed the Chef client libraries.
+
+## BUGS
+`knife bootstrap` is not capable of bootstrapping multiple hosts in
+parallel.
 
+The bootstrap script is passed as an argument to sh(1) on the remote
+system, so sensitive information contained in the script will be visible
+to other users via the process list using tools such as ps(1).
 
 ## SEE ALSO
    __knife-ssh__(1)

data/distro/common/markdown/man1/knife-client.mkd

@@ -5,23 +5,9 @@ knife-client(1) -- Manage Chef API Clients
 
 __knife__ __client__ _sub-command_ _(options)_
 
-## DESCRIPTION
-Clients are identities used for communication with the Chef Server API,
-roughly equivalent to user accounts on the Chef Server, except that
-clients only communicate with the Chef Server API and are authenticated
-via request signatures.
-
-In the typical case, there will be one client object on the server for
-each node, and the corresponding client and node will have identical
-names.
-
-In the Chef authorization model, there is one special client, the
-"validator", which is authorized to create new non-administrative
-clients but has minimal privileges otherwise. This identity is used as a
-sort of "guest account" to create a client identity when initially
-setting up a host for management with Chef.
-
-## CLIENT SUB-COMMANDS
+## SUB-COMMANDS
+Client subcommands follow a basic create, read, update, delete (CRUD)
+pattern. The Following subcommands are available:
 
 ## BULK DELETE
 __knife client bulk delete__ _regex_ _(options)_
@@ -86,6 +72,22 @@ __client show__ _client name_ _(options)_
 
 Show a client. Output format is determined by the --format option.
 
+## DESCRIPTION
+Clients are identities used for communication with the Chef Server API,
+roughly equivalent to user accounts on the Chef Server, except that
+clients only communicate with the Chef Server API and are authenticated
+via request signatures.
+
+In the typical case, there will be one client object on the server for
+each node, and the corresponding client and node will have identical
+names.
+
+In the Chef authorization model, there is one special client, the
+"validator", which is authorized to create new non-administrative
+clients but has minimal privileges otherwise. This identity is used as a
+sort of "guest account" to create a client identity when initially
+setting up a host for management with Chef.
+
 ## SEE ALSO
    __knife-node__(1)
 

data/distro/common/markdown/man1/knife-cookbook-site.mkd

@@ -6,28 +6,58 @@ knife-cookbook-site(1) -- Install and update open source cookbooks
 __knife__ __cookbook site__ _sub-command_ _(options)_
 
 ## COOKBOOK SITE SUB-COMMANDS
+`knife cookbook site` provides the following subcommands:
 
-The following sub-commands are still in the context of cookbooks, but they make use of Opscode's Cookbook Community site, _http://cookbooks.opscode.com/_. That site has an API, and these sub-commands utilize that API, rather than the Chef Server API.
+## INSTALL
+__cookbook site install COOKBOOK [VERSION]__ _(options)_
 
-__cookbook site download COOKBOOK [VERSION]__ _(options)_
+  * `-d`, `--dependencies`:
+    Grab dependencies automatically
+
+Uses git(1) version control in conjunction with the cookbook site to
+install community contributed cookbooks to your local cookbook
+repository. Running `knife cookbook site install` does the following:
+
+1. A new "pristine copy" branch is created in git for tracking the
+   upstream;
+2. All existing cookbooks are removed from the branch;
+3. The cookbook is downloaded from the cookbook site in tarball form;
+4. The downloaded cookbook is untarred, and its contents commited via git;
+5. The pristine copy branch is merged into the master branch.
+
+By installing cookbook with this process, you can locally modify the
+upstream cookbook in your master branch ant let git maintain your
+changes as a separate patch.  When an updated upstream version becomes
+available, you will be able to merge the upstream changes while
+maintaining your local modifications.
+
+If _-d_ is specified, the process is applied recursively to all the
+cookbooks _COOKBOOK_ depends on (via metadata _dependencies_).
+
+## DOWNLOAD
+__knife cookbook site download COOKBOOK [VERSION]__ _(options)_
 
   * `-f`, `--file FILE`:
     The filename to write to
 
-Downloads a specific cookbook from the Community site, optionally specifying a certain version.
+Downloads a specific cookbook from the Community site, optionally
+specifying a certain version.
 
-__cookbook site list__ _(options)_
+## LIST
+__knife cookbook site list__ _(options)_
 
   * `-w`, `--with-uri`:
     Show corresponding URIs
 
 Lists available cookbooks from the Community site.
 
-__cookbook site search QUERY__ _(options)_
+## SEARCH
+__knife cookbook site search QUERY__ _(options)_
 
-Searches the Community site with the specified query.
+Searches for available cookbooks matching the specified query.
 
-__cookbook site share COOKBOOK CATEGORY__ _(options)_
+## SHARE
+__knife cookbook site share COOKBOOK CATEGORY__ _(options)_
 
   * `-k`, `--key KEY`:
     API Client Key
@@ -36,26 +66,44 @@ __cookbook site share COOKBOOK CATEGORY__ _(options)_
   * `-o`, `--cookbook-path PATH:PATH`:
     A colon-separated path to look for cookbooks in
 
-Uploads the specified cookbook using the given category to the Opscode cookbooks site. Requires a login user and certificate for the Opscode Cookbooks site. See __EXAMPLES__ for usage if the Opscode user and certificate pair are not used for authenticating with the Chef Server. In other words, if the Chef Server is not the Opscode Platform.
+Uploads the specified cookbook using the given category to the Opscode
+cookbooks site. Requires a login user and certificate for the Opscode
+Cookbooks site. By default, knife will use the username and API key
+you've configured in your configuration file; otherwise you must
+explicitly set these values on the command line or use an alternate
+configuration file.
 
-__cookbook site unshare COOKBOOK__
+## UNSHARE
+__knife cookbook site unshare COOKBOOK__
 
 Stops sharing the specified cookbook on the Opscode cookbooks site.
 
-__cookbook site show COOKBOOK [VERSION]__ _(options)_
+## SHOW
+__knife cookbook site show COOKBOOK [VERSION]__ _(options)_
 
 Shows information from the site about a particular cookbook.
 
-__cookbook site vendor COOKBOOK [VERSION]__ _(options)_
+## DESCRIPTION
+The cookbook site, <http://community.opscode.com/>, is a cookbook
+distribution service operated by Opscode. This service provides users
+with a central location to publish cookbooks for sharing with other
+community members.
 
-  * `-d`, `--dependencies`:
-    Grab dependencies automatically
+`knife cookbook site` commands provide an interface to the cookbook
+site's HTTP API. For commands that read data from the API, no account is
+required. In order to upload cookbooks using the `knife cookbook site
+share` command, you must create an account on the cookbook site and
+configure your credentials via command line option or in your knife
+configuration file.
 
-Uses `git` version control in conjunction with the cookbook site to download upstream cookbooks. A new vendor branch is created in git, the cookbook downloaded from the site and untarred, then the master branch is merged. This allows the user to track upstream changes to cookbooks while merging in customizations. If _-d_ is specified, all the cookbooks it depends on (via metadata _dependencies_) are downloaded and untarred as well, each using their own vendor branch.
+## EXAMPLES
+Uploading cookbooks to the Opscode cookbooks site:
 
+    knife cookbook site share example Other -k ~/.chef/USERNAME.pem -u USERNAME
 
 ## SEE ALSO
-   __knife-environment__(1)
+   __knife-cookbook(1)__
+   <http://community.opscode.com/cookbooks>
 
 ## AUTHOR
    Chef was written by Adam Jacob <adam@opscode.com> with many contributions from the community.

data/distro/common/markdown/man1/knife-cookbook.mkd

@@ -1,136 +1,253 @@
-knife-cookbook(1) -- Upload and manage Chef cookbooks
+knife-cookbook(1) -- upload and manage chef cookbooks
 ========================================
 
 ## SYNOPSIS
 
 __knife__ __cookbook__ _sub-command_ _(options)_
 
-## COOKBOOK SUB-COMMANDS
+## SUB-COMMANDS
+`knife cookbook` supports the following sub commands:
 
-Cookbooks are the fundamental unit of distribution in Chef. They encapsulate all recipes of resources and assets used to configure a particular aspect of the infrastructure. The following sub-commands can be used to manipulate the cookbooks stored on the Chef Server.
+## LIST
+__knife cookbook list__ _(options)_
 
-__cookbook bulk delete REGEX__ _(options)_
-
-  * `-p`, `--purge`:
-    Purge files from backing store. This will disable any cookbook that contains any of the same files as the cookbook being purged.
-
-Delete cookbooks on the Chef Server based on a regular expression. The regular expression (_REGEX_) should be in quotes, not in //'s.
-
-__cookbook create COOKBOOK__ _(options)_
-
-  * `-o`, `--cookbook-path PATH`:
-    The directory where the cookbook will be created
-  * `-r`, `--readme-format FORMAT`:
-    Format of the README file
-  * `-C`, `--copyright COPYRIGHT`:
-    Name of Copyright holder
-  * `-I`, `--license LICENSE`:
-    License for cookbook, apachev2 or none
-  * `-E`, `--email EMAIL`:
-    Email address of cookbook maintainer
-
-This is a helper command that creates a new cookbook directory in the `cookbook_path`. The following directories and files are created for the named cookbook.
-
-* COOKBOOK/attributes
-* COOKBOOK/definitions
-* COOKBOOK/files/default
-* COOKBOOK/libraries
-* COOKBOOK/metadata.rb
-* COOKBOOK/providers
-* COOKBOOK/README.rdoc
-* COOKBOOK/recipes/default.rb
-* COOKBOOK/resources
-* COOKBOOK/templates/default
-
-Supported README formats are 'rdoc' (default), 'md', 'mkd', 'txt'. The README file will be written with the specified extension and a set of helpful starting headers.
+  * `-a`, `--all`:
+    show all versions of a cookbook instead of just the most recent
+  * `-w`, `--with-uri`:
+    show corresponding uris
 
-Specify `-C` or `--copyright` with the name of the copyright holder as your name or your company/organization name in a quoted string. If this value is not specified an all-caps string `YOUR_COMPANY_NAME` is used which can be easily changed with find/replace.
+Lists the cookbooks available on the Chef server.
 
-Specify `-I` or `--license` with the license that the cookbook is distributed under for sharing with other people or posting to the Opscode Cookbooks site. Be aware of the licenses of files you put inside the cookbook and follow any restrictions they describe. When using `none` (default) or `apachev2`, comment header text and metadata file are pre-filled. The `none` license will be treated as non-redistributable.
+## SHOW
+__knife cookbook show cookbook [version] [part] [filename]__ _(options)_
 
-Specify `-E` or `--email` with the email address of the cookbook's maintainer. If this value is not specified, an all-caps string `YOUR_EMAIL` is used which can easily be changed with find/replace.
+  * `-f`, `--fqdn fqdn               `:
+    the fqdn of the host to see the file for
+  * `-p`, `--platform platform       `:
+    the platform to see the file for
+  * `-v`, `--platform-version version`:
+    the platform version to see the file for
 
-The cookbook copyright, license and email settings can be filled in the `knife.rb`, for example with default values:
+show a particular part of a _cookbook_ for the specified _version_. _part_ can be one of:
 
-    cookbook_copyright "YOUR_COMPANY_NAME"
-    cookbook_license "none"
-    cookbook_email "YOUR_EMAIL"
+  * _attributes_
+  * _definitions_
+  * _files_
+  * _libraries_
+  * _providers_
+  * _recipes_
+  * _resources_
+  * _templates_
 
-__cookbook delete COOKBOOK [VERSION]__ _(options)_
+## UPLOAD
+__knife cookbook upload [cookbooks...]__ _(options)_
 
   * `-a`, `--all`:
-    Delete all versions
-  * `-p`, `--purge`:
-    Purge files from backing store. This will disable any cookbook that contains any of the same files as the cookbook being purged.
-
-Delete the specified _VERSION_ of the named _COOKBOOK_. If no version is specified, and only one version exists on the server, that version will be deleted. If multiple versions are available on the server, you will be prompted for a version to delete.
-
-__cookbook download COOKBOOK [VERSION]__ _(options)_
-
-  * `-d`, `--dir DOWNLOAD_DIRECTORY`:
-    The directory to download the cookbook into
+    upload all cookbooks, rather than just a single cookbook
+  * `-o`, `--cookbook-path path:path`:
+    a colon-separated path to look for cookbooks in
+  * `-E`, `--environment ENVIRONMENT`:
+    An _ENVIRONMENT_ to apply the uploaded cookbooks to. Specifying this
+    option will cause knife to edit the _ENVIRONMENT_ to place a strict
+    version constraint on the cookbook version(s) uploaded.
+  * `--freeze`:
+    Sets the frozen flag on the uploaded cookbook(s) Any future attempt
+    to modify the cookbook without changing the version number will
+    return an error unless --force is specified.
+  * `--force`:
+    Overrides the frozen flag on a cookbook, allowing you to overwrite a
+    cookbook version that has previously been uploaded with the --freeze
+    option.
+
+Uploads one or more cookbooks from your local cookbook repository(ies)
+to the Chef Server. Only files that don't yet exist on the server will
+be uploaded.
+
+## DOWNLOAD
+__knife cookbook download cookbook [version]__ _(options)_
+
+  * `-d`, `--dir download_directory`:
+    the directory to download the cookbook into
   * `-f`, `--force`:
-    Overwrite an existing directory with the download
-  * `-N`, `--latest`:
-    Download the latest version of the cookbook
-
-Download a cookbook from the Chef Server. If no version is specified and only one version exists on the server, that version will be downloaded. If no version is specified and multiple versions are available on the server, you will be prompted for a version to download.
-
-__cookbook list__ _(options)_
+    overwrite an existing directory with the download
+  * `-n`, `--latest`:
+    download the latest version of the cookbook
 
-  * `-w`, `--with-uri`:
-    Show corresponding URIs
-
-List all the cookbooks.
+download a cookbook from the chef server. if no version is specified and
+only one version exists on the server, that version will be downloaded.
+if no version is specified and multiple versions are available on the
+server, you will be prompted for a version to download.
 
-__cookbook metadata COOKBOOK__ _(options)_
+## DELETE
+__knife cookbook delete cookbook [version]__ _(options)_
 
   * `-a`, `--all`:
-    Generate metadata for all cookbooks, rather than just a single cookbook
-  * `-o`, `--cookbook-path PATH:PATH`:
-    A colon-separated path to look for cookbooks in
-
-Generate cookbook metadata for the named _COOKBOOK_. The _PATH_ used here specifies where the cookbooks directory is located and corresponds to the `cookbook_path` configuration option.
+    delete all versions
+  * `-p`, `--purge`:
+    purge files from backing store. this will disable any cookbook that contains any of the same files as the cookbook being purged.
 
-__cookbook metadata from FILE__ _(options)_
+delete the specified _version_ of the named _cookbook_. if no version is
+specified, and only one version exists on the server, that version will
+be deleted. if multiple versions are available on the server, you will
+be prompted for a version to delete.
 
-Load the cookbook metadata from a specified file.
+## BULK DELETE
+__knife cookbook bulk delete regex__ _(options)_
 
-__cookbook show COOKBOOK [VERSION] [PART] [FILENAME]__ _(options)_
+  * `-p`, `--purge`:
+    purge files from backing store. this will disable any cookbook that
+    contains any of the same files as the cookbook being purged.
+
+delete cookbooks on the chef server based on a regular expression. the
+regular expression (_regex_) should be in quotes, not in //'s.
+
+## COOKBOOK CREATE
+__knife cookbook create cookbook__ _(options)_
+
+  * `-o`, `--cookbook-path path`:
+    the directory where the cookbook will be created
+  * `-r`, `--readme-format format`:
+    format of the readme file
+  * `-c`, `--copyright copyright`:
+    name of copyright holder
+  * `-i`, `--license license`:
+    license for cookbook, apachev2 or none
+  * `-e`, `--email email`:
+    email address of cookbook maintainer
+
+this is a helper command that creates a new cookbook directory in the
+`cookbook_path`. the following directories and files are created for the
+named cookbook.
+
+* cookbook/attributes
+* cookbook/definitions
+* cookbook/files/default
+* cookbook/libraries
+* cookbook/metadata.rb
+* cookbook/providers
+* cookbook/readme.rdoc
+* cookbook/recipes/default.rb
+* cookbook/resources
+* cookbook/templates/default
+
+supported readme formats are 'rdoc' (default), 'md', 'mkd', 'txt'. the
+readme file will be written with the specified extension and a set of
+helpful starting headers.
+
+specify `-c` or `--copyright` with the name of the copyright holder as
+your name or your company/organization name in a quoted string. if this
+value is not specified an all-caps string `your_company_name` is used
+which can be easily changed with find/replace.
+
+specify `-i` or `--license` with the license that the cookbook is
+distributed under for sharing with other people or posting to the
+opscode cookbooks site. be aware of the licenses of files you put inside
+the cookbook and follow any restrictions they describe. when using
+`none` (default) or `apachev2`, comment header text and metadata file
+are pre-filled. the `none` license will be treated as
+non-redistributable.
+
+specify `-e` or `--email` with the email address of the cookbook's
+maintainer. if this value is not specified, an all-caps string
+`your_email` is used which can easily be changed with find/replace.
+
+the cookbook copyright, license and email settings can be filled in the
+`knife.rb`, for example with default values:
+
+    cookbook_copyright "your_company_name"
+    cookbook_license "none"
+    cookbook_email "your_email"
 
-  * `-f`, `--fqdn FQDN               `:
-    The FQDN of the host to see the file for
-  * `-p`, `--platform PLATFORM       `:
-    The platform to see the file for
-  * `-V`, `--platform-version VERSION`:
-    The platform version to see the file for
 
-Show a particular part of a _COOKBOOK_ for the specified _VERSION_. _PART_ can be one of:
-
-  * _attributes_
-  * _definitions_
-  * _files_
-  * _libraries_
-  * _providers_
-  * _recipes_
-  * _resources_
-  * _templates_
-
-__cookbook test [COOKBOOKS...]__ _(options)_
+## METADATA
+__knife cookbook metadata cookbook__ _(options)_
 
   * `-a`, `--all`:
-    Test all cookbooks, rather than just a single cookbook
-  * `-o`, `--cookbook-path PATH:PATH`:
-    A colon-separated path to look for cookbooks in
+    generate metadata for all cookbooks, rather than just a single cookbook
+  * `-o`, `--cookbook-path path:path`:
+    a colon-separated path to look for cookbooks in
 
-Test the specified cookbooks for syntax errors. This uses the built-in Ruby syntax checking option for files in the cookbook ending in `.rb`, and the ERB syntax check for files ending in `.erb` (templates).
+generate cookbook metadata for the named _cookbook_. the _path_ used here specifies where the cookbooks directory is located and corresponds to the `cookbook_path` configuration option.
 
-__cookbook upload [COOKBOOKS...]__ _(options)_
+## METADATA FROM FILE
+__knife cookbook metadata from file__ _(options)_
 
-  * `-a`, `--all`:
-    Upload all cookbooks, rather than just a single cookbook
-  * `-o`, `--cookbook-path PATH:PATH`:
-    A colon-separated path to look for cookbooks in
+load the cookbook metadata from a specified file.
 
-Uploads the specified cookbooks to the Chef Server. The actual upload executes a number of commands, most of which occur on the local machine. The cookbook is staged in a temporary location. Then the `cookbook_path` (or `-o PATH`) is processed to search for the named cookbook, and each occurance is copied in the order specified. A syntax check is performed a la `cookbook test`, above. The metadata is generated, a la `cookbook metadata`. A gzip(1)'ed, tar(1) file is created, and is uploaded to the server.
+## TEST
+__knife cookbook test [cookbooks...]__ _(options)_
 
+  * `-a`, `--all`:
+    test all cookbooks, rather than just a single cookbook
+  * `-o`, `--cookbook-path path:path`:
+    a colon-separated path to look for cookbooks in
+
+test the specified cookbooks for syntax errors. this uses the built-in
+ruby syntax checking option for files in the cookbook ending in `.rb`,
+and the erb syntax check for files ending in `.erb` (templates).
+
+## RECIPE LIST
+__knife recipe list [PATTERN]__
+
+List available recipes from the server. Specify _PATTERN_ as a regular
+expression to limit the results.
+
+## DESCRIPTION
+Cookbooks are the fundamental unit of distribution in Chef. They
+encapsulate all recipes of resources and assets used to configure a
+particular aspect of the infrastructure. The following sub-commands can
+be used to manipulate the cookbooks stored on the Chef Server.
+
+On disk, cookbooks are directories with a defined structure. The
+following directories may appear within a cookbook:
+
+  * COOKBOOK/attributes/:
+    Ruby files that define default parameters to be used in recipes
+  * COOKBOOK/definitions/:
+    Ruby files that contain _resource definitions_
+  * COOKBOOK/files/SPECIFICITY:
+    Files of arbitrary type. These files may be downloaded by
+    chef-client(8) when configuring a host.
+  * COOKBOOK/libraries/:
+    Ruby files that contain library code needed for recipes
+  * COOKBOOK/providers/:
+    Ruby files that contain Lightweight Provider definitions
+  * COOKBOOK/recipes/:
+    Ruby files that use Chef's recipe DSL to describe the desired
+    configuration of a system
+  * COOKBOOK/resources/:
+    Ruby files that contain Lightweight Resource definitions
+  * COOKBOOK/templates/SPECIFICITY:
+    ERuby (ERb) template files. These are referenced by _recipes_ and
+    evaluated to dynamically generate configuration files.
+
+__SPECIFICITY__ is a feature of _files_ and _templates_ that allow you
+to specify alternate files to be used on a specific OS platform or host.
+The default specificity setting is _default_, that is files in
+`COOKBOOK/files/default` will be used when a more specific copy is not
+available. Further documentation for this feature is available on the
+Chef wiki: <http://wiki.opscode.com/display/chef/File+Distribution#FileDistribution-FileSpecificity>
+
+Cookbooks also contain a metadata file that defines various properties
+of the cookbook. The most important of these are the _version_ and the
+_dependencies_. The _version_ is used in combination with environments
+to select which copy of a given cookbook is distributed to a node. The
+_dependencies_ are used by the server to determine which additional
+cookbooks must be distributed to a given host when it requires a
+cookbook.
+
+## SEE ALSO
+   __knife-environment(1)__ __knife-cookbook-site(1)__
+   <http://wiki.opscode.com/display/chef/Cookbooks>
+   <http://wiki.opscode.com/display/chef/Metadata>
+
+## AUTHOR
+   Chef was written by Adam Jacob <adam@opscode.com> with many contributions from the community.
+
+## DOCUMENTATION
+   This manual page was written by Joshua Timberman <joshua@opscode.com>.
+   Permission is granted to copy, distribute and / or modify this document under the terms of the Apache 2.0 License.
+
+
+## CHEF
+   Knife is distributed with Chef. <http://wiki.opscode.com/display/chef/Home>