rmm-chef 0.10.0.rc.0

data/distro/common/man/man8/chef-server-webui.8

@@ -0,0 +1,155 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CHEF\-SERVER\-WEBUI" "8" "April 2011" "Chef 0.10.0.rc.0" "Chef Manual"
+.
+.SH "NAME"
+\fBchef\-server\-webui\fR \- Start the Chef Server merb application slice providing Web User Interface (Management Console)\.
+.
+.SH "SYNOPSIS"
+\fBchef\-server\-webui\fR \fI(options)\fR
+.
+.TP
+\fB\-u\fR, \fB\-\-user USER\fR
+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\.
+.
+.TP
+\fB\-G\fR, \fB\-\-group GROUP\fR
+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\.
+.
+.TP
+\fB\-d\fR, \fB\-\-daemonize\fR
+This will run a single chef\-server\-webui in the background\.
+.
+.TP
+\fB\-N\fR, \fB\-\-no\-daemonize\fR
+This will allow you to run a cluster in console mode\.
+.
+.TP
+\fB\-c\fR, \fB\-\-cluster\-nodes NUM_MERBS\fR
+Number of merb daemons to run for chef\-server\-webui\.
+.
+.TP
+\fB\-I\fR, \fB\-\-init\-file FILE\fR
+File to use for initialization on load, defaults to config/init\.rb\.
+.
+.TP
+\fB\-p\fR, \fB\-\-port PORTNUM\fR
+Port to run chef\-server\-webui on, defaults to 4040\. Additional nodes (\-c) listen on incrementing port numbers\.
+.
+.TP
+\fB\-o\fR, \fB\-\-socket\-file FILE\fR
+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 \fIonly\fR if you \fImust\fR\.
+.
+.TP
+\fB\-s\fR, \fB\-\-socket SOCKNUM\fR
+Socket number to run chef\-server\-webui on, defaults to 0\.
+.
+.TP
+\fB\-n\fR, \fB\-\-name NAME\fR
+Set the name of the application\. This is used in the process title and log file names\.
+.
+.TP
+\fB\-P\fR, \fB\-\-pid PIDFILE\fR
+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\.
+.
+.TP
+\fB\-h\fR, \fB\-\-host HOSTNAME\fR
+Host to bind to (default is 0\.0\.0\.0)\.
+.
+.TP
+\fB\-m\fR, \fB\-\-merb\-root PATH_TO_APP_ROOT\fR
+The path to the Merb\.root for the app you want to run (default is current working directory)\.
+.
+.TP
+\fB\-a\fR, \fB\-\-adapter ADAPTER\fR
+The rack adapter to use to run chef\-server\-webui (default is mongrel) [mongrel, emongrel, thin, ebb, fastcgi, webrick]\.
+.
+.TP
+\fB\-R\fR, \fB\-\-rackup FILE\fR
+Load an alternate Rack config file (default is config/rack\.rb)\.
+.
+.TP
+\fB\-i\fR, \fB\-\-irb\-console\fR
+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\.
+.
+.TP
+\fB\-S\fR, \fB\-\-sandbox\fR
+This flag will enable a sandboxed irb console\. If your ORM supports transactions, all edits will be rolled back on exit\.
+.
+.TP
+\fB\-l\fR, \fB\-\-log\-level LEVEL\fR
+Log levels can be set to any of these options: debug < info < warn < error < fatal (default is info)\.
+.
+.TP
+\fB\-L\fR, \fB\-\-log LOGFILE\fR
+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\.
+.
+.TP
+\fB\-e\fR, \fB\-\-environment STRING\fR
+Environment to run Merb under [development, production, testing] (default is development)\.
+.
+.TP
+\fB\-r\fR, \fB\-\-script\-runner [\'RUBY CODE\'| FULL_SCRIPT_PATH]\fR
+Command\-line option to run scripts and/or code in the chef\-server\-webui app\.
+.
+.TP
+\fB\-K\fR, \fB\-graceful PORT or all\fR
+Gracefully kill chef\-server\-webui proceses by port number\. Use chef\-server \-K all to gracefully kill all merbs\.
+.
+.TP
+\fB\-k\fR, \fB\-\-kill PORT\fR
+Force kill one merb worker by port number\. This will cause the worker to be respawned\.
+.
+.TP
+\fB\-\-fast\-deploy\fR
+Reload the code, but not yourinit\.rb or gems\.
+.
+.TP
+\fB\-X\fR, \fB\-\-mutex on/off\fR
+This flag is for turning the mutex lock on and off\.
+.
+.TP
+\fB\-D\fR, \fB\-\-debugger\fR
+Run chef\-server\-webui using rDebug\.
+.
+.TP
+\fB\-V\fR, \fB\-\-verbose\fR
+Print extra information\.
+.
+.TP
+\fB\-C\fR, \fB\-\-console\-trap\fR
+Enter an irb console on ^C\.
+.
+.TP
+\fB\-?\fR, \fB\-H\fR, \fB\-\-help\fR
+Show this help message\.
+.
+.SH "DESCRIPTION"
+The Chef Server WebUI (Management Console) is a Merb application slice\. The default listen port is 4040\.
+.
+.P
+The Management Console is Chef Server\'s web interface\. Nodes, roles, cookbooks, data bags, and API clients can be managed through the Management Console\. Search can also be done on the console\.
+.
+.P
+In order to start using the Management Console, you need to first create a user or change the default password on the "admin" user\.
+.
+.P
+The default credentials are:
+.
+.IP "\(bu" 4
+\fBUsername\fR: admin
+.
+.IP "\(bu" 4
+\fBPassword\fR: p@ssw0rd1
+.
+.IP "" 0
+.
+.SH "SEE ALSO"
+Full documentation for Chef and chef\-server\-webui (Management Console) is located on the Chef wiki, http://wiki\.opscode\.com/display/chef/Home\.
+.
+.SH "AUTHOR"
+Chef was written by Adam Jacob \fIadam@ospcode\.com\fR of Opscode (http://www\.opscode\.com), with contributions from the community\. This manual page was written by Joshua Timberman \fIjoshua@opscode\.com\fR with help2man for the Debian project (but may be used by others)\. Permission is granted to copy, distribute and / or modify this document under the terms of the Apache 2\.0 License\.
+.
+.P
+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/man/man8/chef-server.8

@@ -0,0 +1,147 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CHEF\-SERVER" "8" "April 2011" "Chef 0.10.0.rc.0" "Chef Manual"
+.
+.SH "NAME"
+\fBchef\-server\fR \- Start the Chef Server merb application slice\.
+.
+.SH "SYNOPSIS"
+\fBchef\-server\fR \fI(options)\fR
+.
+.TP
+\fB\-u\fR, \fB\-\-user USER\fR
+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\.
+.
+.TP
+\fB\-G\fR, \fB\-\-group GROUP\fR
+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\.
+.
+.TP
+\fB\-d\fR, \fB\-\-daemonize\fR
+This will run a single chef\-server\-webui in the background\.
+.
+.TP
+\fB\-N\fR, \fB\-\-no\-daemonize\fR
+This will allow you to run a cluster in console mode\.
+.
+.TP
+\fB\-c\fR, \fB\-\-cluster\-nodes NUM_MERBS\fR
+Number of merb daemons to run for chef\-server\-webui\.
+.
+.TP
+\fB\-I\fR, \fB\-\-init\-file FILE\fR
+File to use for initialization on load, defaults to config/init\.rb\.
+.
+.TP
+\fB\-p\fR, \fB\-\-port PORTNUM\fR
+Port to run chef\-server\-webui on, defaults to 4040\. Additional nodes (\-c) listen on incrementing port numbers\.
+.
+.TP
+\fB\-o\fR, \fB\-\-socket\-file FILE\fR
+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 \fIonly\fR if you \fImust\fR\.
+.
+.TP
+\fB\-s\fR, \fB\-\-socket SOCKNUM\fR
+Socket number to run chef\-server\-webui on, defaults to 0\.
+.
+.TP
+\fB\-n\fR, \fB\-\-name NAME\fR
+Set the name of the application\. This is used in the process title and log file names\.
+.
+.TP
+\fB\-P\fR, \fB\-\-pid PIDFILE\fR
+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\.
+.
+.TP
+\fB\-h\fR, \fB\-\-host HOSTNAME\fR
+Host to bind to (default is 0\.0\.0\.0)\.
+.
+.TP
+\fB\-m\fR, \fB\-\-merb\-root PATH_TO_APP_ROOT\fR
+The path to the Merb\.root for the app you want to run (default is current working directory)\.
+.
+.TP
+\fB\-a\fR, \fB\-\-adapter ADAPTER\fR
+The rack adapter to use to run chef\-server\-webui (default is mongrel) [mongrel, emongrel, thin, ebb, fastcgi, webrick]\.
+.
+.TP
+\fB\-R\fR, \fB\-\-rackup FILE\fR
+Load an alternate Rack config file (default is config/rack\.rb)\.
+.
+.TP
+\fB\-i\fR, \fB\-\-irb\-console\fR
+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\.
+.
+.TP
+\fB\-S\fR, \fB\-\-sandbox\fR
+This flag will enable a sandboxed irb console\. If your ORM supports transactions, all edits will be rolled back on exit\.
+.
+.TP
+\fB\-l\fR, \fB\-\-log\-level LEVEL\fR
+Log levels can be set to any of these options: debug < info < warn < error < fatal (default is info)\.
+.
+.TP
+\fB\-L\fR, \fB\-\-log LOGFILE\fR
+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\.
+.
+.TP
+\fB\-e\fR, \fB\-\-environment STRING\fR
+Environment to run Merb under [development, production, testing] (default is development)\.
+.
+.TP
+\fB\-r\fR, \fB\-\-script\-runner [\'RUBY CODE\'| FULL_SCRIPT_PATH]\fR
+Command\-line option to run scripts and/or code in the chef\-server\-webui app\.
+.
+.TP
+\fB\-K\fR, \fB\-graceful PORT or all\fR
+Gracefully kill chef\-server\-webui proceses by port number\. Use chef\-server \-K all to gracefully kill all merbs\.
+.
+.TP
+\fB\-k\fR, \fB\-\-kill PORT\fR
+Force kill one merb worker by port number\. This will cause the worker to be respawned\.
+.
+.TP
+\fB\-\-fast\-deploy\fR
+Reload the code, but not yourinit\.rb or gems\.
+.
+.TP
+\fB\-X\fR, \fB\-\-mutex on/off\fR
+This flag is for turning the mutex lock on and off\.
+.
+.TP
+\fB\-D\fR, \fB\-\-debugger\fR
+Run chef\-server\-webui using rDebug\.
+.
+.TP
+\fB\-V\fR, \fB\-\-verbose\fR
+Print extra information\.
+.
+.TP
+\fB\-C\fR, \fB\-\-console\-trap\fR
+Enter an irb console on ^C\.
+.
+.TP
+\fB\-?\fR, \fB\-H\fR, \fB\-\-help\fR
+Show this help message\.
+.
+.SH "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\.
+.
+.P
+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\.
+.
+.P
+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\.
+.
+.SH "SEE ALSO"
+\fBchef\-client\fR(8) \fBchef\-server\-webui\fR(8) \fBknife\fR(1)
+.
+.P
+Full documentation for Chef and chef\-server is located on the Chef wiki, http://wiki\.opscode\.com/display/chef/Home\.
+.
+.SH "AUTHOR"
+Chef was written by Adam Jacob \fIadam@ospcode\.com\fR of Opscode (http://www\.opscode\.com), with contributions from the community\. This manual page was written by Joshua Timberman \fIjoshua@opscode\.com\fR with help2man\. Permission is granted to copy, distribute and / or modify this document under the terms of the Apache 2\.0 License\.
+.
+.P
+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/man/man8/chef-solo.8

@@ -0,0 +1,158 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CHEF\-SOLO" "8" "April 2011" "Chef 0.10.0.rc.0" "Chef Manual"
+.
+.SH "NAME"
+\fBchef\-solo\fR \- Runs chef in solo mode against a specified cookbook location\.
+.
+.SH "SYNOPSIS"
+\fBchef\-solo\fR \fI(options)\fR
+.
+.TP
+\fB\-c\fR, \fB\-\-config CONFIG\fR
+The configuration file to use
+.
+.TP
+\fB\-d\fR, \fB\-\-daemonize\fR
+Daemonize the process
+.
+.TP
+\fB\-g\fR, \fB\-\-group GROUP\fR
+Group to set privilege to
+.
+.TP
+\fB\-i\fR, \fB\-\-interval SECONDS\fR
+Run chef\-client periodically, in seconds
+.
+.TP
+\fB\-j\fR, \fB\-\-json\-attributes JSON_ATTRIBS\fR
+Load attributes from a JSON file or URL
+.
+.TP
+\fB\-l\fR, \fB\-\-log_level LEVEL\fR
+Set the log level (debug, info, warn, error, fatal)
+.
+.TP
+\fB\-L\fR, \fB\-\-logfile LOGLOCATION\fR
+Set the log file location, defaults to STDOUT \- recommended for daemonizing
+.
+.TP
+\fB\-N\fR, \fB\-\-node\-name NODE_NAME\fR
+The node name for this client
+.
+.TP
+\fB\-r\fR, \fB\-\-recipe\-url RECIPE_URL\fR
+Pull down a remote gzipped tarball of recipes and untar it to the cookbook cache\.
+.
+.TP
+\fB\-s\fR, \fB\-\-splay SECONDS\fR
+The splay time for running at intervals, in seconds
+.
+.TP
+\fB\-u\fR, \fB\-\-user USER\fR
+User to set privilege to
+.
+.TP
+\fB\-v\fR, \fB\-\-version\fR
+Show chef version
+.
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Show this message
+.
+.SH "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\.
+.
+.P
+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\.
+.
+.P
+For example:
+.
+.IP "" 4
+.
+.nf
+
+file_cache_path "/var/chef\-solo"
+cookbook_path "/var/chef\-solo/cookbooks"
+.
+.fi
+.
+.IP "" 0
+.
+.P
+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\.
+.
+.P
+You can also specify cookbook_path as an array, passing multiple locations to search for cookbooks\.
+.
+.P
+For example:
+.
+.IP "" 4
+.
+.nf
+
+file_cache_path "/var/chef\-solo"
+cookbook_path ["/var/chef\-solo/cookbooks", "/var/chef\-solo/site\-cookbooks"]
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Note that earlier entries are now overridden by later ones\.
+.
+.P
+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\.
+.
+.P
+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:
+.
+.IP "" 4
+.
+.nf
+
+{
+  "resolver": {
+    "nameservers": [ "10\.0\.0\.1" ],
+    "search":"int\.example\.com"
+  },
+  "run_list": [ "recipe[resolver]" ]
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+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\.
+.
+.P
+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\.
+.
+.P
+For example:
+.
+.IP "" 4
+.
+.nf
+
+chef\-solo \-c ~/solo\.rb \-j ~/node\.json  \-r http://www\.example\.com/chef\-solo\.tar\.gz
+.
+.fi
+.
+.IP "" 0
+.
+.P
+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\.
+.
+.SH "SEE ALSO"
+Full documentation for Chef and chef\-solo is located on the Chef wiki, http://wiki\.opscode\.com/display/chef/Home\.
+.
+.SH "AUTHOR"
+Chef was written by Adam Jacob \fIadam@ospcode\.com\fR of Opscode (http://www\.opscode\.com), with contributions from the community\. This manual page was written by Joshua Timberman \fIjoshua@opscode\.com\fR with help2man\. Permission is granted to copy, distribute and / or modify this document under the terms of the Apache 2\.0 License\.
+.
+.P
+On Debian systems, the complete text of the Apache 2\.0 License can be found in /usr/share/common\-licenses/Apache\-2\.0\.