microwave 1.0.2 → 1.0.3

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

@@ -1,121 +0,0 @@
-chef-server(8) - Start the Chef Server merb application slice.
-========================================
-
-## SYNOPSIS
-
-__chef-server__ _(options)_
-
-  * `-u`, `--user USER`:
-    This  flag  is  for having chef-server-webui run as a user other than the
-    one currently logged in. Note: if you set this you must also provide a
-    --group option for it to take effect.
-  * `-G`, `--group GROUP`:
-    This flag is for having chef-server-webui run as a group other than the
-    one currently logged in. Note: if you set this you  must also provide a
-    --user option for it to take effect.
-  * `-d`, `--daemonize`:
-    This will run a single chef-server-webui in the background.
-  * `-N`, `--no-daemonize`:
-    This will allow you to run a cluster in console mode.
-  * `-c`, `--cluster-nodes NUM_MERBS`:
-    Number of merb daemons to run for chef-server-webui.
-  * `-I`, `--init-file FILE`:
-    File to use for initialization on load, defaults to config/init.rb.
-  * `-p`, `--port PORTNUM`:
-    Port to run chef-server-webui on, defaults to 4040. Additional nodes (-c)
-    listen on incrementing port numbers.
-  * `-o`, `--socket-file FILE`:
-    Socket  file  to  run  chef-server-webui on, defaults to
-    [Merb.root]/log/merb.sock. This is for web servers, like thin, that use
-    sockets. Specify this *only* if you *must*.
-  * `-s`, `--socket SOCKNUM`:
-    Socket number to run chef-server-webui on, defaults to 0.
-  * `-n`, `--name NAME`:
-    Set the name of the application. This is used in the process title and
-    log file names.
-  * `-P`, `--pid PIDFILE`:
-    PID file, defaults to [Merb.root]/log/merb.main.pid for the master
-    process and[Merb.root]/log/merb.[port number].pid for  worker processes.
-    For clusters, use %s to specify where in the file chef-server-webui
-    should place the port number. For instance: -P myapp.%s.pid.
-  * `-h`, `--host HOSTNAME`:
-    Host to bind to (default is 0.0.0.0).
-  * `-m`, `--merb-root PATH_TO_APP_ROOT`:
-    The path to the Merb.root for the app you want to run
-    (default is current working directory).
-  * `-a`, `--adapter ADAPTER`:
-    The rack adapter to use to run chef-server-webui (default is mongrel)
-    [mongrel, emongrel, thin, ebb, fastcgi, webrick].
-  * `-R`, `--rackup FILE`:
-    Load an alternate Rack config file (default is config/rack.rb).
-  * `-i`, `--irb-console`:
-    This flag will start chef-server-webui in irb console mode. All your models
-    and other classes will be available for you in an irb session.
-  * `-S`, `--sandbox`:
-    This flag will enable a sandboxed irb console. If your ORM supports
-    transactions, all edits will be rolled back on exit.
-  * `-l`, `--log-level LEVEL`:
-    Log levels can be set to any of these options:
-    debug < info < warn < error < fatal (default is info).
-  * `-L`, `--log LOGFILE`:
-    A string representing the logfile to use. Defaults to
-    [Merb.root]/log/merb.[main].log for the master process and
-    [Merb.root]/log/merb[port number].logfor worker processes.
-  * `-e`, `--environment STRING`:
-    Environment to run Merb under [development, production, testing]
-    (default is development).
-  * `-r`, `--script-runner ['RUBY CODE'| FULL_SCRIPT_PATH]`:
-    Command-line option to run scripts and/or code in the chef-server-webui
-    app.
-  * `-K`, `-graceful PORT or all`:
-    Gracefully kill chef-server-webui proceses by port number.
-    Use chef-server -K all to gracefully kill all merbs.
-  * `-k`, `--kill PORT`:
-    Force kill one merb worker by port number. This will cause the worker
-    to be respawned.
-  * `--fast-deploy`:
-    Reload the code, but not yourinit.rb or gems.
-  * `-X`, `--mutex on/off`:
-    This flag is for turning the mutex lock on and off.
-  * `-D`, `--debugger`:
-    Run chef-server-webui using rDebug.
-  * `-V`, `--verbose`:
-    Print extra information.
-  * `-C`, `--console-trap`:
-    Enter an irb console on ^C.
-  * `-?`, `-H`, `--help`:
-    Show this help message.
-
-## DESCRIPTION
-
-The Chef Server provides a central point for the distribution of Cookbooks,
-management and authentication of Nodes, and the use of Search. It provides
-a REST API.
-
-The API service is what clients use to interact with the server to manage
-node configuration in Chef. By default, the service is started on port 4000
-as a Merb application slice running with the thin server adapter.
-
-The two methods of interaction with the API for humans are the command-line
-tool Knife and the Management Console. The Chef Client library is used for
-interacting with the API for client nodes.
-
-## SEE ALSO
-
-__chef-client__(8)
-__chef-server-webui__(8)
-__knife__(1)
-
-Full documentation for Chef and chef-server is located on the Chef
-wiki, http://wiki.opscode.com/display/chef/Home.
-
-## 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-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  wiki,
-http://wiki.opscode.com/display/chef/Home.
-
-## 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
-wiki, http://wiki.opscode.com/display/chef/Home.
-
-## 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/debian/etc/default/chef-client

