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

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

@@ -5,4 +5,147 @@ knife-environment(1) -- Define cookbook policies for the environments in your in
 
 __knife__ __environment__ _sub-command_ _(options)_
 
-## ENVIRONMENT SUBCOMMANDS
+## SUBCOMMANDS
+Environment subcommands follow a basic create, read, update, delete
+(CRUD) pattern. The following subcommands are available:
+
+## CREATE
+__knife environment create__ _environment_ _(options)_
+
+  * `-d`, `--description DESCRIPTION`:
+    The value of the description field.
+
+Create a new environment object on the Chef Server. The envrionment will
+be opened in the text editor for editing prior to creation if the -n
+option is not present.
+
+## DELETE
+__knife environment delete__ _environment_ _(options)_
+
+Destroy an environment on the Chef Server. A prompt for confirmation
+will be displayed if the -y options is not given.
+
+## EDIT
+__knife environment edit__ _environment_ _(options)_
+
+Fetch _environment_ and display it in the text editor for editing. The
+environment will be saved to the Chef Server when the editing session
+exits.
+
+## FROM FILE
+__knife environment from file__ _file_ _(options)_
+
+Create or update an environment from the JSON or Ruby format _file_. See
+__format__ for the proper format of this file.
+
+## LIST
+__knife environment list__ _(options)_
+  * `-w`, `--with-uri`:
+    Show the resource URI for each environment
+
+## SHOW
+__knife environment show__ _environment_ _(options)_
+
+## DESCRIPTION
+Environments provide a means to apply policies to hosts in your
+infrastructure based on business function. For example, you may have a
+separate copy of your infrastructure called "dev" that runs the latest
+version of your application and should use the newest versions of your
+cookbooks when configuring systems, and a production instance of your
+infrastructure where you wish to update code and cookbooks in a more
+controlled fashion. In Chef, this function is implemented with
+_environments_.
+
+Environments contain two major components: a set of cookbook version
+constraints and environment attributes.
+
+## SYNTAX
+A cookbook version constraint is comprised of a _cookbook name_ and a
+_version constraint_. The _cookbook name_ is the name of a cookbook in
+your system, and the _version constraint_ is a String describing the
+version(s) of that cookbook allowed in the environment.  Only one
+_version constraint_ is supported for a given _cookbook name_.
+
+The exact syntax used to define a cookbook version constraint varies
+depending on whether you use the JSON format or the Ruby format. In the
+JSON format, the cookbook version constraints for an environment are
+represented as a single JSON object, like this:
+
+    {"apache2": ">= 1.5.0"}
+
+In the Ruby format, the cookbook version contraints for an environment
+are represented as a Ruby Hash, like this:
+
+    {"apache2" => ">= 1.5.0"}
+
+A _version number_ is a String comprised of two or three digits
+separated by a dot (.) character, or in other words, strings of the form
+"major.minor" or "major.minor.patch". "1.2" and "1.2.3" are examples of
+valid version numbers. Version numbers containing more than three digits
+or alphabetic characters are not supported.
+
+A _version constraint_ String is composed of an _operator_ and a
+_version number_. The following operators are available:
+
+  * `= VERSION`:
+    Equality. Only the exact version specified may be used.
+  * `> VERSION`:
+    Greater than. Only versions greater than `VERSION` may be used.
+  * `>= VERSION`:
+    Greater than or equal to. Only versions equal to VERSION or greater
+    may be used.
+  * `< VERSION`:
+    Less than. Only versions less than VERSION may be used.
+  * `<= VERSION`:
+    Less than or equal to. Only versions lesser or equal to VERSION may
+    be used.
+  * `~> VERSION`:
+    Pessimistic greater than. Depending on the number of components in
+    the given VERSION, the constraint will be optimistic about future
+    minor or patch revisions only. For example, `~> 1.1` will match any
+    version less than `2.0` and greater than or equal to `1.1.0`,
+    whereas `~> 2.0.5` will match any version less than `2.1.0` and
+    greater than or equal to `2.0.5`.
+
+## FORMAT
+The JSON format of an envioronment is as follows:
+
+    {
+      "name": "dev",
+      "description": "The development environment",
+      "cookbook_versions": {
+        "couchdb": "= 11.0.0"
+      },
+      "json_class": "Chef::Environment",
+      "chef_type": "environment",
+      "default_attributes": {
+        "apache2": { "listen_ports": [ "80", "443" ] }
+      },
+      "override_attributes": {
+        "aws_s3_bucket": "production"
+      }
+    }
+
+The Ruby format of an environment is as follows:
+
+    name "dev"
+    description "The development environment"
+    cookbook_versions  "couchdb" => "= 11.0.0"
+    default_attributes "apache2" => { "listen_ports" => [ "80", "443" ] }
+    override_attributes "aws_s3_bucket" => "production"
+
+
+## SEE ALSO
+   __knife-node(1)__ __knife-cookbook(1)__ __knife-role(1)__
+  <http://wiki.opscode.com/display/chef/Environments>
+  <http://wiki.opscode.com/display/chef/Version+Constraints>
+
+## AUTHOR
+   Chef was written by Adam Jacob <adam@opscode.com> with many contributions from the community.
+
+## DOCUMENTATION
+   This manual page was written by Daniel DeLeo <dan@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>

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

