chef 13.11.3-universal-mingw32 → 13.12.3-universal-mingw32

data/distro/common/markdown/man8/chef-solo.mkd

@@ -1,107 +0,0 @@
-chef-solo(8) -- Runs chef in solo mode against a specified cookbook location.
-========================================
-
-## SYNOPSIS
-
-__chef-solo__ _(options)_
-
-  * `-c`, `--config CONFIG`:
-    The configuration file to use
-  * `-d`, `--daemonize`:
-    Daemonize the process
-  * `-g`, `--group GROUP`:
-    Group to set privilege to
-  * `-i`, `--interval SECONDS`:
-    Run chef-client periodically, in seconds
-  * `-j`, `--json-attributes JSON_ATTRIBS`:
-    Load attributes from a JSON file or URL
-  * `-l`, `--log_level LEVEL`:
-    Set the log level (debug, info, warn, error, fatal)
-  * `-L`, `--logfile LOGLOCATION`:
-    Set the log file location, defaults to STDOUT - recommended for
-    daemonizing
-  * `-N`, `--node-name NODE_NAME`:
-    The node name for this client
-  * `-r`, `--recipe-url RECIPE_URL`:
-    Pull  down  a  remote  gzipped  tarball of recipes and untar it to the
-    cookbook cache.
-  * `-s`, `--splay SECONDS`:
-    The splay time for running at intervals, in seconds
-  * `-u`, `--user USER`:
-    User to set privilege to
-  * `-v`, `--version`:
-    Show chef version
-  * `-h`, `--help`:
-    Show this message
-
-## DESCRIPTION
-
-Chef Solo allows you to run Chef Cookbooks in the absence of a Chef Server.
-To do this, the complete cookbook needs to be present on disk.
-
-By default Chef Solo will look in /etc/chef/solo.rb for its configuration.
-This configuration file has two required variables: file_cache_path and
-cookbook_path.
-
-For example:
-    file_cache_path "/var/chef-solo"
-    cookbook_path "/var/chef-solo/cookbooks"
-
-For your own systems, you can change this to reflect any directory you like,
-but you'll need to specify absolute paths and the cookbook_path directory
-should be a subdirectory of the file_cache_path.
-
-You can also specify cookbook_path as an array, passing multiple locations
-to search for cookbooks.
-
-For example:
-    file_cache_path "/var/chef-solo"
-    cookbook_path ["/var/chef-solo/cookbooks", "/var/chef-solo/site-cookbooks"]
-
-Note that earlier entries are now overridden by later ones.
-
-Since chef-solo doesn't have any interaction with a Chef Server, you'll need
-to specify node-specifc attributes in a JSON file. This can be located on the
-target system itself, or it can be stored on a remote server such as S3, or a
-web server on your network.
-
-Within the JSON file, you'll also specify the recipes that Chef should run in
-the "run_list". An example JSON file, which sets a resolv.conf:
-
-    {
-      "resolver": {
-        "nameservers": [ "10.0.0.1" ],
-        "search":"int.example.com"
-      },
-      "run_list": [ "recipe[resolver]" ]
-    }
-
-Then you can run chef-solo with -j to specify the JSON file. It will look for
-cookbooks in the cookbook_path configured in the configuration file, and apply
-attributes and use the run_list from the JSON file specified.
-
-You can use -c to specify the path to the configuration file (if you don't want
-chef-solo to use the default). You can also specify -r for a cookbook tarball.
-
-For example:
-    chef-solo -c ~/solo.rb -j ~/node.json  -r http://www.example.com/chef-solo.tar.gz
-
-In the above case, chef-solo would extract the tarball to your specified
-cookbook_path, use ~/solo.rb as the configuration file, and apply attributes
-and use the run_list from ~/node.json.
-
-## SEE ALSO
-
-Full documentation for Chef and  chef-solo  is  located  on  the  Chef  docs site,
-http://docs.chef.io/.
-
-## AUTHOR
-
-Chef was written by Adam Jacob <adam@ospcode.com> of Opscode
-(http://www.opscode.com),  with contributions from the community.  This
-manual page was written by Joshua Timberman  <joshua@opscode.com>  with
-help2man.  Permission  is  granted  to copy, distribute and / or modify
-this document under the terms of the Apache 2.0 License.
-
-On Debian systems, the complete text of the Apache 2.0 License  can  be
-found in /usr/share/common-licenses/Apache-2.0.

data/distro/common/markdown/man8/chef-solr.mkd

@@ -1,89 +0,0 @@
-chef-solr(8) -- Runs as Chef's search server
-========================================
-
-## SYNOPSIS
-
-__chef-solr__ _(options)_
-
-  * `-c`, `--config CONFIG`:
-    The configuration file to use
-  * `-d`, `--daemonize`:
-    Daemonize the process
-  * `-g`, `--group GROUP`:
-    Group to set privilege to
-  * `-l`, `--log_level LEVEL`:
-    Set the log level (debug, info, warn, error, fatal)
-  * `-L`, `--logfile LOGLOCATION`:
-    Set the log file location, defaults to STDOUT - recommended for daemonizing
-  * `-P`, `--pid PIDFILE`:
-    Set the PID file location, defaults to /tmp/chef-solr.pid
-  * `-D`, `--solr-data-dir PATH`:
-    Where the Solr data lives
-  * `-x`, `--solor-heap-size SIZE`:
-    Set the size of the Java Heap
-  * `-H`, `--solr-home-dir PATH`:
-    Solr home directory
-  * `-j`, `--java-opts OPTS`:
-    Raw options passed to Java
-  * `-x`, `--solor-heap-size`:
-    Set the size of the Java Heap
-  * `-W`, `--solr-jetty-dir PATH`:
-    Where to place the Solr Jetty instance
-  * `-u`, `--user USER`:
-    User to set privilege to
-  * `-v`, `--version`:
-    Show chef-solr version
-  * `-h`, `--help`:
-    Show this message
-
-## DESCRIPTION
-
-Chef-solr provides search service for Chef. You need to have both
-chef-solr and chef-expander-cluster running in order for search to work.
-
-__Installation__
-
-Make sure you backed up your data if you are upgrading from a previous version.
-Run chef-solr-installer to upgrade your Chef Solr installation. Answer "yes"
-when prompted for confirmation. The process should look like this:
-
-    yourshell> chef-solr-installer
-    Configuration setting solr_heap_size is unknown and will be ignored
-
-    Chef Solr is already installed in /var/chef/solr
-    Do you want to overwrite the current install? All existing Solr data will be lost. [y/n] y
-    Removing the existing Chef Solr installation
-      rm -rf /var/chef/solr
-      rm -rf /var/chef/solr-jetty
-      rm -rf /var/chef/solr/data
-    Creating Solr Home Directory
-      mkdir -p /var/chef/solr
-      entering /var/chef/solr
-      tar zxvf /Users/ddeleo/opscode/chef/chef-solr/solr/solr-home.tar.gz
-    Creating Solr Data Directory
-      mkdir -p /var/chef/solr/data
-    Unpacking Solr Jetty
-      mkdir -p /var/chef/solr-jetty
-      entering /var/chef/solr-jetty
-      tar zxvf /Users/ddeleo/opscode/chef/chef-solr/solr/solr-jetty.tar.gz
-
-    Successfully installed Chef Solr.
-    You can restore your search index using `knife index rebuild`
-
-## SEE ALSO
-
-__chef-expander-cluster__(8)
-
-Full documentation for Chef and chef-server is located on the Chef
-Docs site, http://docs.chef.io/.
-
-## AUTHOR
-
-Chef was written by Adam Jacob <adam@ospcode.com> of Opscode
-(http://www.opscode.com),  with contributions from the community.  This
-manual page was written by Joshua Timberman  <joshua@opscode.com>  with
-help2man.  Permission  is  granted  to copy, distribute and / or modify
-this document under the terms of the Apache 2.0 License.
-
-On Debian systems, the complete text of the Apache 2.0 License  can  be
-found in /usr/share/common-licenses/Apache-2.0.

data/tasks/cbgb.rb

@@ -1,84 +0,0 @@
-#
-# Author:: Thom May (tmay@chef.io)
-# Author:: Nathen Harvey (nharvey@chef.io)
-# Copyright:: Copyright 2015-2016, Chef Software, Inc
-# License:: Apache License, Version 2.0
-#
-# 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
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-
-require "rake"
-
-CBGB_SOURCE = File.join(File.dirname(__FILE__), "..", "CBGB.toml")
-CBGB_TARGET = File.join(File.dirname(__FILE__), "..", "CBGB.md")
-
-begin
-  require "tomlrb"
-
-  task :default => :generate
-
-  namespace :cbgb do
-    desc "Generate MarkDown version of CBGB file"
-    task :generate do
-      cbgb = Tomlrb.load_file CBGB_SOURCE
-      out = "<!-- This is a generated file. Please do not edit directly -->\n"
-      out << "<!-- Modify CBGB.toml file and run `rake cbgb:generate` to regenerate -->\n\n"
-      out << "# " + cbgb["Preamble"]["title"] + "\n\n"
-      out << cbgb["Preamble"]["text"] + "\n"
-      out << "# Board of Governors\n\n"
-      out << "## " + cbgb["Org"]["Lead"]["title"] + "\n\n"
-      out << person(cbgb["people"], cbgb["Org"]["Lead"]["person"]) + "\n\n"
-      out << "### " + cbgb["Org"]["Contributors"]["title"] + "\n\n"
-      out << cbgb(cbgb["people"], cbgb["Org"]["Contributors"]["governers"]) + "\n\n"
-      out << "### " + cbgb["Org"]["Corporate-Contributors"]["title"] + "\n\n"
-      out << cbgb(cbgb["corporations"], cbgb["Org"]["Corporate-Contributors"]["governers"]) + "\n\n"
-      out << "### " + cbgb["Org"]["Lieutenants"]["title"] + "\n\n"
-      out << cbgb(cbgb["people"], cbgb["Org"]["Lieutenants"]["governers"]) + "\n\n"
-      File.open(CBGB_TARGET, "w") do |fn|
-        fn.write out
-      end
-    end
-  end
-
-  def components(list, cmp)
-    out = ""
-    cmp.each do |k, v|
-      out << "\n#### #{v['title'].gsub('#', '\\#')}\n"
-      out << cbgb(list, v["cbgb"])
-    end
-    out
-  end
-
-  def cbgb(list, people)
-    o = ""
-    people.each do |p|
-      o << person(list, p) + "\n"
-    end
-    o
-  end
-
-  def person(list, person)
-    if list[person].has_key?("GitHub")
-      out = "* [#{list[person]["Name"]}](https://github.com/#{list[person]["GitHub"]})"
-    else
-      out =  "* #{list[person]["Name"]}"
-    end
-    if list[person].has_key?("Person")
-      out << " - #{list[person]["Person"]}"
-    end
-    out
-  end
-
-rescue LoadError
-  STDERR.puts "\n*** TomlRb not available.\n\n"
-end