@@ -1,4 +0,0 @@
-LOGFILE=/var/log/chef/client.log
-CONFIG=/etc/chef/client.rb
-INTERVAL=1800
-SPLAY=20

data/distro/debian/etc/default/chef-expander

@@ -1,8 +0,0 @@
-LOGFILE=/var/log/chef/expander.log
-CONFIG=/etc/chef/solr.rb
-USER=chef
-GROUP=chef
-# Sleep to give daemon enough time to fully start or stop.
-DIETIME=5
-STARTTIME=5
-CHEF_EXPANDER_ARGS="-n 1 -i 1"

data/distro/debian/etc/default/chef-server

@@ -1,9 +0,0 @@
-LOGFILE=/var/log/chef/server.log
-CONFIG=/etc/chef/server.rb
-ADAPTER=thin
-PORT=4000
-USER=chef
-GROUP=chef
-# Sleep to give daemon enough time to fully start or stop.
-STARTTIME=10
-DIETIME=5

data/distro/debian/etc/default/chef-server-webui

@@ -1,9 +0,0 @@
-LOGFILE=/var/log/chef/server-webui.log
-CONFIG=/etc/chef/webui.rb
-ADAPTER=thin
-PORT=4040
-USER=chef
-GROUP=chef
-# Sleep to give daemon enough time to fully start or stop.
-STARTTIME=10
-DIETIME=5

data/distro/debian/etc/default/chef-solr

@@ -1,8 +0,0 @@
-LOGFILE=/var/log/chef/solr.log
-CONFIG=/etc/chef/solr.rb
-USER=chef
-GROUP=chef
-# Sleep to give daemon enough time to fully start or stop.
-DIETIME=5
-STARTTIME=5
-MAXTRIES=20

data/distro/debian/etc/init.d/chef-client