@@ -5,5 +5,33 @@ knife-exec(1) -- Run user scripts using the Chef API DSL
 
 __knife__ __exec__ _(options)_
 
-## EXEC SUBCOMMAND
+  * `-E`, `--exec CODE`:
+    Provide a snippet of code to evaluate on the command line
+
+## DESCRIPTION
+`knife exec` runs arbitrary ruby scripts in a context similar to that of
+the shef(1) DSL. See the shef documentation for a description of the
+commands available.
+
+## EXAMPLES
+  * Make an API call against an arbitrary endpoint:
+    knife exec -E 'api.get("nodes/fluke.localdomain/cookbooks")'  
+    => list of cookbooks for the node _fluke.localdomain_
+  * Remove the role _obsolete_ from all nodes:
+    knife exec -E 'nodes.transform(:all){|n| n.run\_list.delete("role[obsolete]")}'
+  * Generate the expanded run list for hosts in the `webserver` role:
+    knife exec -E 'nodes.find(:roles => "webserver") {|n| n.expand!; n[:recipes]}'
+
+## SEE ALSO
+   __shef(1)__
+
+## 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>
 

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

@@ -28,7 +28,7 @@ host for the node name, though this may be overridden by configuration
 settings.
 
 ## NODE SUB-COMMANDS
-
+The following `node` subcommands are available:
 
 ## BULK DELETE
 __knife node bulk delete__ _regex_ _(options)_

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

@@ -5,29 +5,26 @@ knife-role(1) -- Group common configuration settings
 
 __knife__ __role__ _sub-command_ _(options)_
 
-## DESCRIPTION
-Roles provide a mechanism to group repeated configuration settings.
-Roles are data structures that contain __default\_attributes__, and
-__override_attributes__, which are nested hashes of configuration
-settings, and a __run_list__, which is an ordered list of recipes and
-roles that should be applied to a host by chef-client.
+## ROLE SUB-COMMANDS
+The following `role` subcommands are available:
 
-__default_attributes__ will be overridden if they conflict with a value
-on a node that includes the role. Conversely, __override_attributes__
-will override any values set on nodes that apply them.
+## LIST
+__knife role list__ _(options)_
 
-When __chef-client__(8) configures a host, it will "expand" the
-__run_list__ included in that host's node data. The expansion process
-will recursively replace any roles in the run\_list with that role's
-run\_list.
+  * `-w`, `--with-uri`:
+    Show corresponding URIs
 
+List roles.
 
-## ROLE SUB-COMMANDS
+## SHOW
+__knife role show ROLE__ _(options)_
 
-__knife role bulk delete REGEX__ _(options)_
+  * `-a`, `--attribute ATTR`:
+    Show only one attribute
 
-Delete roles on the Chef Server based on a regular expression. The regular expression (_REGEX_) should be in quotes, not in //'s.
+Show a specific role.
 
+## CREATE
 __knife role create ROLE__ _(options)_
 
   * `-d`, `--description`:
@@ -35,36 +32,45 @@ __knife role create ROLE__ _(options)_
 
 Create a new role.
 
-__knife role delete ROLE__ _(options)_
-
-Delete a role.
-
+## EDIT
 __knife role edit ROLE__ _(options)_
 
 Edit a role.
 
+## FROM FILE
 __knife role from file FILE__ _(options)_
 
 Create or update a role from a role Ruby DSL (`.rb`) or JSON file.
 
-__knife role list__ _(options)_
+## DELETE
+__knife role delete ROLE__ _(options)_
 
-  * `-w`, `--with-uri`:
-    Show corresponding URIs
+Delete a role.
 
-List roles.
+## BULK DELETE
+__knife role bulk delete REGEX__ _(options)_
 
-__knife role show ROLE__ _(options)_
+Delete roles on the Chef Server based on a regular expression. The regular expression (_REGEX_) should be in quotes, not in //'s.
 
-  * `-a`, `--attribute ATTR`:
-    Show only one attribute
+## DESCRIPTION
+Roles provide a mechanism to group repeated configuration settings.
+Roles are data structures that contain __default\_attributes__, and
+__override_attributes__, which are nested hashes of configuration
+settings, and a __run_list__, which is an ordered list of recipes and
+roles that should be applied to a host by chef-client.
 
-Show a specific role.
+__default_attributes__ will be overridden if they conflict with a value
+on a node that includes the role. Conversely, __override_attributes__
+will override any values set on nodes that apply them.
 
+When __chef-client__(8) configures a host, it will "expand" the
+__run_list__ included in that host's node data. The expansion process
+will recursively replace any roles in the run\_list with that role's
+run\_list.
 
 ## SEE ALSO
-   __knife-node__(1)
-
+   __knife-node(1)__ __knife-environment(1)__
+   <http://wiki.opscode.com/display/chef/Roles>
    <http://wiki.opscode.com/display/chef/Attributes>
 
 ## AUTHOR

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

@@ -40,7 +40,6 @@ query syntax. The following data types are indexed for search:
 
 ## SEE ALSO
    __knife-ssh__(1)
-
    <http://wiki.opscode.com/display/chef/Attributes>
 
 ## AUTHOR

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

@@ -49,8 +49,6 @@ The available multiplexers are:
 ## SEE ALSO
    __knife-search__(1)
 
-   <http://wiki.opscode.com/display/chef/Attributes>
-
 ## AUTHOR
    Chef was written by Adam Jacob <adam@opscode.com> with many contributions from the community.
 

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

@@ -23,8 +23,6 @@ may not be publicly reachable.
 ## SEE ALSO
    __knife-search__(1)
 
-   <http://wiki.opscode.com/display/chef/Attributes>
-
 ## AUTHOR
    Chef was written by Adam Jacob <adam@opscode.com> with many contributions from the community.
 

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

@@ -6,3 +6,34 @@ knife-tag(1) -- Apply tags to nodes on a Chef Server
 __knife__ __tag__ _subcommand_ _(options)_
 
 ## TAG SUBCOMMANDS
+The following `tag` subcommands are available:
+
+## CREATE
+__knife tag create__ _node_ _tag_ [_..._]
+
+Adds one or more tags to _node_
+
+## DELETE
+__knife tag delete__ _node_ _tag_ [_..._]
+
+Removes one or more tags from _node_
+
+## LIST
+__knife tag list__ _node_
+
+Lists the tags applied to _node_
+
+
+## SEE ALSO
+   __knife-node(1)__
+
+## AUTHOR
+   Chef was written by Adam Jacob <adam@opscode.com> with many contributions from the community.
+
+## DOCUMENTATION
+   This manual page was written by Daniel DeLeo <dan@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>
+

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