@@ -1,210 +0,0 @@
-#! /bin/sh
-### BEGIN INIT INFO
-# Provides:           chef-client
-# Required-Start:     $remote_fs $network
-# Required-Stop:      $remote_fs $network
-# Default-Start:      2 3 4 5
-# Default-Stop:       0 1 6
-# Short-Description:  Start a chef-client.
-### END INIT INFO
-#
-# Copyright (c) 2009-2010 Opscode, Inc, <legal@opscode.com>
-#
-# chef-client         Startup script for chef-client.
-# chkconfig: - 99 02
-# description: starts up chef-client in daemon mode.
-
-PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
-DAEMON=$(which chef-client)
-NAME=chef-client
-DESC=chef-client
-PIDFILE=/var/run/chef/client.pid
-
-test -x $DAEMON || exit 0
-
-. /lib/lsb/init-functions
-
-[ -r /etc/default/$NAME ] && . /etc/default/$NAME
-
-if [ ! -d /var/run/chef ]; then
-  mkdir /var/run/chef
-fi
-
-DAEMON_OPTS="-d -P $PIDFILE -c $CONFIG -i $INTERVAL -s $SPLAY"
-
-if [ ! -z $LOGFILE ]; then
-  DAEMON_OPTS="${DAEMON_OPTS} -L $LOGFILE"
-fi
-
-running_pid() {
-  pid=$1
-  name=$2
-  [ -z "$pid" ] && return 1
-  [ ! -d /proc/$pid ] &&  return 1
-  cmd=`awk '/Name:/ {print $2}' /proc/$pid/status`
-  [ "$cmd" != "$name" ] &&  return 1
-  return 0
-}
-
-running() {
-  [ ! -f "$PIDFILE" ] && return 1
-  pid=`cat $PIDFILE`
-  running_pid $pid $NAME || return 1
-  return 0
-}
-
-start_server() {
-  if [ -z "$DAEMONUSER" ] ; then
-    start_daemon -p $PIDFILE $DAEMON $DAEMON_OPTS
-  errcode=$?
-  else
-    start-stop-daemon --start --quiet --pidfile $PIDFILE \
-      --chuid $DAEMONUSER \
-      --exec $DAEMON -- $DAEMON_OPTS
-    errcode=$?
-  fi
-  return $errcode
-}
-
-stop_server() {
-   if [ -z "$DAEMONUSER" ] ; then
-     killproc -p $PIDFILE $DAEMON
-     errcode=$?
-   else
-     start-stop-daemon --stop --quiet --pidfile $PIDFILE \
-       --user $DAEMONUSER \
-       --exec $DAEMON
-     errcode=$?
-   fi
-   return $errcode
-}
-
-reload_server() {
-  if [ -z "$DAEMONUSER" ] ; then
-     killproc -p $PIDFILE $DAEMON -HUP
-     errcode=$?
-   else
-     start-stop-daemon --stop --signal HUP --quiet --pidfile $PIDFILE \
-       --user $DAEMONUSER \
-       --exec $DAEMON
-     errcode=$?
-   fi
-   return $errcode
-}
-
-run_server() {
-  if [ -z "$DAEMONUSER" ] ; then
-     killproc -p $PIDFILE $DAEMON -USR1
-     errcode=$?
-   else
-     start-stop-daemon --stop --signal USR1 --quiet --pidfile $PIDFILE \
-       --user $DAEMONUSER \
-       --exec $DAEMON
-     errcode=$?
-   fi
-   return $errcode
-}
-
-force_stop() {
-  [ ! -e "$PIDFILE" ] && return
-  if running ; then
-    /bin/kill -15 $pid
-    sleep "$DIETIME"s
-    if running ; then
-      /bin/kill -9 $pid
-      sleep "$DIETIME"s
-      if running ; then
-        echo "Cannot kill $NAME (pid=$pid)!"
-        exit 1
-      fi
-    fi
-  fi
-  rm -f $PIDFILE
-}
-
-case "$1" in
-  start)
-    log_daemon_msg "Starting $DESC " "$NAME"
-    if running ;  then
-        log_progress_msg "apparently already running"
-        log_end_msg 0
-        exit 0
-    fi
-    if start_server ; then
-        [ -n "$STARTTIME" ] && sleep $STARTTIME # Wait some time
-        if  running ;  then
-            log_end_msg 0
-        else
-            log_end_msg 1
-        fi
-    else
-        log_end_msg 1
-    fi
-    ;;
-  stop)
-    log_daemon_msg "Stopping $DESC" "$NAME"
-    if running ; then
-      errcode=0
-      stop_server || errcode=$?
-      log_end_msg $errcode
-    else
-      log_progress_msg "apparently not running"
-      log_end_msg 0
-      exit 0
-    fi
-    ;;
-  force-stop)
-    $0 stop
-    if running; then
-      log_daemon_msg "Stopping (force) $DESC" "$NAME"
-      errcode=0
-      force_stop || errcode=$?
-      log_end_msg $errcode
-    fi
-    ;;
-  restart|force-reload)
-    log_daemon_msg "Restarting $DESC" "$NAME"
-    errcode=0
-    stop_server || errcode=$?
-    [ -n "$DIETIME" ] && sleep $DIETIME
-    start_server || errcode=$?
-    [ -n "$STARTTIME" ] && sleep $STARTTIME
-    running || errcode=$?
-    log_end_msg $errcode
-    ;;
-  status)
-    log_daemon_msg "Checking status of $DESC" "$NAME"
-    if running ;  then
-      log_progress_msg "running"
-      log_end_msg 0
-    else
-      log_progress_msg "apparently not running"
-      log_end_msg 1
-      exit 3
-    fi
-    ;;
-  reload)
-    if running; then
-      log_daemon_msg "Reloading $DESC" "$NAME"
-      errcode=0
-      reload_server || errcode=$?
-      log_end_msg $errcode
-    fi
-    ;;
-  run)
-    if running; then
-      log_daemon_msg "Triggering run of $DESC" "$NAME"
-      errcode=0
-      run_server || errcode=$?
-      log_end_msg $errcode
-    fi
-    ;;
-  *)
-    N=/etc/init.d/$NAME
-    echo "Usage: $N {start|stop|force-stop|restart|force-reload|status|run}" >&2
-    exit 1
-    ;;
-esac
-
-exit 0
-