@@ -1,28 +1,39 @@
-knife(1) -- Chef Server REST API utility
+knife(1) -- Chef Server API client utility
 ========================================
 
 ## SYNOPSIS
 
-__knife__ _sub-command_ _(options)_
+__knife__ _sub-command_ [_argument_...] _(options)_
 
 ## DESCRIPTION
 
-This manual page documents knife, a command-line utility used to
-interact with a Chef server directly through the RESTful API. Knife uses
-sub-commands to take various actions on different types of Chef objects.
-Some sub-commands take additional options. General options follow
-sub-commands and their options. A configuration file can be created for
-common defaults.
-
-Unless otherwise specified, output is in JSON format, and input files
-are also JSON format.
-
-The Chef class `Chef::Config` that configures the behavior of how knife
-runs has options that correspond to command-line options. These are
-noted as `Chef::Config` values.
-
-## GENERAL OPTIONS
-
+Knife is a command-line utility used to manage data on a Chef server
+through the HTTP(S) API. Knife is organized into groups of subcommands
+centered around the various object types in Chef. Each category of
+subcommand is documented in its own manual page. Available topics are:
+
+  * bootstrap
+  * client
+  * configure
+  * cookbook-site
+  * cookbook
+  * data-bag
+  * environment
+  * exec
+  * index
+  * node
+  * recipe
+  * role
+  * search
+  * ssh
+  * status
+  * tag
+
+If the knife manuals are in your `MANPATH`, you can access help for the
+above topics using `man knife-TOPIC`; otherwise, you can view the
+documentation using `knife help TOPIC`.
+
+## OPTIONS
   * `-s`, `--server-url` URL:
     Chef Server URL, corresponds to `Chef::Config` `chef_server_url`.
   * `-k`, `--key` KEY:
@@ -48,29 +59,21 @@ noted as `Chef::Config` values.
   * `-y`, `--yes`:
     Say yes to all prompts for confirmation
   * `-h`, `--help`:
-    Show this message
-
-Usage information for sub-commands can be displayed with `knife SUB-COMMAND --help`.
+    Show the available options for a command.
 
 ## SUB-COMMANDS
 
-Knife sub-commands are structured as _NOUN verb NOUN (options)_. The
-sub-commands are meant to be intuitively named. Because the Chef Server
-API is RESTful, sub-commands generally utilize CRUD operations.
+Sub-commands that operate on the basic Chef data types are structured as
+_NOUN verb NOUN (options)_. For all data types, the following commands
+are available:
 
 * create (create)
 * list and show (read)
 * edit (update)
 * delete (destroy)
 
-Objects stored on the server support these, as described below.
-
-## GENERAL SUB-COMMANDS
-
-__recipe list [PATTERN]__
-
-List available recipes from the server. Specify _PATTERN_ as a regular expression to limit the results.
-
+Knife also includes commands that take actions other than displaying or
+modifying data on the Chef Server, such as __knife-ssh(1)__.
 
 ## CONFIGURATION
 
@@ -82,94 +85,40 @@ be `.chef/knife.rb` in the current directory of the repository.
 
 If the config file exists, knife uses these settings for __GENERAL OPTIONS__ defaults.
 
-`log_level`
-
-A Ruby symbol specifying the log level. Corresponds to `-l` or `--log_level` option. Default is _:info_. Valid values are:
-
-  * :info
-  * :debug
-  * :warn
-  * :fatal
-
-`log_location`
-
-Corresponds to the `-L` or `--log-file` option. Defaults is __STDOUT__.
-Valid values are __STDOUT__ or a filename.
-
-`node_name`
-
-User to authenticate to the Chef server. Corresponds to the `-u` or
-`--user` option. This is requested from the user when running this
-sub-command.
-
-`client_key`
-
-Private key file to authenticate to the Chef server. Corresponds to the
-`-k` or `--key` option. This is requested from the user when running
-this sub-command.
-
-`chef_server_url`
-
-URL of the Chef server. Corresponds to the `-s` or `--server-url`
-option. This is requested from the user when running this sub-command.
-
-`cache_type`
-
-The type of cache to use. Default is BasicFile. This can be any type of
-Cache that moneta supports: BasicFile, Berkeley, Couch, DataMapper,
-File, LMC, Memcache, Memory, MongoDB, Redis, Rufus, S3, SDBM, Tyrant,
-Xattr, YAML.
-
-`cache_options`
-
-Specifies various options to use for caching. Default reads the Chef
-client configuration (/etc/chef/checksums).
-
-`validation_client_name`
-
-Specifies the name of the client used to validate new clients. This is
-requested from the user when running the configuration sub-command.
-
-`validation_key`
-
-Specifies the private key file to use for generating ec2 instance data
-for validating new clients. This is implied from the
-`validation_client_name`.
-
-`cookbook_copyright`
-`cookbook_email`
-`cookbook_license`
-
-Used by `knife cookbook create` sub-command to specify the copyright
-holder, maintainer email and license (respectively) for new cookbooks.
-The copyright holder is listed as the maintainer in the cookbook's
-metadata and as the Copyright in the comments of the default recipe. The
-maintainer email is used in the cookbook metadata. The license
-determines what preamble to put in the comment of the default recipe,
-and is listed as the license in the cookbook metadata. Currently
-supported licenses are "apachev2" and "none". Any other values will
-result in an empty license in the metadata (needs to be filled in by the
-author), and no comment preamble in the default recipe.
-
-`knife[:aws_access_key_id]`
-`knife[:aws_secret_access_key]`
-
-Specifies the Amazon AWS EC2 credentials to use when running the ec2 sub-commands.
-
-`knife[:rackspace_api_username]`
-`knife[:rackspace_api_key]`
-
-Specifies the Rackspace Cloud credentials to use when running the rackspace sub-commands.
-
-`knife[:terremark_username]`
-`knife[:terremark_password]`
-`knife[:terremark_service]`
-
-Specifies the Terremark vCloud credentials to use when running the terremark sub-commands.
-
-`knife[:slicehost_password]`
-
-Specifies the Slicehost password to use when running the slicdehost sub-commands.
+  * `node_name`:
+    User or client identity (i.e., _name_) to use for authenticating
+    requests to the Chef Server.
+  * `client_key`:
+    Private key file to authenticate to the Chef server. Corresponds to the
+    `-k` or `--key` option.
+  * `chef_server_url`:
+    URL of the Chef server. Corresponds to the `-s` or `--server-url`
+    option. This is requested from the user when running this sub-command.
+  * `cache_type`:
+    The type of cache to use. Default is BasicFile. This can be any type of
+    Cache that moneta supports: BasicFile, Berkeley, Couch, DataMapper,
+    File, LMC, Memcache, Memory, MongoDB, Redis, Rufus, S3, SDBM, Tyrant,
+    Xattr, YAML.
+  * `cache_options`:
+    Specifies various options to use for caching. These options are
+    dependent on the `cache_type`.
+  * `validation_client_name`:
+    Specifies the name of the client used to validate new clients.
+  * `validation_key`:
+    Specifies the private key file to use when bootstrapping new hosts.
+    See knife-client(1) for more information about the validation
+    client.
+  * `cookbook_copyright`, `cookbook_email`, `cookbook_license`
+    Used by `knife cookbook create` sub-command to specify the copyright
+    holder, maintainer email and license (respectively) for new cookbooks.
+    The copyright holder is listed as the maintainer in the cookbook's
+    metadata and as the Copyright in the comments of the default recipe. The
+    maintainer email is used in the cookbook metadata. The license
+    determines what preamble to put in the comment of the default recipe,
+    and is listed as the license in the cookbook metadata. Currently
+    supported licenses are "apachev2" and "none". Any other values will
+    result in an empty license in the metadata (needs to be filled in by the
+    author), and no comment preamble in the default recipe.
 
 ## FILES
 
@@ -197,44 +146,6 @@ recommended though, and git fits with a lot of the workflow paradigms.
 
 ## EXAMPLES
 
-Example client config (`/etc/chef/client.rb`) from `knife configure
-client`. The same configuration is used when using the `knife bootstrap`
-command with the default `gem` templates that come with Chef.
-
-    log_level        :info
-    log_location     STDOUT
-    chef_server_url  'https://api.opscode.com/organizations/ORGNAME'
-    validation_client_name 'ORGNAME-validator'
-
-Setting up a custom bootstrap is fairly straightforward. Create
-`.chef/bootstrap` in your Chef Repository directory 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.
-
-Uploading cookbooks to the Opscode cookbooks site using the user/certificate specifically:
-
-    knife cookbook site share example Other -k ~/.chef/USERNAME.pem -u USERNAME
 
 ## ENVIRONMENT
   * `EDITOR`:
@@ -243,19 +154,36 @@ Uploading cookbooks to the Opscode cookbooks site using the user/certificate spe
     data editing entirely.
 
 ## SEE ALSO
+  __chef-client(8)__ __chef-server(8)__ __shef(1)__
 
-Full documentation for Chef is located on the Chef wiki, http://wiki.opscode.com/display/chef/Home/.
+  __knife-bootstrap(1)__ __knife-client(1)__ __knife-configure(1)__
+  __knife-cookbook-site(1)__ __knife-cookbook(1)__ __knife-data-bag(1)__
+  __knife-environment(1)__ __knife-exec(1)__ __knife-index(1)__
+  __knife-node(1)__ __knife-recipe(1)__ __knife-role(1)__
+  __knife-search(1)__ __knife-ssh(1)__ __knife-tag(1)__
 
-JSON is JavaScript Object Notation and more information can be found at http://json.org/.
+  Complete Chef documentation is available online: <http://wiki.opscode.com/display/chef/Home/>
 
-SOLR is an open source search engine. The Chef Server includes a SOLR installation. More information about SOLR, including the search query syntax, can be found at http://lucene.apache.org/solr/.
+  JSON is JavaScript Object Notation <http://json.org/>
 
-Git is a version control system and documented at http://git-scm.com/.
+  SOLR is an open source search engine. <http://lucene.apache.org/solr/>
 
-This manual page was generated in nroff from Markdown with ronn. Ryan Tomayko wrote ronn and more information can be found at http://rtomayko.github.com/ronn/ronn.5.html.
+  __git(1)__ is a version control system <http://git-scm.com/>
+
+  This manual page was generated from Markdown with __ronn(1)__ <http://rtomayko.github.com/ronn/ronn.1.html>
 
 ## AUTHOR
+   Chef was written by Adam Jacob <adam@opscode.com> of Opscode
+   (<http://www.opscode.com>), with contributions from the community.
+
+## DOCUMENTATION
+   This manual page was written by Joshua Timberman <joshua@opscode.com>.
+
+## LICENSE
+   Both Chef and this documentation are released under the terms of the
+   Apache 2.0 License. You may view the license online: <http://www.apache.org/licenses/LICENSE-2.0.html>
+   On some systems, the complete text of the Apache 2.0 License may be found in `/usr/share/common-licenses/Apache-2.0`.
 
-Chef was written by Adam Jacob <adam@opscode.com> of Opscode (<http://www.opscode.com>), with contributions from the community. 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>
 
-On Debian systems, the complete text of the Apache 2.0 License can be found in `/usr/share/common-licenses/Apache-2.0`.