Skip to content
Browse files

chef 0.10 doesn't need metadata.json

  • Loading branch information...
1 parent 9d8adb5 commit a1e547c8c71563c44885ef710bf9a8a8b5b6144a @jtimberman jtimberman committed May 20, 2011
Showing with 0 additions and 6,655 deletions.
  1. +0 −44 activemq/metadata.json
  2. +0 −51 ant/metadata.json
  3. +0 −500 apache2/metadata.json
  4. +0 −33 apparmor/metadata.json
  5. +0 −47 application/metadata.json
  6. +0 −34 apt/metadata.json
  7. +0 −30 aws/metadata.json
  8. +0 −30 bluepill/metadata.json
  9. +0 −33 boost/metadata.json
  10. +0 −35 build-essential/metadata.json
  11. +0 −41 chef-client/metadata.json
  12. +0 −94 chef/metadata.json
  13. +0 −32 cloudkick/metadata.json
  14. +0 −55 couchdb/metadata.json
  15. +0 −29 cron/metadata.json
  16. +0 −45 daemontools/metadata.json
  17. +0 −43 database/metadata.json
  18. +0 −164 djbdns/metadata.json
  19. +0 −39 drbd/metadata.json
  20. +0 −32 dynect/metadata.json
  21. +0 −42 emacs/metadata.json
  22. +0 −36 erlang/metadata.json
  23. +0 −36 fail2ban/metadata.json
  24. +0 −35 gecode/metadata.json
  25. +0 −99 gems/metadata.json
  26. +0 −43 git/metadata.json
  27. +0 −32 gnu_parallel/metadata.json
  28. +0 −39 god/metadata.json
  29. +0 −32 gunicorn/metadata.json
  30. +0 −43 hadoop/metadata.json
  31. +0 −37 haproxy/metadata.json
  32. +0 −39 heartbeat/metadata.json
  33. +0 −46 imagemagick/metadata.json
  34. +0 −42 iptables/metadata.json
  35. +0 −50 java/metadata.json
  36. +0 −51 jetty/metadata.json
  37. +0 −187 jira/metadata.json
  38. +0 −42 jpackage/metadata.json
  39. +0 −33 keepalived/metadata.json
  40. +0 −40 kickstart/metadata.json
  41. +0 −42 logrotate/metadata.json
  42. +0 −45 logwatch/metadata.json
  43. +0 −42 lvm/metadata.json
  44. +0 −45 man/metadata.json
  45. +0 −63 maradns/metadata.json
  46. +0 −50 maven/metadata.json
  47. +0 −95 memcached/metadata.json
  48. +0 −36 mercurial/metadata.json
  49. +0 −30 motd-tail/metadata.json
  50. +0 −44 munin/metadata.json
  51. +0 −226 mysql/metadata.json
  52. +0 −41 nagios/metadata.json
  53. +0 −255 nginx/metadata.json
  54. +0 −45 nscd/metadata.json
  55. +0 −103 ntp/metadata.json
  56. +0 −44 ohai/metadata.json
  57. +0 −269 openldap/metadata.json
  58. +0 −48 openssh/metadata.json
  59. +0 −30 openssl/metadata.json
  60. +0 −116 openvpn/metadata.json
  61. +0 −50 ossec/metadata.json
  62. +0 −29 pacman/metadata.json
  63. +0 −49 passenger_apache2/metadata.json
  64. +0 −32 pdns/metadata.json
  65. +0 −45 perl/metadata.json
  66. +0 −50 php/metadata.json
  67. +0 −232 postfix/metadata.json
  68. +0 −51 postgresql/metadata.json
  69. +0 −29 powershell/metadata.json
  70. +0 −35 pxe_dust/metadata.json
  71. +0 −52 python/metadata.json
  72. +0 −139 radiant/metadata.json
  73. +0 −36 reprepro/metadata.json
  74. +0 −97 resolver/metadata.json
  75. +0 −45 rsync/metadata.json
  76. +0 −96 rsyslog/metadata.json
  77. +0 −108 runit/metadata.json
  78. +0 −50 samba/metadata.json
  79. +0 −37 sbuild/metadata.json
  80. +0 −45 screen/metadata.json
  81. +0 −45 snort/metadata.json
  82. +0 −36 sqlite/metadata.json
  83. +0 −30 ssh_known_hosts/metadata.json
  84. +0 −45 stompserver/metadata.json
  85. +0 −50 subversion/metadata.json
  86. +0 −104 sudo/metadata.json
  87. +0 −45 thrift/metadata.json
  88. +0 −29 tmux/metadata.json
  89. +0 −51 tomcat/metadata.json
  90. +0 −40 trac/metadata.json
  91. +0 −35 transmission/metadata.json
  92. +0 −36 ubuntu/metadata.json
  93. +0 −48 ucspi-tcp/metadata.json
  94. +0 −30 unicorn/metadata.json
  95. +0 −36 users/metadata.json
  96. +0 −36 varnish/metadata.json
  97. +0 −29 vim/metadata.json
  98. +0 −188 wordpress/metadata.json
  99. +0 −36 xfs/metadata.json
  100. +0 −48 xml/metadata.json
  101. +0 −183 zenoss/metadata.json
  102. +0 −48 zlib/metadata.json
  103. +0 −36 zsh/metadata.json
View
44 activemq/metadata.json
@@ -1,44 +0,0 @@
-{
- "name": "activemq",
- "description": "Installs activemq and sets it up as service",
- "long_description": "# DESCRIPTION:\n\nInstalls activemq and sets up a service using the init script that comes with it.\n\n# REQUIREMENTS:\n\nPlatform:\n\nTested on Ubuntu 10.04 and CentOS 5.5. Should work on any Debian or Red Hat family distributions.\n\nOpscode cookbooks:\n\n* java\n\n# ATTRIBUTES:\n\n* `activemq[:mirror]` - download URL up to the activemq/apache-activemq directory.\n* `activemq[:version]` - version to install.\n* `activemq[:deploy]` - directory to deploy to (/opt by default)\n\n# USAGE:\n\nSimply add `recipe[activemq]` to a run list.\n\nThis cookbook doesn't use any custom configuration for activemq.\n\n# LICENSE AND AUTHOR:\n\nAuthor:: Joshua Timberman (<joshua@opscode.com>)\n\nCopyright:: 2009-2011, Opscode, Inc\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "ubuntu": [
-
- ],
- "debian": [
-
- ],
- "redhat": [
-
- ],
- "centos": [
-
- ]
- },
- "dependencies": {
- "java": [
-
- ]
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- },
- "version": "1.0.0"
-}
View
51 ant/metadata.json
@@ -1,51 +0,0 @@
-{
- "name": "ant",
- "description": "Installs/Configures ant",
- "long_description": "Description\n===========\n\nInstalls and configures Apache Ant & Ivy\n\nRequirements\n============\n\nPlatform: \n\n* Debian, Ubuntu, CentOS, Red Hat, Fedora\n\nThe following Opscode cookbooks are dependencies:\n\n* java\n* jpackage\n\nAttributes\n==========\n\nUsage\n=====\n\nSimply include the recipe where you want Apache Ant & Ivy installed.\n\nTODO\n====\n\n* plugin support\n* global config template - /etc/ant/ant.conf\n\nLicense and Author\n==================\n\nAuthor:: Seth Chisamore (<schisamo@opscode.com>)\n\nCopyright 2010, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n\n\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "debian": [
-
- ],
- "ubuntu": [
-
- ],
- "centos": [
-
- ],
- "redhat": [
-
- ],
- "fedora": [
-
- ]
- },
- "dependencies": {
- "java": [
-
- ],
- "jpackage": [
-
- ]
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "ant::default": "Installs and configures Ant"
- },
- "version": "0.10.1"
-}
View
500 apache2/metadata.json
@@ -1,500 +0,0 @@
-{
- "name": "apache2",
- "description": "Installs and configures all aspects of apache2 using Debian style symlinks with helper definitions",
- "long_description": "= DESCRIPTION:\n\nComplete Debian/Ubuntu style Apache2 configuration.\n\n= REQUIREMENTS:\n\nDebian or Ubuntu preferred.\n\nRed Hat, CentOS, Fedora and ArchLinux can be used but will be converted to a Debian/Ubuntu style Apache as it's far easier to manage with Chef.\n\n= ATTRIBUTES:\n\nThe file attributes/apache.rb contains the following attribute types:\n\n* platform specific locations and settings.\n* general settings\n* prefork attributes\n* worker attributes\n\nGeneral settings and prefork/worker attributes are tunable.\n\n= USAGE:\n\nInclude the apache2 recipe to install Apache2 and get 'sane' default settings. Configuration is modularized through Apache vhost sites a la Debian style configuration.\n\nFor Red Hat, CentOS and Fedora you should first disable selinux as it's not supported (yet), then remove the stock httpd and all it's dependencies prior to attempting to use this recipe. Many packages in these distributions drop conflicting configs into conf.d, all of which haven't been accounted for yet. Starting from scratch will also make it far easier to debug.\n\n== Defines:\n\n* +apache_module+: sets up an Apache module.\n* +apache_conf+: sets up a config file for an apache module.\n* +apache_site+: sets up a vhost site. The conf file must be available.\n* +web_app+: copies the template for a web app and enables it as a site via +apache_site+.\n\n== Web Apps:\n\nVarious applications that can be set up with Apache as the front end, such as PHP, Django, Rails and others can use the web_app define to set up the template and the Apache site. The define is kind of dumb, so the template needs have the application implementation settings, since we don't know what your app is or what is needed from Apache.\n\nWe only prototype one parameter for the +web_app+ define, \"template\". This is used to specify the name of the template to use in the current cookbook. When you use +web_app+, you can set up any parameters you want to use in your template. They will get passed to the template through the params hash. For example, the sample +web_app.conf.erb+ template in this cookbook makes use of these.\n\n* +docroot+\n* +server_name+\n* +server_aliases+\n\nThese are available as +params[:docroot]+, +params[:server_name]+, +params[:server_aliases]+ prefixed with an @ within the template.\n\nIf 'cookbook' and 'template' are not specified, the current cookbook's +templates/default/web_app.conf.erb+ will be used. If this template is not suitable for your application, copy it to your cookbook and customize as needed.\n\n== God Monitor:\n\nThere's a new recipe, +apache2::god_monitor+. You will need to make sure to include the 'god' recipe before using the +apache2::god_monitor+ recipe in your cookbook.\n\n== OpenID Auth\n\nInstalls the +mod_auth_openid+ module from source. Specify an array of OpenIDs that are allowed to authenticate with the attribute +apache[:allowed_openids]+. Use the following in a vhost to protect with OpenID authentication:\n\n AuthOpenIDEnabled On\n AuthOpenIDDBLocation /var/cache/apache2/mod_auth_openid.db\n AuthOpenIDUserProgram /usr/local/bin/mod_auth_openid.rb\n\nChange the DBLocation as appropriate for your platform. You'll need to change the file in the recipe to match. The UserProgram is optional if you don't want to limit access by certain OpenIDs.\n\n= LICENSE & AUTHOR:\n\nAuthor:: Joshua Timberman (<joshua@opscode.com>)\nCopyright:: 2009, Opscode, Inc\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "redhat": [
-
- ],
- "centos": [
-
- ],
- "debian": [
-
- ],
- "ubuntu": [
-
- ],
- "arch": [
-
- ]
- },
- "dependencies": {
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- "apache": {
- "display_name": "Apache Hash",
- "description": "Hash of Apache attributes",
- "type": "hash",
- "choice": [
-
- ],
- "calculated": false,
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/dir": {
- "display_name": "Apache Directory",
- "description": "Location for Apache configuration",
- "default": "/etc/apache2",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/log_dir": {
- "display_name": "Apache Log Directory",
- "description": "Location for Apache logs",
- "default": "/etc/apache2",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/user": {
- "display_name": "Apache User",
- "description": "User Apache runs as",
- "default": "www-data",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/binary": {
- "display_name": "Apache Binary",
- "description": "Apache server daemon program",
- "default": "/usr/sbin/apache2",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/icondir": {
- "display_name": "Apache Icondir",
- "description": "Directory location for icons",
- "default": "/usr/share/apache2/icons",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/listen_ports": {
- "display_name": "Apache Listen Ports",
- "description": "Ports that Apache should listen on",
- "type": "array",
- "default": [
- "80",
- "443"
- ],
- "choice": [
-
- ],
- "calculated": false,
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/contact": {
- "display_name": "Apache Contact",
- "description": "Email address of webmaster",
- "default": "ops@example.com",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/timeout": {
- "display_name": "Apache Timeout",
- "description": "Connection timeout value",
- "default": "300",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/keepalive": {
- "display_name": "Apache Keepalive",
- "description": "HTTP persistent connections",
- "default": "On",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/keepaliverequests": {
- "display_name": "Apache Keepalive Requests",
- "description": "Number of requests allowed on a persistent connection",
- "default": "100",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/keepalivetimeout": {
- "display_name": "Apache Keepalive Timeout",
- "description": "Time to wait for requests on persistent connection",
- "default": "5",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/servertokens": {
- "display_name": "Apache Server Tokens",
- "description": "Server response header",
- "default": "Prod",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/serversignature": {
- "display_name": "Apache Server Signature",
- "description": "Configure footer on server-generated documents",
- "default": "On",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/traceenable": {
- "display_name": "Apache Trace Enable",
- "description": "Determine behavior of TRACE requests",
- "default": "On",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/allowed_openids": {
- "display_name": "Apache Allowed OpenIDs",
- "description": "Array of OpenIDs allowed to authenticate",
- "default": "",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/prefork": {
- "display_name": "Apache Prefork",
- "description": "Hash of Apache prefork tuning attributes.",
- "type": "hash",
- "choice": [
-
- ],
- "calculated": false,
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/prefork/startservers": {
- "display_name": "Apache Prefork MPM StartServers",
- "description": "Number of MPM servers to start",
- "default": "16",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/prefork/minspareservers": {
- "display_name": "Apache Prefork MPM MinSpareServers",
- "description": "Minimum number of spare server processes",
- "default": "16",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/prefork/maxspareservers": {
- "display_name": "Apache Prefork MPM MaxSpareServers",
- "description": "Maximum number of spare server processes",
- "default": "32",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/prefork/serverlimit": {
- "display_name": "Apache Prefork MPM ServerLimit",
- "description": "Upper limit on configurable server processes",
- "default": "400",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/prefork/maxclients": {
- "display_name": "Apache Prefork MPM MaxClients",
- "description": "Maximum number of simultaneous connections",
- "default": "400",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/prefork/maxrequestsperchild": {
- "display_name": "Apache Prefork MPM MaxRequestsPerChild",
- "description": "Maximum number of request a child process will handle",
- "default": "10000",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/worker": {
- "display_name": "Apache Worker",
- "description": "Hash of Apache prefork tuning attributes.",
- "type": "hash",
- "choice": [
-
- ],
- "calculated": false,
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/worker/startservers": {
- "display_name": "Apache Worker MPM StartServers",
- "description": "Initial number of server processes to start",
- "default": "4",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/worker/maxclients": {
- "display_name": "Apache Worker MPM MaxClients",
- "description": "Maximum number of simultaneous connections",
- "default": "1024",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/worker/minsparethreads": {
- "display_name": "Apache Worker MPM MinSpareThreads",
- "description": "Minimum number of spare worker threads",
- "default": "64",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/worker/maxsparethreads": {
- "display_name": "Apache Worker MPM MaxSpareThreads",
- "description": "Maximum number of spare worker threads",
- "default": "192",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/worker/threadsperchild": {
- "display_name": "Apache Worker MPM ThreadsPerChild",
- "description": "Constant number of worker threads in each server process",
- "default": "64",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "apache/worker/maxrequestsperchild": {
- "display_name": "Apache Worker MPM MaxRequestsPerChild",
- "description": "Maximum number of request a child process will handle",
- "default": "0",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- }
- },
- "groupings": {
- },
- "recipes": {
- "apache2": "Main Apache configuration",
- "apache2::mod_alias": "Apache module 'alias' with config file",
- "apache2::mod_auth_basic": "Apache module 'auth_basic'",
- "apache2::mod_auth_digest": "Apache module 'auth_digest'",
- "apache2::mod_auth_openid": "Apache module 'authopenid'",
- "apache2::mod_authn_file": "Apache module 'authn_file'",
- "apache2::mod_authnz_ldap": "Apache module 'authnz_ldap'",
- "apache2::mod_authz_default": "Apache module 'authz_default'",
- "apache2::mod_authz_groupfile": "Apache module 'authz_groupfile'",
- "apache2::mod_authz_host": "Apache module 'authz_host'",
- "apache2::mod_authz_user": "Apache module 'authz_user'",
- "apache2::mod_autoindex": "Apache module 'autoindex' with config file",
- "apache2::mod_cgi": "Apache module 'cgi'",
- "apache2::mod_dav": "Apache module 'dav'",
- "apache2::mod_dav_svn": "Apache module 'dav_svn'",
- "apache2::mod_deflate": "Apache module 'deflate' with config file",
- "apache2::mod_dir": "Apache module 'dir' with config file",
- "apache2::mod_env": "Apache module 'env'",
- "apache2::mod_expires": "Apache module 'expires'",
- "apache2::mod_fcgid": "Apache module 'fcgid', package on ubuntu/debian, rhel/centos, compile source on suse; with config file",
- "apache2::mod_headers": "Apache module 'headers'",
- "apache2::mod_ldap": "Apache module 'ldap'",
- "apache2::mod_log_config": "Apache module 'log_config'",
- "apache2::mod_mime": "Apache module 'mime' with config file",
- "apache2::mod_negotiation": "Apache module 'negotiation' with config file",
- "apache2::mod_php5": "Apache module 'php5'",
- "apache2::mod_proxy": "Apache module 'proxy' with config file",
- "apache2::mod_proxy_ajp": "Apache module 'proxy_ajp'",
- "apache2::mod_proxy_balancer": "Apache module 'proxy_balancer'",
- "apache2::mod_proxy_connect": "Apache module 'proxy_connect'",
- "apache2::mod_proxy_http": "Apache module 'proxy_http'",
- "apache2::mod_python": "Apache module 'python'",
- "apache2::mod_rewrite": "Apache module 'rewrite'",
- "apache2::mod_setenvif": "Apache module 'setenvif' with config file",
- "apache2::mod_ssl": "Apache module 'ssl' with config file, adds port 443 to listen_ports",
- "apache2::mod_status": "Apache module 'status' with config file"
- },
- "version": "0.99.3"
-}
View
33 apparmor/metadata.json
@@ -1,33 +0,0 @@
-{
- "name": "apparmor",
- "description": "Disables apparmor service on Ubuntu",
- "long_description": "",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "ubuntu": [
-
- ]
- },
- "dependencies": {
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "default": "Disables apparmor service on Ubuntu"
- },
- "version": "0.9.0"
-}
View
47 application/metadata.json
@@ -1,47 +0,0 @@
-{
- "name": "application",
- "description": "Deploys and configures a variety of applications defined from databag 'apps'",
- "long_description": "Application cookbook\n====================\n\nThis cookbook is initially designed to be able to describe and deploy web applications. Currently supported:\n\n* Rails\n* Java\n* Django\n* PHP\n\nOther application stacks (Rack, WSGI, etc) will be supported as new recipes at a later date.\n\nThis cookbook aims to provide primitives to install/deploy any kind of application driven entirely by data defined in an abstract way through a data bag.\n\n---\nRequirements\n============\n\nChef 0.9.14 or higher required.\n\nThe following Opscode cookbooks are dependencies:\n\n* runit\n* unicorn\n* passenger_apache2\n* tomcat\n* python\n* gunicorn\n* apache2\n* php\n\n---\nRecipes\n=======\n\nThe application cookbook contains the following recipes.\n\ndefault\n-------\n\nSearches the `apps` data bag and checks that a server role in the app exists on this node, adds the app to the run state and uses the role for the app to locate the recipes that need to be used. The recipes listed in the \"type\" part of the data bag are included by this recipe, so only the \"application\" recipe needs to be in the node or role `run_list`.\n\nSee below regarding the application data bag structure.\n\ndjango\n------\n\nUsing the node's `run_state` that contains the current application in the search, this recipe will:\n\n* create an application specific virtualenv\n* install required packages and pips\n* set up the deployment scaffolding\n* creates `settings_local.py` file with the database connection information if required\n* performs a revision-based deploy\n\nThis recipe can be used on nodes that are going to run the application, or on nodes that need to have the application code checkout available such as supporting utility nodes or a configured load balancer that needs static assets stored in the application repository.\n\nFor pip requirements.txt files: ensure the requirements.txt file is present in the root of the application code (APP_ROOT/requirements.txt) or named after the node's current app_environment in a directory named requirements (requirements/production.txt) and `pip install -r` will be run before migrations.\n\nIn order to manage running database migrations (python manage.py migrate), you can use a role that sets the `run_migrations` attribute for the application (`my_app`, below) in the correct environment (production, below). Note the data bag item needs to have migrate set to true. See the data bag example below.\n\n {\n \"name\": \"my_app_run_migrations\",\n \"description\": \"Run db:migrate on demand for my_app\",\n \"json_class\": \"Chef::Role\",\n \"default_attributes\": {\n },\n \"override_attributes\": {\n \"apps\": {\n \"my_app\": {\n \"production\": {\n \"run_migrations\": true\n }\n }\n }\n },\n \"chef_type\": \"role\",\n \"run_list\": [\n ]\n }\n\nSimply apply this role to the node's run list when it is time to run migrations, and the recipe will remove the role when done. Since Django does not have a standard database migration function built into the core framework, we assume the popular [South framework](http://south.aeracode.org/) is being used.\n\ngunicorn\n--------\n\nRequires `gunicorn` cookbook.\n\nGunicorn is installed, default attributes are set for the node and an app specific gunicorn config and runit service are created.\n\njava_webapp\n-----------\n\nUsing the node's `run_state` that contains the current application in the search, this recipe will:\n\n* install required packages\n* set up the deployment scaffolding\n* create the context configuration for the servlet container\n* performs a `remote_file` deploy.\n\nThe servlet container context configuration (`context.xml`) exposes the following JNDI resources which can be referenced by the webapp's deployment descriptor (web.xml):\n\n* A JDBC datasource for all databases in the node's current `app_environment`. The datasource uses the information (including JDBC driver) specified in the data bag item for the application.\n* An Environment entry that matches the node's current `app_environment` attribute value. This is useful for loading environment specific properties files in the web application. \n\nThis recipe assumes some sort of build process, such as Maven or a Continuous Integration server like Hudson, will create a deployable artifact and make it available for download via HTTP (such as S3 or artifactory).\n\nmod\\_php\\_apache2\n-----------------\n\nRequires `apache2` cookbook. Sets up a mod_php vhost template for the application using the `apache2` cookbook's `web_app` definition. See data bag example below.\n\npassenger_apache2\n-----------------\n\nRequires `apache2` and `passenger_apache2` cookbooks. Sets up a passenger vhost template for the application using the `apache2` cookbook's `web_app` definition. Use this with the `rails` recipe, in the list of recipes for a specific application type. See data bag example below.\n\nphp\n---\n\nUsing the node's `run_state` that contains the current application in the search, this recipe will:\n\n* install required packages and pears/pecls\n* set up the deployment scaffolding\n* creates a `local_settings.php` (specific file name and project path is configurable) file with the database connection information if required\n* performs a revision-based deploy\n\nThis recipe can be used on nodes that are going to run the application, or on nodes that need to have the application code checkout available such as supporting utility nodes or a configured load balancer that needs static assets stored in the application repository.\n\nSince PHP projects do not have a standard `local_settings.php` file (or format) that contains database connection information. This recipe assumes you will provide a template in an application specific cookbook. See additional notes in the 'Application Data Bag' section below.\n\nrails\n-----\n\nUsing the node's `run_state` that contains the current application in the search, this recipe will:\n\n* install required packages and gems\n* set up the deployment scaffolding\n* creates database and memcached configurations if required\n* performs a revision-based deploy.\n\nThis recipe can be used on nodes that are going to run the application, or on nodes that need to have the application code checkout available such as supporting utility nodes or a configured load balancer that needs static assets stored in the application repository.\n\nFor Gem Bundler: include `bundler` or `bundler08` in the gems list. `bundle install` or `gem bundle` will be run before migrations. The `bundle install` command is invoked with the `--deployment` and `--without` flags following [Bundler best practices](http://gembundler.com/deploying.html).\n\nFor config.gem in environment: `rake gems:install RAILS_ENV=<node environment>` will be run when a Gem Bundler command is not.\n\nIn order to manage running database migrations (rake db:migrate), you can use a role that sets the `run_migrations` attribute for the application (`my_app`, below) in the correct environment (production, below). Note the data bag item needs to have migrate set to true. See the data bag example below.\n\n {\n \"name\": \"my_app_run_migrations\",\n \"description\": \"Run db:migrate on demand for my_app\",\n \"json_class\": \"Chef::Role\",\n \"default_attributes\": {\n },\n \"override_attributes\": {\n \"apps\": {\n \"my_app\": {\n \"production\": {\n \"run_migrations\": true\n }\n }\n }\n },\n \"chef_type\": \"role\",\n \"run_list\": [\n ]\n }\n\nSimply apply this role to the node's run list when it is time to run migrations, and the recipe will remove the role when done.\n\ntomcat\n-------\n\nRequires `tomcat` cookbook.\n\nTomcat is installed, default attributes are set for the node and the app specific context.xml is symlinked over to Tomcat's context directory as the root context (ROOT.xml).\n\nunicorn\n-------\n\nRequires `unicorn` cookbook.\n\nUnicorn is installed, default attributes are set for the node and an app specific unicorn config and runit service are created.\n\n---\nDeprecated Recipes\n==================\n\nThe following recipes are deprecated and have been removed from the cookbook. To retrieve an older version, reference commit 4396ce6.\n\n`passenger-nginx`\n`rails_nginx_ree_passenger`\n\n---\nApplication Data Bag \n=====================\n\nThe applications data bag expects certain values in order to configure parts of the recipe. Below is a paste of the JSON, where the value is a description of the key. Use your own values, as required. Note that this data bag is also used by the `database` cookbook, so it will contain database information as well. Items that may be ambiguous have an example.\n\nThe application used in examples is named `my_app` and the environment is `production`. Most top-level keys are Arrays, and each top-level key has an entry that describes what it is for, followed by the example entries. Entries that are hashes themselves will have the description in the value.\n\nNote about \"type\": the recipes listed in the \"type\" will be included in the run list via `include_recipe` in the application default recipe based on the type matching one of the `server_roles` values.\n\nNote about packages, the version is optional. If specified, the version will be passed as a parameter to the resource. Otherwise it will use the latest available version per the default `:install` action for the package provider.\n\nRail's version additional notes\n-------------------------------\n\nNote about `databases`, the data specified will be rendered as the `database.yml` file. In the `database` cookbook, this information is also used to set up privileges for the application user, and create the databases.\n\nNote about gems, the version is optional. If specified, the version will be passed as a parameter to the resource. Otherwise it will use the latest available version per the default `:install` action for the package provider.\n\nAn example is data bag item is included in this cookbook at `examples/data_bags/apps/rails_app.json`.\n\nJava webapp version additional notes\n------------------------------------\n\nNote about `databases`, the data specified will be rendered as JNDI Datasource `Resources` in the servlet container context confiruation (`context.xml`) file. In the `database` cookbook, this information is also used to set up privileges for the application user, and create the databases.\n\nAn example is data bag item is included in this cookbook at `examples/data_bags/apps/java_app.json`.\n\nDjango version additional notes\n-------------------------------\n\nNote about `databases`, the data specified will be rendered as the `settings_local.py` file. In the `database` cookbook, this information is also used to set up privileges for the application user, and create the databases.\n\nNote about pips, the version is optional. If specified, the version will be passed as a parameter to the resource. Otherwise it will use the latest available version per the default `:install` action for the python_pip package provider.\n\nThe `local_settings_file` value may be used to supply an alternate name for the environment specific `settings_local.py`, since Django projects do not have a standard name for this file.\n\nAn example is data bag item is included in this cookbook at `examples/data_bags/apps/django_app.json`.\n\nPHP version additional notes\n----------------------------\n\nNote about `databases`, the data specified will be rendered as the `local_settings.php` file. In the `database` cookbook, this information is also used to set up privileges for the application user, and create the databases.\n\nNote about pears/pecls, the version is optional. If specified, the version will be passed as a parameter to the resource. Otherwise it will use the latest available version per the default `:install` action for the php_pear package provider.\n\nThe `local_settings_file` value is used to supply the name, and relative local project path, for the environment specific `local_settings.php`, since PHP projects do not have a standard name (or location) for this file.\n\nFor applications that look for this file in the project root just supply a name:\n\nMediaWiki:\n\n \"local_settings_file\": \"LocalSettings.php\"\n \nWordpress:\n\n \"local_settings_file\": \"wp-config.php\"\n\nFor applications that expect the file nested within the project root, you can supply a relative path:\n\nCakePHP:\n\n \"local_settings_file\": \"app/config/database.php\"\n\nThe template used to render this `local_settings.php` file is assumed to be provided in an application specific cookbook named after the application being deployed. For example if you were deploying code for an application named `mediawiki` you would create a cookbook named `mediawiki` and in that cookbook place a template named `LocalSettings.php.erb`:\n\n mediawiki/\n +-- files\n | +-- default\n | +-- schema.sql\n +-- metadata.rb\n +-- README.md\n +-- recipes\n | +-- db_bootstrap.rb\n | +-- default.rb\n +-- templates\n +-- default\n +-- LocalSettings.php.erb\n\nThe template will be passed the following variables which can be used to dynamically fill values in the ERB:\n\n* path - fill path to the 'current' project path\n* host - database master fqdn\n* database - environment specific database information from the application's data bag item\n* app - Ruby mash representation of the complete application data bag item for this app, useful if other arbitrary config data has been stashed in the data bag item.\n\nA few example `local_settings` templates are included in this cookbook at `examples/templates/defaults/*`:\n\n* MediaWiki - LocalSettings.php.erb\n* Wordpress - wp-config.php.erb\n\nAn example is data bag item is included in this cookbook at `examples/data_bags/apps/php_app.json`.\n\n---\nUsage\n=====\n\nTo use the application cookbook, we recommend creating a role named after the application, e.g. `my_app`. This role should match one of the `server_roles` entries, that will correspond to a `type` entry, in the databag. Create a Ruby DSL role in your chef-repo, or create the role directly with knife.\n\n % knife role show my_app\n {\n \"name\": \"my_app\",\n \"chef_type\": \"role\",\n \"json_class\": \"Chef::Role\",\n \"default_attributes\": {\n },\n \"description\": \"\",\n \"run_list\": [\n \"recipe[application]\"\n ],\n \"override_attributes\": {\n }\n }\n\nAlso recommended is a cookbook named after the application, e.g. `my_app`, for additional application specific setup such as other config files for queues, search engines and other components of your application. The `my_app` recipe can be used in the run list of the role, if it includes the `application` recipe.\n\nYou should also have a role for the environment(s) you wish to use this cookbook. Similar to the role above, create the Ruby DSL file in chef-repo, or create with knife directly.\n\n % knife role show production\n {\n \"name\": \"production\",\n \"chef_type\": \"role\",\n \"json_class\": \"Chef::Role\",\n \"default_attributes\": {\n \"app_environment\": \"production\"\n },\n \"description\": \"production environment role\",\n \"run_list\": [\n\n ],\n \"override_attributes\": {\n }\n }\n\nThis role uses a default attribute so nodes can be moved into other environments on the fly simply by modifying their node object directly on the Chef Server.\n\n---\nLicense and Author\n==================\n\nAuthor:: Adam Jacob (<adam@opscode.com>)\nAuthor:: Joshua Timberman (<joshua@opscode.com>)\nAuthor:: Seth Chisamore (<schisamo@opscode.com>)\n\nCopyright 2009-2011, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- },
- "dependencies": {
- "runit": ">= 0.0.0",
- "unicorn": ">= 0.0.0",
- "apache2": ">= 0.0.0",
- "passenger_apache2": ">= 0.0.0",
- "tomcat": ">= 0.0.0",
- "python": ">= 0.0.0",
- "gunicorn": ">= 0.0.0",
- "php": ">= 0.0.0"
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "application": "Loads application databags and selects recipes to use",
- "application::django": "Deploys a Django application specified in a data bag with the deploy_revision resource",
- "application::gunicorn": "Sets up the deployed Django application with Gunicorn as the web server",
- "application::java_webapp": "Deploys a Java web application WAR specified in a data bag with the remote_file resource",
- "application::mod_php_apache2": "Sets up a deployed PHP application as a mod_php virtual host in Apache2",
- "application::passenger_apache2": "Sets up a deployed Rails application as a Passenger virtual host in Apache2",
- "application::php": "Deploys a PHP application specified in a data bag with the deploy_revision resource",
- "application::rails": "Deploys a Rails application specified in a data bag with the deploy_revision resource",
- "application::tomcat": "Sets up the deployed Java application with Tomcat as the servlet container",
- "application::unicorn": "Sets up the deployed Rails application with Unicorn as the web server"
- },
- "version": "0.99.9"
-}
View
34 apt/metadata.json
@@ -1,34 +0,0 @@
-{
- "name": "apt",
- "description": "Configures apt and apt services and an LWRP for managing apt repositories",
- "long_description": "Description\n===========\n\nConfigures various APT components on Debian-like systems. Also includes a LWRP.\n\nRecipes\n=======\n\ndefault\n-------\nThe default recipe runs apt-get update during the Compile Phase of the Chef run to ensure that the system's package cache is updated with the latest. It is recommended that this recipe appear first in a node's run list (directly or through a role) to ensure that when installing packages, Chef will be able to download the latest version available on the remote APT repository.\n\nThis recipe also sets up a local cache directory for preseeding packages.\n\ncacher\n------\nInstalls the apt-cacher package and service so the system can provide APT caching. You can check the usage report at http://{hostname}:3142/report. The cacher recipe includes the `cacher-client` recipe, so it helps seed itself.\n\ncacher-client\n-------------\nConfigures the node to use the apt-cacher server as a client.\n\nResources/Providers\n===================\n\nThis LWRP provides an easy way to manage additional APT repositories.\n\n# Actions\n\n- :add: creates a repository file and builds the repository listing\n- :remove: removes the repository file\n\n# Attribute Parameters\n\n- repo_name: name attribute. The name of the channel to discover\n- uri: the base of the Debian distribution\n- distribution: this is usually your release's codename...ie something like `karmic`, `lucid` or `maverick`\n- components: package groupings..when it doubt use `main`\n- deb_src: whether or not to add the repository as a source repo as well\n- key_server: the GPG keyserver where the key for the repo should be retrieved\n- key: if a `key_server` is provided, this is assumed to be the fingerprint, otherwise it is the URI to the GPG key for the repo\n\n# Example\n\n # add the Zenoss repo\n apt_repository \"zenoss\" do\n uri \"http://dev.zenoss.org/deb\"\n components [\"main\",\"stable\"]\n action :add\n end\n \n # add the Nginx PPA; grab key from keyserver\n apt_repository \"nginx-php\" do\n uri \"http://ppa.launchpad.net/nginx/php5/ubuntu\"\n distribution node['lsb']['codename']\n components [\"main\"]\n keyserver \"keyserver.ubuntu.com\"\n key \"C300EE8C\"\n action :add\n end\n \n # add the Cloudkick Repo\n apt_repository \"cloudkick\" do\n uri \"http://packages.cloudkick.com/ubuntu\"\n distribution node['lsb']['codename']\n components [\"main\"]\n key \"http://packages.cloudkick.com/cloudkick.packages.key\"\n action :add\n end\n \n # remove Zenoss repo\n apt_repository \"zenoss\" do\n action :remove\n end\n \nUsage\n=====\n\nPut `recipe[apt]` first in the run list. If you have other recipes that you want to use to configure how apt behaves, like new sources, notify the execute resource to run, e.g.:\n\n template \"/etc/apt/sources.list.d/my_apt_sources.list\" do\n notifies :run, resources(:execute => \"apt-get update\"), :immediately\n end\n\nThe above will run during execution phase since it is a normal template resource, and should appear before other package resources that need the sources in the template.\n\nPut `recipe[apt::cacher]` in the run_list for a server to provide APT caching and add `recipe[apt::cacher-client]` on the rest of the Debian-based nodes to take advantage of the caching server.\n\nLicense and Author\n==================\n\nAuthor:: Joshua Timberman (<joshua@opscode.com>)\nAuthor:: Matt Ray (<matt@opscode.com>)\nAuthor:: Seth Chisamore (<schisamo@opscode.com>)\n\nCopyright 2009-2011 Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "ubuntu": ">= 0.0.0",
- "debian": ">= 0.0.0"
- },
- "dependencies": {
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "apt": "Runs apt-get update during compile phase and sets up preseed directories",
- "apt::cacher": "Set up an APT cache",
- "apt::cacher-client": "Client for the apt::cacher server"
- },
- "version": "1.1.1"
-}
View
30 aws/metadata.json
@@ -1,30 +0,0 @@
-{
- "name": "aws",
- "description": "LWRPs for managing AWS resources",
- "long_description": "Description\n===========\n\nThis cookbook provides libraries, resources and providers to configure and manage Amazon Web Services components and offerings with the EC2 API. Currently supported resources:\n\n* EBS Volumes (`ebs_volume`)\n* Elastic IPs (`elastic_ip`)\n\n---\nRequirements\n============\n\nRequires Chef 0.7.10 or higher for Lightweight Resource and Provider support. Chef 0.8+ is recommended. While this cookbook can be used in `chef-solo` mode, to gain the most flexibility, we recommend using `chef-client` with a Chef Server.\n\nAn Amazon Web Services account is required. The Access Key and Secret Access Key are used to authenticate with EC2.\n\n---\nAWS Credentials\n===============\n\nIn order to manage AWS components, authentication credentials need to be available to the node. There are a number of ways to handle this, such as node attributes or roles. We recommend storing these in a databag (Chef 0.8+), and loading them in the recipe where the resources are needed.\n\nDataBag recommendation:\n\n % knife data bag show aws main\n {\n \"id\": \"main\",\n \"aws_access_key_id\": \"YOUR_ACCESS_KEY\",\n \"aws_secret_access_key\": \"YOUR_SECRET_ACCESS_KEY\"\n }\n\nThis can be loaded in a recipe with:\n\n aws = data_bag_item(\"aws\", \"main\")\n\nAnd to access the values:\n\n aws['aws_access_key_id']\n aws['aws_secret_access_key']\n\nWe'll look at specific usage below.\n\n---\nRecipes\n=======\n\ndefault.rb\n----------\n\nThe default recipe installs the `right_aws` RubyGem, which this cookbook requires in order to work with the EC2 API. Make sure that the aws recipe is in the node or role `run_list` before any resources from this cookbook are used.\n\n \"run_list\": [\n \"recipe[aws]\"\n ]\n\nThe `gem_package` is created as a Ruby Object and thus installed during the Compile Phase of the Chef run.\n\n---\nLibraries\n=========\n\nThe cookbook has a library module, `Opscode::AWS::Ec2`, which can be included where necessary:\n\n include Opscode::Aws::Ec2\n\nThis is needed in any providers in the cookbook. Along with some helper methods used in the providers, it sets up a class variable, `ec2` that is used along with the access and secret access keys\n\n---\nResources and Providers\n=======================\n\nThis cookbook provides two resources and corresponding providers.\n\n`ebs_volume.rb`\n-------------\n\nManage Elastic Block Store (EBS) volumes with this resource.\n\nActions:\n\n* `create` - create a new volume.\n* `attach` - attach the specified volume.\n* `detach` - detach the specified volume.\n* `snapshot` - create a snapshot of the volume.\n* `prune` - prune snapshots.\n\nAttribute Parameters:\n\n* `aws_secret_access_key`, `aws_access_key` - passed to `Opscode::AWS:Ec2` to authenticate, required.\n* `size` - size of the volume in gigabytes.\n* `snapshot_id` - snapshot to build EBS volume from.\n* `availability_zone` - EC2 region, and is normally automatically detected.\n* `device` - local block device to attach the volume to, e.g. `/dev/sdi` but no default value, required.\n* `volume_id` - specify an ID to attach, cannot be used with action `:create` because AWS assigns new volume IDs\n* `timeout` - connection timeout for EC2 API.\n* `snapshots_to_keep` - used with action `:prune` for number of snapshots to maintain.\n\n`elastic_ip.rb`\n-------------\n\nActions:\n\n* `associate` - associate the IP.\n* `disassociate` - disassociate the IP.\n\nAttribute Parameters:\n\n* `aws_secret_access_key`, `aws_access_key` - passed to `Opscode::AWS:Ec2` to authenticate, required.\n* `ip` - the IP address.\n* `timeout` - connection timeout for EC2 API.\n\n\n---\nUsage\n=====\n\nFor both the `ebs_volume` and `elastic_ip` resources, put the following at the top of the recipe where they are used.\n\n include_recipe \"aws\"\n aws = data_bag_item(\"aws\", \"main\")\n\naws_ebs_volume\n--------------\n\nThe resource only handles manipulating the EBS volume, additional resources need to be created in the recipe to manage the attached volume as a filesystem or logical volume.\n\n aws_ebs_volume \"db_ebs_volume\" do\n aws_access_key aws['aws_access_key_id']\n aws_secret_access_key aws['aws_secret_access_key']\n size 50\n device \"/dev/sdi\"\n action [ :create, :attach ]\n end\n\nThis will create a 50G volume, attach it to the instance as `/dev/sdi`.\n\n aws_ebs_volume \"db_ebs_volume_from_snapshot\" do\n aws_access_key aws['aws_access_key_id']\n aws_secret_access_key aws['aws_secret_access_key']\n size 50\n device \"/dev/sdi\"\n snapshot_id \"snap-ABCDEFGH\"\n action [ :create, :attach ]\n end\n\nThis will create a new 50G volume from the snapshot ID provided and attach it as `/dev/sdi`.\n\naws_elastic_ip\n--------------\n\nThe `elastic_ip` resource provider does not support allocating new IPs. This must be done before running a recipe that uses the resource. After allocating a new Elastic IP, we recommend storing it in a databag and loading the item in the recipe.\n\nDatabag structure:\n\n % knife data bag show aws eip_load_balancer_production\n {\n \"id\": \"eip_load_balancer_production\",\n \"public_ip\": \"YOUR_ALLOCATED_IP\"\n }\n\nThen to set up the Elastic IP on a system:\n\n ip_info = data_bag_item(\"aws\", \"eip_load_balancer_production\")\n\n aws_elastic_ip \"eip_load_balancer_production\" do\n aws_access_key aws['aws_access_key_id']\n aws_secret_access_key aws['aws_secret_access_key']\n lb ip_info['public_ip']\n action :associate\n end\n\nThis will use the loaded `aws` and `ip_info` databags to pass the required values into the resource to configure. Note that when associating an Elastic IP to an instance, connectivity to the instance will be lost because the public IP address is changed. You will need to reconnect to the instance with the new IP.\n\nYou can also store this in a role as an attribute or assign to the node directly, if preferred.\n\n---\nLicense and Author\n==================\n\nAuthor:: Chris Walters (<cw@opscode.com>)\nAuthor:: AJ Christensen (<aj@opscode.com>)\n\nCopyright 2009-2010, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- },
- "dependencies": {
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "aws": "Installs the right_aws gem during compile time"
- },
- "version": "0.99.0"
-}
View
30 bluepill/metadata.json
@@ -1,30 +0,0 @@
-{
- "name": "bluepill",
- "description": "Installs bluepill gem and configures to manage services, includes bluepill_service LWRP",
- "long_description": "Description\n===========\n\nInstalls bluepill RubyGem and configures it to manage services. Also includes a LWRP.\n\nRequirements\n============\n\nBluepill is a pure Ruby service management tool/library, so this cookbook should work on any system. The attributes do set up paths based on FHS locations, see below.\n\nAttributes\n==========\n\nDefault locations for bluepill are in \"FHS compliant\" locations.\n\n* `node[\"bluepill\"][\"bin\"]` - Path to bluepill program, default is 'bluepill' in the RubyGems binary directory.\n* `node[\"bluepill\"][\"logfile\"]` - Location of the bluepill log file, default \"/var/log/bluepill.log\".\n* `node[\"bluepill\"][\"conf_dir\"]` - Location of service config files (pills), default \"/etc/bluepill\".\n* `node[\"bluepill\"][\"pid_dir\"]` - Location of pidfiles, default \"/var/run/bluepill\"\n* `node[\"bluepill\"][\"state_dir\"]` - Location of state directory, default \"/var/lib/bluepill\"\n* `node[\"bluepill\"][\"init_dir\"]` - Location of init script directory, default selected by platform.\n\nResources/Providers\n===================\n\nThis cookbook contains an LWRP, `bluepill_service`. This can be used with the normal Chef service resource, by using the `provider` parameter, or by specifying the `bluepill_service` shortcut. These two resources are equivalent.\n\n service \"my_app\" do\n provider bluepill_service\n action [:enable, :load, :start]\n end\n\n bluepill_service \"my_app\" do\n action [:enable, :load, :start]\n end\n\nThe load action should probably always be specified, to ensure that if bluepill isn't running already it gets started. The \n\nThe recipe using the service must contain a template resource for the pill and it must be named `my_app.pill.erb`, where `my_app` is the service name passed to the bluepill service resource. \n\nUsage\n=====\n\nBe sure to include the bluepill recipe in the run list to ensure that the gem and bluepill-related directories are created. This will also make the cookbook available on the system and other cookbooks won't need to explicitly depend on it in the metadata.\n\nIf the default directory locations in the attributes/default.rb aren't what you want, change them by setting them either in the attributes file itself, or create attributes in a role applied to any systems that will use bluepill.\n\nExample pill template resource and .erb file:\n\n template \"/etc/bluepill/my_app\" do\n source \"my_app.pill.erb\"\n end\n\n Bluepill.application(\"my_app\") do |app|\n app.process(\"my_app\") do |process|\n process.pid_file = \"/var/run/my_app.pid\"\n process.start_command = \"/usr/bin/my_app\"\n end\n end\n\nSee bluepill's documentation for more information on creating pill templates.\n \n\nLicense and Author\n==================\n\nAuthor:: Joshua Timberman (<joshua@opscode.com>)\n\nCopyright 2010, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- },
- "dependencies": {
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "bluepill::default": "Installs bluepill rubygem and set up management directories"
- },
- "version": "0.2.0"
-}
View
33 boost/metadata.json
@@ -1,33 +0,0 @@
-{
- "recommendations": {
- },
- "attributes": {
- },
- "maintainer": "Opscode, Inc.",
- "suggestions": {
- },
- "dependencies": {
- },
- "maintainer_email": "cookbooks@opscode.com",
- "conflicting": {
- },
- "platforms": {
- "ubuntu": [
-
- ]
- },
- "license": "Apache 2.0",
- "version": "0.1.0",
- "providing": {
- },
- "recipes": {
- "boost": "Installs libboost-dev"
- },
- "replacing": {
- },
- "name": "boost",
- "description": "Installs libboost",
- "groupings": {
- },
- "long_description": "= DESCRIPTION:\n\nInstalls boost, mainly to support Thrift.\n\n= REQUIREMENTS:\n\nPlatform: Ubuntu 9.04. Not tested on any others at this time.\n\n= USAGE:\n\nInclude this recipe to install boost development packages.\n\n include_recipe \"boost\"\n\nMerely installs the libboost-dev package which should grab a bunch of dependencies and get the right thing.\n\n= LICENSE and AUTHOR:\n\n\nAuthor:: Joshua Timberman (<joshua@opscode.com>)\nCopyright:: 2009, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n"
- }
View
35 build-essential/metadata.json
@@ -1,35 +0,0 @@
-{
- "name": "build-essential",
- "description": "Installs C compiler / build tools",
- "long_description": "",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "fedora": ">= 0.0.0",
- "redhat": ">= 0.0.0",
- "centos": ">= 0.0.0",
- "ubuntu": ">= 0.0.0",
- "debian": ">= 0.0.0"
- },
- "dependencies": {
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "build-essential": "Installs C compiler and build tools on Linux"
- },
- "version": "1.0.0"
-}
View
41 chef-client/metadata.json
@@ -1,41 +0,0 @@
-{
- "name": "chef-client",
- "description": "Manages aspects of only chef-client",
- "long_description": "DESCRIPTION\n===========\n\nThis cookbook is used to configure a system as a Chef Client.\n\nREQUIREMENTS\n============\n\nChef 0.9.12 or later is required.\n\nSupported Platforms\n-------------------\n\nThe following platforms are supported by this cookbook, meaning that the recipes run on these platforms without error.\n\n* Debian\n* Ubuntu\n* Red Hat\n* CentOS\n* Fedora\n* ArchLinux\n* FreeBSD\n* Mac OS X\n\nOther Cookbooks\n---------------\n\nOther cookbooks can be used with this cookbook but they are not explicitly required. The default settings in this cookbook do not require their use. The other cookbooks (on cookbooks.opsocde.com) are:\n\n* bluepill\n* daemontools\n* runit\n\nSee __USAGE__ below.\n\nATTRIBUTES\n==========\n\n* `node[\"chef_client\"][\"interval\"]` - Sets `Chef::Config[:interval]` via command-line option for number of seconds between chef-client daemon runs. Default 1800.\n* `node[\"chef_client\"][\"splay\"]` - Sets `Chef::Config[:splay]` via command-line option for a random amount of seconds to add to interval. Default 20.\n* `node[\"chef_client\"][\"log_dir\"]` - Sets directory used in `Chef::Config[:log_location]` via command-line option to a location where chef-client should log output. Default \"/var/log/chef\".\n* `node[\"chef_client\"][\"server_url\"]` - Sets `Chef::Config[:chef_server_url]` in the config file to the Chef Server URI. Default \"http://localhost:4000\". See __USAGE__.\n* `node[\"chef_client\"][\"validation_client_name\"]` - Sets `Chef::Config[:validation_client_name]` in the config file to the name of the validation client. Default \"chef-validator\". See __USAGE__.\n* `node[\"chef_client\"][\"init_style\"]` - Sets up the client service based on the style of init system to use. Default is based on platform and falls back to \"none\". See __USAGE__.\n* `node[\"chef_client\"][\"run_path\"]` - Directory location where chef-client should write the PID file. Default based on platform, falls back to \"/var/run\".\n* `node[\"chef_client\"][\"cache_path\"]` - Directory location for `Chef::Config[:file_cache_path]` where chef-client will cache various files. Default is based on platform, falls back to \"/var/chef/cache\".\n* `node[\"chef_client\"][\"backup_path\"]` - Directory location for `Chef::Config[:file_backup_path]` where chef-client will backup templates and cookbook files. Default is based on platform, falls back to \"/var/chef/backup\".\n\nRECIPES\n=======\n\nThis section describes the recipes in the cookbook and how to use them in your environment.\n\nconfig\n------\n\nSets up the `/etc/chef/client.rb` config file from a template and reloads the configuration for the current chef-client run.\n\nservice\n-------\n\nUse this recipe on systems that should have a `chef-client` daemon running, such as when Knife bootstrap was used to install Chef on a new system.\n\nThis recipe sets up the `chef-client` service depending on the `init_style` attribute (see above). The following init styles are supported:\n\n* init - uses the init script included in the chef gem, supported on debian and redhat family distributions.\n* upstart - uses the upstart job included in the chef gem, supported on ubuntu.\n* arch - uses the init script included in this cookbook for ArchLinux, supported on arch.\n* runit - sets up the service under runit, supported on ubuntu, debian and gentoo.\n* bluepill - sets up the service under bluepill. As bluepill is a pure ruby process monitor, this should work on any platform.\n* daemontools -sets up the service under daemontools, supported on debian, ubuntu and arch\n* bsd - prints a message about how to update BSD systems to enable the chef-client service, supported on Free/OpenBSD and OSX.\n\ndefault\n-------\n\nIncludes the `chef-client::service` recipe by default.\n\n`delete_validation`\n-------------------\n\nUse this recipe to delete the validation certificate (default `/etc/chef/validation.pem`) when using a `chef-client` after the client has been validated and authorized to connect to the server.\n\nBeware if using this on your Chef Server. First copy the validation.pem certificate file to another location, such as your knife configuration directory (`~/.chef`) or [Chef Repository](http://wiki.opscode.com/display/chef/Chef+Repository).\n\nUSAGE\n=====\n\nCreate a `base` role that will represent the base configuration for any system that includes managing aspects of the chef-client. Add recipes to the run list of the role, customize the attributes, and apply the role to nodes. For example, the following role (Ruby DSL) will set the init style to `init`, delete the validation certificate (as the client would already be authenticated) and set up the chef-client as a service using the init style.\n\n name \"base\"\n description \"Base role applied to all nodes\"\n override_attributes(\n \"chef_client\" => {\n \"init_style\" => \"init\"\n }\n )\n run_list(\n \"recipe[chef-client::delete_validation]\",\n \"recipe[chef-client::config]\",\n \"recipe[chef-client]\"\n )\n\nThe `chef-client::config` recipe is only required with init style `init` (default setting for the attribute on debian/redhat family platforms, because the init script doesn't include the `pid_file` option which is set in the config.\n\nThe default Chef Server will be `http://localhost:4000` which is the `Chef::Config[:chef_server_url]` default value. To use the config recipe with the Opscode Platform, for example, add the following to the `override_attributes`\n\n override_attributes(\n \"chef_client\" => {\n \"server_url\" => \"https://api.opscode.com/organizations/ORGNAME\",\n \"validation_client_name\" => \"ORGNAME-validator\"\n }\n )\nWhere ORGNAME is your Opscode Platform organization name. Be sure to add these attributes to the role if modifying per the section below.\n\nYou can also set all of the `Chef::Config` http proxy related settings. By default Chef will not use a proxy.\n\n override_attributes(\n \"chef_client\" => {\n \"http_proxy\" => \"http://proxy.vmware.com:3128\",\n \"https_proxy\" => \"http://proxy.vmware.com:3128\",\n \"http_proxy_user\" => \"my_username\",\n \"http_proxy_pass\" => \"Awe_some_Pass_Word!\",\n \"no_proxy\" => \"*.vmware.com,10.*\"\n }\n )\n\nAlternate Init Styles\n---------------------\n\nThe alternate init styles available are:\n\n* runit\n* bluepill\n* daemontools\n\nFor usage, see below.\n\n# Runit\n\nTo use runit, download the cookbook from the cookbook site.\n\n knife cookbook site vendor runit -d\n\nChange the `init_style` to runit in the base role and add the runit recipe to the role's run list:\n\n name \"base\"\n description \"Base role applied to all nodes\"\n override_attributes(\n \"chef_client\" => {\n \"init_style\" => \"runit\"\n }\n )\n run_list(\n \"recipe[chef-client::delete_validation]\",\n \"recipe[runit]\",\n \"recipe[chef-client]\"\n )\n\nThe `chef-client` recipe will create the chef-client service configured with runit. The runit run script will be located in `/etc/sv/chef-client/run`. The output log will be in the runit service directory, `/etc/sv/chef-client/log/main/current`.\n\n# Bluepill\n\nTo use bluepill, download the cookbook from the cookbook site.\n\n knife cookbook site vendor bluepill -d\n\nChange the `init_style` to runit in the base role and add the bluepill recipe to the role's run list:\n\n name \"base\"\n description \"Base role applied to all nodes\"\n override_attributes(\n \"chef_client\" => {\n \"init_style\" => \"bluepill\"\n }\n )\n run_list(\n \"recipe[chef-client::delete_validation]\",\n \"recipe[bluepill]\",\n \"recipe[chef-client]\"\n )\n\nThe `chef-client` recipe will create the chef-client service configured with bluepill. The bluepill \"pill\" will be located in `/etc/bluepill/chef-client.pill`. The output log will be to client.log file in the `node[\"chef_client\"][\"log_dir\"]` location, `/var/log/chef/client` by default.\n\n# Daemontools\n\nTo use daemontools, download the cookbook from the cookbook site.\n\n knife cookbook site vendor daemontools -d\n\nChange the `init_style` to runit in the base role and add the daemontools recipe to the role's run list:\n\n name \"base\"\n description \"Base role applied to all nodes\"\n override_attributes(\n \"chef_client\" => {\n \"init_style\" => \"daemontools\"\n }\n )\n run_list(\n \"recipe[chef-client::delete_validation]\",\n \"recipe[daemontools]\",\n \"recipe[chef-client]\"\n )\n\nThe `chef-client` recipe will create the chef-cilent service configured under daemontools. It uses the same sv run scripts as the runit recipe. The run script will be located in `/etc/sv/chef-client/run`. The output log will be in the daemontools service directory, `/etc/sv/chef-client/log/main/current`.\n\nTEMPLATES\n=========\n\nchef-client.pill.erb\n--------------------\n\nBluepill configuration for the chef-client service.\n\nclient.rb.erb\n-------------\n\nConfiguration for the client, lands in `/etc/chef/client.rb`.\n\n`sv-chef-client-*run.erb`\n-------------------------\n\nRunit and Daemontools run script for chef-client service and logs.\n\nLogs will be located in the `node[\"chef_client\"][\"log_dir\"]`.\n\nLICENSE AND AUTHORS\n===================\n\n* Author: Joshua Timberman <joshua@opscode.com>\n* Author: Seth Chisamore <schisamo@opscode.com>\n* Copyright 2010-2011, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "ubuntu": ">= 0.0.0",
- "debian": ">= 0.0.0",
- "redhat": ">= 0.0.0",
- "centos": ">= 0.0.0",
- "fedora": ">= 0.0.0",
- "freebsd": ">= 0.0.0",
- "openbsd": ">= 0.0.0",
- "mac_os_x": ">= 0.0.0"
- },
- "dependencies": {
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "chef-client": "Includes the service recipe by default.",
- "chef-client::config": "Configures the client.rb from a template.",
- "chef-client::service": "Sets up a client daemon to run periodically",
- "chef-client::delete_validation": "Deletes validation.pem after client registers"
- },
- "version": "0.99.5"
-}
View
94 chef/metadata.json
@@ -1,94 +0,0 @@
-{
- "name": "chef",
- "description": "Installs and configures Chef for chef-client and chef-server",
- "long_description": "IMPORTANT CHANGES - version 0.99.9\n==================================\n\nIn the interest of user experience and clarity of intention, this cookbook is deprecated. It has been split into two cookbooks. For compatibility reasons, it will depend on the cookbooks it is split into and use the recipes from those cookbooks where applicable.\n\n* chef-client: All the client related configuration/setup.\n* chef-server: All the server related configuration/setup.\n\nDESCRIPTION\n===========\n\nThis cookbook is used to configure the system to be a Chef Client or a Chef Server. It is a complex cookbook, please read this entire document to understand how it works. For more information on how Chef itself works, see the [Chef Wiki](http://wiki.opscode.com)\n\nREQUIREMENTS\n============\n\nChef 0.8.16 or later is required.\n\nChef 0.9.0 or later is required to use the `chef.init_style` attribute value `init`, in order to have the init scripts available.\n\nPlatform\n--------\n\nIf using this cookbook to manage a Chef Server system that was installed from Debian/Ubuntu packages, note that in the packages, the configuration files are split up for server.rb, solr.rb and webui.rb, and the `chef::server` recipe may not work as desired.\n\nA recent version of Ubuntu or Debian is recommended for the Chef Server.\n\n* Ubuntu 9.10/10.04\n* Debian testing/unstable\n\nThese versions have newer versions of CouchDB and RabbitMQ packaged.\n\n`chef::client` is tested on Ubuntu 8.04+, Debian 5.0, CentOS 5.x, Fedora 10+, OpenBSD 4.6, FreeBSD 7.1 and Gentoo.\n\n`chef::bootstrap_client` is tested on the above. OpenSolaris 11 is also tested, but there's a bug in Ohai that requires some manual intervention (OHAI-122).\n\n`chef::server` is tested on Ubuntu 8.04+, Debian 5.0.\n\n`chef::bootstrap_server` is tested on Ubuntu 8.04+, Debian 5.0.\n\nClient\n------\n\n`runit` cookbook is suggested for RubyGems installation. No other cookbooks are required for clients.\n\nServer\n------\n\nThe `chef::bootstrap_server` recipe uses the following other cookbooks from Opscode.\n\n* couchdb\n* `rabbitmq_chef`\n* openssl\n* zlib\n* xml\n* java\n\nThe `chef::server_proxy` recipe uses the following cookbook:\n\n* apache2\n\nATTRIBUTES\n==========\n\nThe attributes for configuring the `chef` cookbook are under the `chef` namespace on the node, i.e., `@node[:chef]` or `@node.chef`.\n\nWhen using the bootstrap recipe, set the desired attributes using a JSON file. See \"BOOTSTRAPPING\" for examples.\n\numask\n-----\n\nSets the umask for files created by the server process via `Chef::Config[:umask]` in `/etc/chef/server.rb`\n\n`url_type`\n----------\n\nSet up the URLs the client should connect to with this. Default is `http`, which tells the client to connect to `http://server:4000`. If you set up your chef-server to use an SSL front-end for example with `chef::server_proxy`, set this to `https` for clients and the URLs will be `https://server/`.\n\nBy default the only URL config setting for Chef 0.8.x+ is `Chef::Config[:chef_server_url]`. The other older URLs are still supported so you can split out the various functions of the Chef Server, but configuration of those is outside the scope of this cookbook.\n\n`init_style`\n------------\n\nSpecifies the init style to use. Possible values:\n\n* runit - uses runit to set up the service. Logs will be in `/etc/sv/chef-client/log/main`. Default value for this attribute.\n* init - uses init scripts that are included in the `chef` gem. Logs will be in `/var/log/chef`. Only usable with debian/ubuntu and red hat family distributions.\n* daemontools - uses daemontools to set up the service. Logs will be in `/etc/sv/chef-client/log/main`.\n* bluepill - uses bluepill to set up the service.\n* bsd - Prints a message with the chef-client command to use in rc.local.\n\nIf your platform doesn't have a `runit` package or if the cookbook doesn't detect it, but you still want to use runit, set `init_style` to `none` and install runit separately. You may need to configure the runit services separately.\n\nUsing the `init` value for this attribute will retrieve the init scripts that are distributed with the Chef gem.\n\nThis cookbook does not yet support Upstart for Ubuntu/Debian, but that is planned for a future release, and will be specified via this attribute.\n\npath\n----\n\nThis is the base location where Chef will store data and other artifacts. Default `/srv/chef` for RubyGems installed systems. If using Chef packages for your platform, the location preference varies. The default on Debian and Red Hat based systems is a filesystem hiearchy standard (FHS) suggestion. Some other locations you may consider, by platform:\n\nDebian and Red Hat based Linux distros (Ubuntu, CentOS, Fedora, etc):\n\n* `/var/lib/chef`\n\nAny BSD and Gentoo:\n\n* `/var/chef`\n\n`run_path`\n----------\n\nLocation for pidfiles on systems using init scripts. Default `/var/run/chef`.\n\nIf `init_style` is `init`, this is used, and should match what the init script itself uses for the PID files.\n\n`cache_path`\n------------\n\nLocation where the client will cache cookbooks and other data. Default is `cache` underneath the `chef[:path]` location. Linux distributions adhering to the FHS prefer `/var/cache/chef` instead.\n\nBase directory for data that is easily regenerated such as cookbook tarballs (`Chef::Config[:cookbook_tarballs]`) on the server, downloaded cookbooks on the client, etc. See the config templates.\n\n`backup_path`\n-------------\n\nLocation where backups of files, corresponds to the `file_backup_path` location. Defaults to `backup` under `chef[:path]` location. Set to `false` to use the old behavior which stores the backup files in the same directory as the target.\n\nFHS location suggestion: `/var/lib/chef/backup`.\n\n`serve_path`\n------------\n\nUsed by the Chef server as the base location to \"serve\" cookbooks, roles and other assets. Default is `/srv/chef`.\n\n`server_version`\n----------------\n\nVersion of Chef to install for the server. Used by the `server_proxy` recipe to set the location of the DocumentRoot of the WebUI. Automatically determined via ohai's `chef_packages[:chef][:version]` by default.\n\n`client_version`\n----------------\n\nVersion of Chef to install for the client. Used to display a log message about the location of the init scripts when `init_style` is `init`, and can be used to upgrade `chef` gem with the `chef::bootstrap_client` recipe. Automatically determined via ohai's `chef_packages[:chef][:version]` by default.\n\n`client_interval`\n-----------------\n\nNumber of seconds to run chef-client periodically. Default `1800` (30 minutes).\n\n`client_splay`\n--------------\n\nSplay interval to randomly add to interval. Default `20`.\n\n`log_dir`\n---------\n\nWhen `init_style` is `init`, this directory needs to be created. The default is `/var/log/chef`.\n\n`client_log`, `indexer_log`, `server_log`\n-----------------------------------------\n\nThese options are deprecated to reduce complexity and potential confusion.\n\n`server_port`\n-------------\n\nPort for the Server API service to listen on. Default `4000`.\n\n`webui_port`\n------------\n\nPort for the Server WebUI service to listen on. Default `4040`.\n\n`webui_enabled`\n---------------\n\nAs of version 0.8.x+, the WebUI part of the Chef Server is optional, and disabled by default. To enable it, set this to true.\n\n`server_fqdn`\n-------------\n\nFully qualified domain name of the server. Default is `chef.domain` where domain is detected by Ohai. You should configure a DNS entry for your Chef Server.\n\nOn servers, this specifies the URL the server expects to use by default `Chef::Config[:chef_server_url]`, plus it is used in the `server_ssl_req` as the canonical name (CN) and in `server_proxy` for the vhost name.\n\nOn clients, this specifies the URL the client uses to connect to the server as `Chef::Config[:chef_server_url]`.\n\n`server_url`\n------------\n\nFull URI for the Chef Server. Used for `chef_server_url` config setting. The default value combines the attributes `chef.url_type`, `chef.server_fqdn` and `chef.server_port`, creating for example \"http://chef.example.com:4000\". If you are using the Opscode Platform, set this to \"https://api.opscode.com/organizations/ORGNAME\", where ORGNAME is your organization's simple string name.\n\nSERVER PROXY\n------------\n\nThe following attributes are used by the `server_proxy.rb` recipe, and are stored in the `server_proxy.rb` attributes file.\n\n`doc_root`\n----------\n\nDocumentRoot for the WebUI. Also gets set in the vhost for the API, but it is not used since the vhost merely proxies to the server on port 4000.\n\n`server_ssl_req`\n----------------\n\nUsed by the `server_proxy` recipe, this attribute can be used to set up a self-signed SSL certificate automatically using OpenSSL. Fields:\n\n* C: country (two letter code)\n* ST: state/province\n* L: locality or city\n* O: organization\n* OU: organizational unit\n* CN: canonical name, usually the fully qualified domain name of the server (FQDN)\n* emailAddress: contact email address\n\nThis attribute is now in the `server_proxy.rb` attributes file, as it is specific to that context.\n\n`server_proxy.css_expire_hours`\n-------------------------------\n\nSets expiration time for CSS in the WebUI.\n\n`server_proxy.js_expire_hours`\n------------------------------\n\nSets expiration time for JavaScript in the WebUI.\n\nRECIPES AND USAGE\n=================\n\nThis section describes the recipes in the cookbook and how to use them in your environment.\n\nBOOTSTRAPPING\n-------------\n\nThe first two recipes described are for \"bootstrapping\" a system to be a Chef Client or Chef Server, respectively. Only use these recipes with RubyGems installations of Chef.\n\nThese recipes are typically used with chef-solo using a JSON file of attributes and a run list, and a solo config file. For more information see [Bootstrap Chef RubyGems Installation](http://wiki.opscode.com/display/chef/Bootstrap+Chef+RubyGems+Installation) on the Chef Wiki.\n\n`bootstrap_client`\n------------------\n\nONLY FOR RUBYGEMS INSTALLATIONS. Do not use this recipe if you installed Chef from packages for your platform.\n\nUse this recipe to \"bootstrap\" a client so it can connect to a Chef Server. This recipe does the following:\n\n* Ensures the gem installed matches the version desired (`client_version` attribute).\n* Includes the `chef::client_service` recipe to ensure that `chef-client` is running as a service.\n* Sets up some directories for Chef to use.\n* Creates the client configuration file `/etc/chef/client.rb` based on the configuration passed via JSON.\n\nFor configuring a new client to connect to the Opscode Platform:\n\n {\n \"chef\": {\n \"server_url\": \"https://api.opscode.com/organizations/ORGNAME\"\n },\n \"run_list\": \"recipe[chef::bootstrap_client]\"\n }\n\nFor configuring a new client to connect to a local Chef Server:\n\n {\n \"chef\": {\n \"server_url\": \"http://chef.example.com:4000\"\n },\n \"run_list\": \"recipe[chef::bootstrap_client]\"\n }\n\nThis is the minimal JSON to use for the client configuration. See the ATTRIBUTES section above for more options.\n\n`bootstrap_server`\n------------------\n\nONLY FOR RUBYGEMS INSTALLATIONS. Do not use this recipe if you installed Chef from packages for your platform.\n\nUse this recipe to \"bootstrap\" a system to become a Chef Server. This recipe does the following:\n\n* Includes the `chef::bootstrap_client` recipe to configure itself to be its own client.\n* Installs CouchDB from package or source depending on the platform.\n* Installs Java for the `chef-solr` search engine.\n* Installs RabbitMQ (`rabbitmq_chef` cookbook) for the `chef-solr-indexer` consumer.\n* Installs all the Server-related Gems.\n* Creates the server configuration file `/etc/chef/server.rb` based on the configuration passed via JSON.\n* Sets up some directories for the server to use.\n* Sets up the `chef-server`, `chef-solr`, `chef-solr-indexer` services depending on the `init_style` attribute (see above).\n\nMinimal JSON to use for the server configuration:\n\n {\n \"chef\": {\n \"server_url\": \"http://localhost.localdomain:4000\",\n },\n \"run_list\": \"recipe[chef::bootstrap_server]\"\n }\n\nNote that the `chef-server-webui` is optional and can be enabled if desired by adding this to the JSON under \"chef\":\n\n \"webui_enabled\": true\n\nclient\n------\n\nThe client recipe is used to manage the configuration of an already-installed and configured Chef client. It can be used after a RubyGems installation bootstrap (per above), or with clients that were installed from platform packaging.\n\nThe recipe itself manages the `/etc/chef/client.rb` config file based on the attributes in this cookbook. When the client config is updated, the recipe will also reread the configuration during the Chef run, so the current Chef run can be dynamically changed.\n\nThis recipe does not manage the `chef-client` service. It is assumed to have been set up and started from the `bootstrap_client` recipe above, or from OS / distribution packaging. The `chef-client` service should not be restarted as a result of `/etc/chef/client.rb` changing, as that can cause the current process running the client to be restarted, having unpredictable results.\n\n`client_service`\n----------------\n\nUse this recipe on systems that should have a `chef-client` daemon running, such as when Knife bootstrap was used to install Chef on a new system.\n\nThis recipe sets up the `chef-client` service depending on the `init_style` attribute (see above). It is included by the `chef::bootstrap_client` recipe.\n\ndefault\n-------\n\nThere is no spoon :-).\n\n`delete_validation`\n-------------------\n\nUse this recipe to delete the validation certificate (default `/etc/chef/validation.pem`) when using a `chef-client` after the client has been validated and authorized to connect to the server.\n\nBeware if using this on your Chef Server. First copy the validation.pem certificate file to another location, such as your knife configuration directory (`~/.chef`) or [Chef Repository](http://wiki.opscode.com/display/chef/Chef+Repository).\n\nserver\n------\n\nThe server recipe includes the `chef::client` recipe above.\n\nThe recipe itself manages the services and the Server config file `/etc/chef/server.rb`. See above under Platform requirements for cavaet when running Chef Server installed via Debian/Ubuntu packages. Changes to the recipe to manage additional templates may be required.\n\nThe following services are managed:\n\n* chef-solr\n* chef-solr-indexer\n* chef-server\n* chef-webui (if installed)\n\nChanges to the `/etc/chef/server.rb` will trigger a restart of these services.\n\nSince the Chef Server itself typically runs the CouchDB service for the data store, the recipe will do a compaction on the Chef database and all the views associated with the Chef Server. These compactions only occur if the database/view size is more than 100Mb. It will use the configured CouchDB URL, which is `http://localhost:5984` by default. The actual value used for the CouchDB server is from the `Chef::Config[:couchdb_url]`, so this can be dynamically changed.\n\n`server_proxy`\n--------------\n\nThis recipe sets up an Apache2 VirtualHost to proxy HTTPS for the Chef Server API and WebUI.\n\nThe API will be proxied on port 443. If the `chef-serer-webui` is installed, it will be proxied on port 444. The recipe dynamically creates the OpenSSL certificate based on the `chef.server_ssl_req` attribute. It uses some additional configuration for Apache to improve performance of the webui. The virtual host template is `chef_server.conf.erb`. The DocumentRoot setting is used for the WebUI, but not the API, and is set with the attribute `chef.doc_root`.\n\nTEMPLATES\n=========\n\n`chef_server.conf.erb`\n----------------------\n\nVirtualHost file used by Apache2 in the `chef::server_proxy` recipe.\n\nclient.rb.erb\n-------------\n\nConfiguration for the client, lands in `/etc/chef/client.rb`.\n\nserver.rb.erb\n-------------\n\nConfiguration for the server and server components, lands in `/etc/chef/server.rb`. See above regarding Debian/Ubuntu packaging config files when using packages to install Chef.\n\n`sv-*run.erb`\n-------------\n\nVarious runit \"run\" scripts for the Chef services that get configured when `init_style` is \"runit\".\n\nLICENSE AND AUTHORS\n===================\n\n* Author: Joshua Timberman <joshua@opscode.com>\n* Author: Joshua Sierles <joshua@37signals.com>\n\n* Copyright 2008-2010, Opscode, Inc\n* Copyright 2009, 37signals\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "ubuntu": [
-
- ],
- "debian": [
-
- ],
- "redhat": [
-
- ],
- "centos": [
-
- ],
- "fedora": [
-
- ],
- "freebsd": [
-
- ],
- "openbsd": [
-
- ]
- },
- "dependencies": {
- "runit": [
-
- ],
- "bluepill": [
-
- ],
- "daemontools": [
-
- ],
- "couchdb": [
-
- ],
- "rabbitmq_chef": [
-
- ],
- "apache2": [
-
- ],
- "openssl": [
-
- ],
- "zlib": [
-
- ],
- "xml": [
-
- ],
- "java": [
-
- ],
- "chef-server": [
-
- ],
- "chef-client": [
-
- ]
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "chef": "Default recipe is empty, use one of the other recipes.",
- "chef::client": "Sets up a client to talk to a chef-server",
- "chef::client_service": "Sets up a client daemon to run periodically",
- "chef::bootstrap_client": "Set up rubygem installed chef client",
- "chef::delete_validation": "Deletes validation.pem after client registers",
- "chef::server": "Configures a chef API server as a merb application",
- "chef::bootstrap_server": "Set up rubygem installed chef server",
- "chef::server_proxy": "Configures Apache2 proxy for API and WebUI"
- },
- "version": "0.99.9"
-}
View
32 cloudkick/metadata.json
@@ -1,32 +0,0 @@
-{
- "name": "cloudkick",
- "description": "Installs/Configures the Cloudkick Agent",
- "long_description": "Description\n===========\n\nInstalls and configures the Cloudkick Agent, and integrates it with Chef.\n\nRequirements\n============\n\nPlatform\n--------\n\n* Debian, Ubuntu\n* CentOS, Red Hat, Fedora\n\nCookbooks\n---------\n\n* apt (leverages apt_repository LWRP)\n* yum (leverages yum_repository LWRP)\n\nThe `apt_repository` and `yum_repository` LWRPs are used from these cookbooks to create the proper repository entries so the cloudkick agent can be downloaded and installed.\n\nUsage\n=====\n\nIn order for the agent to function, you'll need to have defined your Cloudkick API key and secret. We recommend you do this in a Role, which should also take care of applying the cloudkick::default recipe.\n\nAssuming you name the role 'cloudkick', here is the required json:\n\n {\n \"name\": \"cloudkick\",\n \"chef_type\": \"role\",\n \"json_class\": \"Chef::Role\",\n \"default_attributes\": {\n\n },\n \"description\": \"Configures Cloudkick\",\n \"run_list\": [\n \"recipe[cloudkick]\"\n ],\n \"override_attributes\": {\n \"cloudkick\": {\n \"oauth_key\": \"YOUR KEY HERE\"\n \"oauth_secret\": \"YOUR SECRET HERE\"\n }\n }\n }\n\nIf you want Cloudkick installed everywhere, we recommend you just add the cloudkick attributes to a base role.\n\nAll of the data about the node from Cloudkick is available in node[:cloudkick] - for example: \n\n \"cloudkick\": {\n \"oauth_key\": \"YOUR KEY HERE\",\n \"oauth_secret\": \"YOUR SECRET HERE\",\n \"data\": {\n \"name\": \"slice204393\",\n \"status\": \"running\",\n \"ipaddress\": \"173.203.83.199\",\n \"provider_id\": \"padc2665\",\n \"tags\": [\n \"agent\",\n \"cloudkick\"\n ],\n \"agent_state\": \"connected\",\n \"id\": \"n87cfc79c5\",\n \"provider_name\": \"Rackspace\",\n \"color\": \"#fffffff\"\n }\n }\n\nOf particular interest is the inclusion of the Cloudkick tags. This will allow you to search Chef via tags placed on nodes within Cloudkick:\n\n $ knife search node 'cloudkick_data_tags:agent' -a fqdn\n {\n \"rows\": [\n {\n \"fqdn\": \"slice204393\",\n \"id\": \"slice204393\"\n }\n ],\n \"start\": 0,\n \"total\": 1\n }\n \nWe automatically add a tag for each Role applied to your node. For example, if your node had a run list of:\n\n \"run_list\": [ \"role[webserver]\", \"role[database_master]\" ]\n\nThe node will automatically have the 'webserver' and 'database_master' tags within Cloudkick.\n\nLicense and Author\n==================\n\nAuthor:: Adam Jacob (<adam@opscode.com>)\nAuthor:: Seth Chisamore (<schisamo@opscode.com>)\nCopyright:: 2010-2011, Opscode, Inc\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- },
- "dependencies": {
- "apt": ">= 0.0.0",
- "yum": ">= 0.0.0"
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "cloudkick::default": "Installs and configures Cloudkick"
- },
- "version": "1.0.1"
-}
View
55 couchdb/metadata.json
@@ -1,55 +0,0 @@
-{
- "name": "couchdb",
- "description": "Installs CouchDB package and starts service",
- "long_description": "Installs the CouchDB package if it is available from an package repository on\nthe node. If the package repository is not available, CouchDB needs to be \ninstalled via some other method, either a backported package, or compiled \ndirectly from source. CouchDB is available on Red Hat-based systems through\nthe EPEL Yum Repository.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "ubuntu": [
- ">= 8.10"
- ],
- "debian": [
- ">= 5.0"
- ],
- "openbsd": [
-
- ],
- "freebsd": [
-
- ],
- "rhel": [
-
- ],
- "centos": [
-
- ],
- "fedora": [
-
- ]
- },
- "dependencies": {
- "erlang": [
-
- ]
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "couchdb": "Installs and configures CouchDB package",
- "couchdb::source": "Installs and configures CouchDB from source"
- },
- "version": "0.14.1"
-}
View
29 cron/metadata.json
@@ -1,29 +0,0 @@
-{
- "providing": {
- },
- "attributes": {
- },
- "maintainer": "Opscode, Inc.",
- "replacing": {
- },
- "dependencies": {
- },
- "recipes": {
- },
- "maintainer_email": "cookbooks@opscode.com",
- "groupings": {
- },
- "recommendations": {
- },
- "platforms": {
- },
- "license": "Apache 2.0",
- "version": "0.0.1",
- "suggestions": {
- },
- "name": "cron",
- "conflicting": {
- },
- "long_description": "DESCRIPTION\n===========\n\nInstalls the cron package.\n\nREQUIREMENTS\n============\n\nWorks on any platform with a package named 'cron'.\n\nLICENSE AND AUTHOR\n==================\n\nAuthor:: Joshua Timberman (<joshua@opscode.com>)\n\nCopyright 2010, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "description": "Installs cron"
- }
View
45 daemontools/metadata.json
@@ -1,45 +0,0 @@
-{
- "name": "daemontools",
- "description": "Installs/Configures daemontools",
- "long_description": "Description\n===========\n\nInstalls DJB's Daemontools and includes a service LWRP.\n\nRequirements\n============\n\nShould work on ArchLinux, Debian and Ubuntu. May work on Red Hat family distributions.\n\nRequires build-essential and ucspi-tcp cookbooks.\n\nAttributes\n==========\n\n* `node[:daemontools][:bin_dir]` - Sets the location of the binaries for daemontools, default is selected by platform, or '/usr/local/bin' as a fallback.\n\nResource/Provider\n=================\n\nThis cookbook includes an LWRP for managing daemontools services.\n\nUsage\n=====\n\nLicense and Author\n==================\n\nAuthor: Joshua Timberman (<joshua@opscode.com>)\n\nCopyright 2010, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "debian": [
-
- ],
- "ubuntu": [
-
- ],
- "arch": [
-
- ]
- },
- "dependencies": {
- "build-essential": [
-
- ],
- "ucspi-tcp": [
-
- ]
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "daemontools": "Installs daemontools by source or package depending on platform"
- },
- "version": "0.9.0"
-}
View
43 database/metadata.json
@@ -1,43 +0,0 @@
-{
- "name": "database",
- "description": "Sets up the database master or slave",
- "long_description": "Database Cookbook\n=================\n\nConfigures mysql database masters and slaves and uses EBS for storage, integrating together with the application cookbook utilizing data bags for application related information.\n\nThis cookbook is written primarily to use MySQL and the Opscode mysql cookbook. Other RDBMS may be supported at a later date.\n\nThis cookbook does not automatically restore database dumps, but does install tools to help with that.\n\nRequirements\n============\n\nChef 0.8 or higher required.\n\nPlatform\n--------\n\nUbuntu, Debian, Red Hat, CentOS or Fedora.\n\nCookbooks\n---------\n\nThe following Opscode cookbooks are dependencies:\n\n* mysql\n* xfs\n* aws\n\nRecipes\n=======\n\n`ebs_volume`\n------------\n\nLoads the aws information from the data bag. Searches the applications data bag for the database master or slave role and checks that role is applied to the node. Loads the EBS information and the master information from data bags. Uses the aws cookbook LWRP, `aws_ebs_volume` to manage the volume.\n\nOn a master node:\n* if we have an ebs volume already as stored in a data bag, attach it.\n* if we don't have the ebs information then create a new one and attach it.\n* store the volume information in a data bag via a ruby block.\n\nOn a slave node:\n* use the master volume information to generate a snapshot.\n* create the new volume from the snapshot and attach it.\n\nAlso on a master node, generate some configuration for running a snapshot via `chef-solo` from cron.\n\nOn a new filesystem volume, create as XFS, then mount it in /mnt, and also bind-mount it to the mysql data directory (default /var/lib/mysql).\n\nmaster\n------\n\nThis recipe no longer loads AWS specific information, and the database position for replication is no longer stored in a databag because the client might not have permission to write to the databag item. This may be handled in a different way at a future date.\n\nSearches the apps databag for applications, and for each one it will check that the specified database master role is set in both the databag and applied to the node's run list. Then, retrieves the passwords for `root`, `repl` and `debian` users and saves them to the node attributes. If the passwords are not found in the databag, it prints a message that they'll be generated by the mysql cookbook.\n\nThen it adds the application databag database settings to a hash, to use later.\n\nIt sets up the template resource for `/etc/mysql/app_grants.sql`, passing in the database settings so privileges for application specific database users can be created.\n\nThen it will iterate over the databases and create them with the `mysql_database` LWRP, detecting their presence with the mysql rubygem.\n\nslave\n-----\n\n_TODO_: Retrieve the master status from a data bag, then start replication using a ruby block. The replication status needs to be handled in some other way for now since the master recipe above doesn't actually set it in the databag anymore.\n\nsnapshot\n--------\n\nRun via Chef Solo. Retrieves the db snapshot configuration from the specified JSON file. Uses the `mysql_database` LWRP to lock and unlock tables, and does a filesystem freeze and EBS snapshot.\n\nDeprecated Recipes\n==================\n\nThe following recipe is considered deprecated. It is kept for reference purposes.\n\n`ebs_backup`\n------------\n\nOlder style of doing mysql snapshot and replication using Adam Jacob's [ec2_mysql](http://github.com/adamhjk/ec2_mysql) script and library.\n\nData Bags\n=========\n\nThis cookbook uses the apps data bag item for the specified application; see the `application` cookbook's README.md. It also creates data bag items in a bag named 'aws' for storing volume information. In order to interact with EC2, it expects aws to have a main item:\n\n {\n \"id\": \"main\",\n \"ec2_private_key\": \"private key as a string\",\n \"ec2_cert\": \"certificate as a string\",\n \"aws_account_id\": \"\",\n \"aws_secret_access_key\": \"\",\n \"aws_access_key_id\": \"\"\n }\n\nNote: with the Open Source Chef Server, the server using the database recipes must be an admin client or it will not be able to create data bag items. You can modify whether the client is admin by editing it with knife.\n\n knife client edit <client_name>\n {\n ...\n \"admin\": true\n ...\n }\n\nThis is not required if the Chef Server is the Opscode Platform, instead use the ACL feature to modify access for the node to be able to update the data bag.\n\nUsage\n=====\n\nAside from the application data bag (see the README in the application cookbook), create a role for the database master. Use a role.rb in your chef-repo, or create the role directly with knife.\n\n % knife role show my_app_database_master\n {\n \"name\": \"my_app_database_master\",\n \"chef_type\": \"role\",\n \"json_class\": \"Chef::Role\",\n \"default_attributes\": {\n },\n \"description\": \"\",\n \"run_list\": [\n \"recipe[mysql::server]\",\n \"recipe[database::master]\"\n ],\n \"override_attributes\": {\n }\n }\n\nAlso create a `production` role, or other role based on your desired environment. This is also used in the `application` cookbook.\n\n % knife role show production\n {\n \"name\": \"production\",\n \"chef_type\": \"role\",\n \"json_class\": \"Chef::Role\",\n \"default_attributes\": {\n \"app_environment\": \"production\"\n },\n \"description\": \"production environment role\",\n \"run_list\": [\n\n ],\n \"override_attributes\": {\n }\n }\n\nThe cookbook `my_app_database` is recommended to set up any application specific database resources such as configuration templates, trending monitors, etc. It is not required, but you would need to create it separately in `site-cookbooks`. Add it to the `my_app_database_master` role.\n\nLicense and Author\n==================\n\nAuthor:: Adam Jacob (<adam@opscode.com>)\nAuthor:: Joshua Timberman (<joshua@opscode.com>)\nAuthor:: AJ Christensen (<aj@opscode.com>)\nAuthor:: Seth Chisamore (<schisamo@opscode.com>)\n\nCopyright 2009-2011, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "debian": ">= 0.0.0",
- "ubuntu": ">= 0.0.0",
- "centos": ">= 0.0.0",
- "suse": ">= 0.0.0",
- "fedora": ">= 0.0.0",
- "redhat": ">= 0.0.0"
- },
- "dependencies": {
- "mysql": ">= 0.0.0",
- "aws": ">= 0.0.0",
- "xfs": ">= 0.0.0"
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "database": "Empty placeholder",
- "database::ebs_backup": "Considered deprecated, older way of backing up EBS volumes",
- "database::ebs_volume": "Sets up an EBS volume in EC2 for the database",
- "database::master": "Creates application specific user and database",
- "database::snapshot": "Locks tables and freezes XFS filesystem for replication, assumes EC2 + EBS"
- },
- "version": "0.99.0"
-}
View
164 djbdns/metadata.json
@@ -1,164 +0,0 @@
-{
- "name": "djbdns",
- "description": "Installs djbdns and configures DNS services",
- "long_description": "",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "ubuntu": [
-
- ],
- "debian": [
-
- ],
- "centos": [
-
- ],
- "rhel": [
-
- ],
- "arch": [
-
- ]
- },
- "dependencies": {
- "build-essential": [
-
- ],
- "runit": [
-
- ],
- "daemontools": [
-
- ],
- "bluepill": [
-
- ],
- "ucspi-tcp": [
-
- ]
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- "djbdns/tinydns_ipaddress": {
- "display_name": "DJB DNS TinyDNS IP Address",
- "description": "Specify the IP address for TinyDNS",
- "default": "127.0.0.1",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "djbdns/tinydns_internal_ipaddress": {
- "display_name": "DJB DNS TinyDNS Internal IP Address",
- "description": "Specify the IP address for internal TinyDNS",
- "default": "127.0.0.1",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "djbdns/axfrdns_ipaddress": {
- "display_name": "DJB DNS AXFR IP Address",
- "description": "Specify the IP address for AXFR service",
- "default": "127.0.0.1",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "djbdns/public_dnscache_ipaddress": {
- "display_name": "DJB DNS Public DNS Cache IP Address",
- "description": "Specify the IP address for the public dnscache",
- "default": "ipaddress",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "djbdns/public_dnscache_allowed_networks": {
- "display_name": "DJB DNS Public DNS Cache Allowed Networks",
- "description": "Networks allowed to query the public dnscache",
- "type": "array",
- "default": [
- "ipaddress.split('.')[0,2].join('.')"
- ],
- "choice": [
-
- ],
- "calculated": false,
- "required": "optional",
- "recipes": [
-
- ]
- },
- "djbdns/tinydns_internal_resolved_domain": {
- "display_name": "DJB DNS TinyDNS Internal Resolved Domain",
- "description": "Internal domain TinyDNS is resolver",
- "default": "domain",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "djbdns/bin_dir": {
- "display_name": "DJB DNS Binaries Directory",
- "description": "Location of the djbdns binaries",
- "default": "/usr/local/bin",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- }
- },
- "groupings": {
- },
- "recipes": {
- "djbdns": "Installs djbdns from package or source and creates users",
- "djbdns::axfr": "Sets up djbdns AXFR service",
- "djbdns::cache": "Sets up public dnscache service",
- "djbdns::internal_server": "Sets up internal TinyDNS",
- "djbdns::server": "Sets up external TinyDNS"
- },
- "version": "0.99.0"
-}
View
39 drbd/metadata.json
@@ -1,39 +0,0 @@
-{
- "recommendations": {
- },
- "attributes": {
- },
- "maintainer": "Opscode, Inc.",
- "suggestions": {
- },
- "dependencies": {
- "lvm": [
-
- ]
- },
- "maintainer_email": "cookbooks@opscode.com",
- "conflicting": {
- },
- "platforms": {
- "debian": [
-
- ],
- "ubuntu": [
-
- ]
- },
- "license": "Apache 2.0",
- "version": "0.7.1",
- "providing": {
- },
- "recipes": {
- "drbd": "Installs drbd"
- },
- "replacing": {
- },
- "name": "drbd",
- "description": "Installs but does not configure drbd",
- "groupings": {
- },
- "long_description": ""
- }
View
32 dynect/metadata.json
@@ -1,32 +0,0 @@
-{
- "name": "dynect",
- "description": "LWRP for managing DNS records with Dynect's REST API",
- "long_description": "DESCRIPTION\n===========\n\nAutomatically configures system DNS using Dyn's API.\n\nREQUIREMENTS\n============\n\nChef 0.8+.\n\nA Dynect account.\n\nThe `dynect_rest` gem. The `dynect::default` recipe installs this gem from gemcutter.\n\nWorks on any platform Chef runs on that can install gems from Rubygems.org.\n\nATTRIBUTES\n==========\n\nThe following attributes need to be set either in a role or on a node directly, they are not set at the cookbook level:\n\n* dynect.customer - Customer ID\n* dynect.username - Username\n* dynect.password - Password\n* dynect.zone - Zone\n* dynect.domain - Domain\n\nExample JSON:\n\n {\n \"dynect\": {\n \"customer\": \"CUSTOMER\",\n \"username\": \"USERNAME\",\n \"password\": \"PASSWORD\",\n \"zone\": \"ZONE\",\n \"domain\": \"DOMAIN\"\n }\n }\n\nEC2 specific attributes:\n\n* dynect.ec2.type - type of system, web, db, etc. Default is 'ec2'.\n* dynect.ec2.env - logical application environment the system is in. Default is 'prod'.\n\nRESOURCES\n=========\n\nrr\n--\n\nDNS Resource Record.\n\nActions:\n\nApplies to the DNS record being managed.\n\n* `:create`\n* `:replace`\n* `:update`\n* `:delete`\n\nAttribute Parameters:\n\n* `record_type` - DNS record type (CNAME, A, etc)\n* `rdata` - record data, see the Dyn API documentation.\n* `ttl` - time to live in seconds\n* `fqdn` - fully qualified domain name\n* `username` - dyn username\n* `password` - dyn password\n* `customer` - dyn customer id\n* `zone` - DNS zone\n\nNone of the parameters have default values.\n\nExample:\n\n dynect_rr \"webprod\" do\n record_type \"A\"\n rdata({\"address\" => \"10.1.1.10\"})\n fqdn \"webprod.#{node.dynect.domain}\"\n customer node[:dynect][:customer]\n username node[:dynect][:username]\n password node[:dynect][:password]\n zone node[:dynect][:zone]\n end\n\nRECIPES\n=======\n\nThis cookbook provides the following recipes.\n\ndefault\n-------\n\nThe default recipe installs Adam Jacob's `dynect_rest` gem during the Chef run's compile time to ensure it is available in the same run as utilizing the `dynect_rr` resource/provider.\n\nec2\n---\n\n**Only use this recipe on Amazon AWS EC2 hosts!**\n\nThe `dynect::ec2` recipe provides an example of working with the Dyn API with EC2 instances. It creates CNAME records based on the EC2 instance ID (`node.ec2.instance_id`), and a constructed hostname from the dynect.ec2 attributes.\n\nThe recipe also edits resolv.conf to search compute-1.internal and the dynect.domain and use dynect.domain as the default domain, and it will set the nodes hostname per the DNS settings.\n\na_record\n--------\n\nThe `dynect::a_record` recipe will create an `A` record for the node using the detected hostname and IP address from `ohai`.\n\nFURTHER READING\n===============\n\nInformation on the Dynect API:\n\n* [PDF](http://cdn.dyndns.com/pdf/Dynect-API.pdf)\n\nDynect REST Ruby Library:\n\n* [Gem](http://rubygems.org/gems/dynect_rest)\n* [Code](http://github.com/adamhjk/dynect_rest)\n\nLICENSE AND AUTHOR\n==================\n\n- Author: Adam Jacob (<adam@opscode.com>)\n- Copyright: 2010, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- },
- "dependencies": {
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "dynect": "Installs the dynect_rest RubyGem",
- "dynect::ec2": "Dynamically configures Dyn resource records for EC2 nodes based on instance ID and prepopulated attributes on the node",
- "dynect::a_record": "Example resource usage to configure an A record"
- },
- "version": "0.3.2"
-}
View
42 emacs/metadata.json
@@ -1,42 +0,0 @@
-{
- "recommendations": {
- },
- "attributes": {
- },
- "maintainer": "Opscode, Inc.",
- "suggestions": {
- },
- "dependencies": {
- },
- "maintainer_email": "cookbooks@opscode.com",
- "conflicting": {
- },
- "platforms": {
- "debian": [
-
- ],
- "centos": [
-
- ],
- "ubuntu": [
-
- ],
- "redhat": [
-
- ]
- },
- "license": "Apache 2.0",
- "version": "0.7.0",
- "providing": {
- },
- "recipes": {
- "emacs": "Installs Emacs"
- },
- "replacing": {
- },
- "name": "emacs",
- "description": "Installs emacs",
- "groupings": {
- },
- "long_description": ""
- }
View
36 erlang/metadata.json
@@ -1,36 +0,0 @@
-{
- "providing": {
- },
- "attributes": {
- },
- "replacing": {
- },
- "dependencies": {
- },
- "groupings": {
- },
- "recommendations": {
- },
- "platforms": {
- "debian": [
-
- ],
- "ubuntu": [
-
- ]
- },
- "license": "Apache 2.0",
- "version": "0.8.2",
- "maintainer": "Opscode, Inc.",
- "suggestions": {
- },
- "recipes": {
- "erlang": "Installs erlang"
- },
- "maintainer_email": "cookbooks@opscode.com",
- "name": "erlang",
- "conflicting": {
- },
- "description": "Installs erlang, optionally install GUI tools.",
- "long_description": ""
- }
View
36 fail2ban/metadata.json
@@ -1,36 +0,0 @@
-{
- "recommendations": {
- },
- "attributes": {
- },
- "maintainer": "Opscode, Inc.",
- "suggestions": {
- },
- "dependencies": {
- },
- "maintainer_email": "cookbooks@opscode.com",
- "conflicting": {
- },
- "platforms": {
- "debian": [
-
- ],
- "ubuntu": [
-
- ]
- },
- "license": "Apache 2.0",
- "version": "1.0.0",
- "providing": {
- },
- "recipes": {
- "fail2ban": "Installs and configures fail2ban"
- },
- "replacing": {
- },
- "name": "fail2ban",
- "description": "Installs and configures fail2ban",
- "groupings": {
- },
- "long_description": ""
- }
View
35 gecode/metadata.json
@@ -1,35 +0,0 @@
-{
- "name": "gecode",
- "description": "Installs gecode",
- "long_description": "Description\n===========\n\nInstalls Gecode 3.5.0+ development package.\n\nRequirements\n============\n\nTested on Ubuntu and Debian with Opscode APT repository and build from source.\n\nTested on CentOS for build from source. See USAGE for information on installing RPMs.\n\nRequires the following cookbooks:\n\n* apt - for installing packages from apt.opscode.com\n* build-essential - for compiling from source\n\nUsage\n=====\n\nThe recipe is primarily used to install gecode's development package or from source in order to install the `dep_selector` gem, which needs to compile native extensions.\n\nNote that compiling gecode takes a long time, up to ~30 minutes on a 4 core Macbook Pro.\n\nOn Debian and Ubuntu systems, the recipe will attempt to install packages from apt.opscode.com. It uses the apt repository LWRP in Opscode's apt cookbook to enable the repository.\n\nOn Red Hat family distros, the recipe will attempt to install gecode from source. To install using a package the recipe needs to be updated to account for a package repository. Implementation varies depending on the package repository. For example, to retrieve the /etc/yum.repos.d/somewhere.repo that has the package available, add a condition to the main 'if' block:\n\n remote_file \"/etc/yum.repos.d/somewhere.repo\" do\n source \"http://somewhere.example.com/yum/el5/somewhere.repo\"\n owner \"root\"\n group \"root\"\n mode 0644\n end\n\n package \"gecode-devel\"\n\nLicense and Author\n==================\n\nAuthor:: Chris Walters (<cw@opscode.com>)\nAuthor:: Nuo Yan (<nuo@opscode.com>)\nAuthor:: Joshua Timberman (<joshua@opscode.com>)\n\nCopyright 2009-2011, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- },
- "dependencies": {
- "apt": [
-
- ],
- "build-essential": [
-
- ]
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- },
- "version": "0.99.0"
-}
View
99 gems/metadata.json
@@ -1,99 +0,0 @@
-{
- "name": "gems",
- "description": "Sets up a local gem server repository or mirror",
- "long_description": "= DESCRIPTION:\n\nSets up a local gem server repository.\n\n= REQUIREMENTS:\n\n== Platform:\n\nTested on Ubuntu 8.10 and 9.04.\n\n== Cookbooks:\n\nOpscode cookbooks, http://github.com/opscode/cookbooks/tree/master\n\n* apache2\n\n= ATTRIBUTES: \n\n* gem_server[:virtual_host_name] - ServerName for Apache vhost. Default 'gems.domain'.\n* gem_server[:virtual_host_alias] - ServerAlias(es) for Apache vhost. Default 'gems'.\n* gem_server[:directory] - Filesystem location for the repository, default is /srv/gems.\n\n= USAGE:\n\nCreate files/default/packages, and copy gems to that directory.\n\nSpecify the gem source on clients via the command line, for example:\n\n sudo gem source -a http://gems\n sudo gem install rails --source http://gems\n\nOr use the source with gem_package resources in your chef recipes.\n\n gem_package \"rails\" do\n source \"http://gems\"\n end\n\nUse the gems::mirror recipe to mirror RubyForge. This will take a long time because the repository is 28k+ gems and over 5.5G. It will also override the remote_directory resource to not notify gem generate_index, and instead handle that in the cron job that does the rsync.\n\n= LICENSE and AUTHOR:\n \nAuthor:: Joshua Timberman (<joshua@opscode.com>)\n\nCopyright:: 2009, Opscode, Inc\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "ubuntu": [
-
- ],
- "debian": [
-
- ]
- },
- "dependencies": {
- "apache2": [
-
- ],
- "rsync": [
-
- ]
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- "gem_server": {
- "display_name": "Gem Server",
- "description": "Hash of Gem Server attributes",
- "type": "hash",
- "choice": [
-
- ],
- "calculated": false,
- "required": "optional",
- "recipes": [
-
- ]
- },
- "gem_server/virtual_host_name": {
- "display_name": "Gem Server Virtual Hostname",
- "description": "Apache ServerName for the virtual host",
- "default": "gems.domain",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- },
- "gem_server/virtual_host_alias": {
- "display_name": "Gem Server Virtual Host Aliases",
- "description": "Array of Apache ServerAlias'es",
- "type": "array",
- "default": "gems",
- "choice": [
-
- ],
- "calculated": false,
- "required": "optional",
- "recipes": [
-
- ]
- },
- "gem_server/directory": {
- "display_name": "Gem Server Directory",
- "description": "Filesystem location of where the gems repository is served from",
- "default": "/srv/gems",
- "choice": [
-
- ],
- "calculated": false,
- "type": "string",
- "required": "optional",
- "recipes": [
-
- ]
- }
- },
- "groupings": {
- },
- "recipes": {
- "gems": "Empty, use one of the other recipes",
- "gems::server": "Sets up a local gem server repository",
- "gems::mirror": "Crons an rsync of rubyforge"
- },
- "version": "1.0.0"
-}
View
43 git/metadata.json
@@ -1,43 +0,0 @@
-{
- "name": "git",
- "description": "Installs git and/or sets up a Git server daemon",
- "long_description": "= DESCRIPTION:\n\nInstalls git.\n\n= REQUIREMENTS:\n\n== Cookbooks:\n\nOpscode Cookbooks (http://github.com/opscode/cookbooks/tree/master)\n\n* runit\n\n= USAGE:\n\nThis cookbook primarily installs git core packages. It can also be used to serve git repositories.\n\n include_recipe \"git::server\"\n\nThis creates the directory /srv/git and starts a git daemon, exporting all repositories found. Repositories need to be added manually, but will be available once they are created.\n\n= LICENSE and AUTHOR:\n \nAuthor:: Joshua Timberman (<joshua@opscode.com>)\n\nCopyright:: 2009, Opscode, Inc\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "ubuntu": [
-
- ],
- "debian": [
-
- ],
- "arch": [
-
- ]
- },
- "dependencies": {
- "runit": [
-
- ]
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "git": "Installs git",
- "git::server": "Sets up a runit_service for git daemon"
- },
- "version": "0.9.0"
-}
View
32 gnu_parallel/metadata.json
@@ -1,32 +0,0 @@
-{
- "name": "gnu_parallel",
- "description": "Installs/Configures gnu_parallel",
- "long_description": "Description\n===========\n\nInstalls GNU parallel.\n\nRequirements\n============\n\nRequires `build-essential` cookbook for installing from source, which is the default.\n\nAttributes\n==========\n\nFor now see the attributes file :).\n\nUsage\n=====\n\nInclude recipe in a run list, get some GNU parallel installed. Set attributes (see attributes file for available values and defaults).\n\nLicense and Author\n==================\n\nAuthor:: Joshua Timberman (<joshua@opscode.com>)\n\nCopyright 2011, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- },
- "dependencies": {
- "build-essential": [
-
- ]
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- },
- "version": "0.99.1"
-}
View
39 god/metadata.json
@@ -1,39 +0,0 @@
-{
- "name": "god",
- "description": "Installs and configures god and provides a define for monitoring",
- "long_description": "= DESCRIPTION:\n\nInstalls god gem, sets up modular configuration directory and provides a define to monitor processes.\n\n= REQUIREMENTS:\n\n== Platform and Application Environment:\n\nTested on Ubuntu 8.10. May work on other platforms, esp Ubuntu/Debian. Sample configuration file uses mongrel_runit for managing mongrels via runit. \n\n== Cookbooks:\n\nOpscode cookbooks, http://github.com/opscode/cookbooks/tree/master:\n\n* ruby\n* runit\n\nOpscode does not yet have a mongrel_runit cookbook.\n\n= ATTRIBUTES: \n\nNo attributes are used.\n\n= USAGE:\n\nThis recipe is designed to be used through the god_monitor define. Create a god configuration file in your application's cookbook and then call god_monitor:\n\n god_monitor \"myproj\" do\n config \"myproj.god.erb\"\n end\n\nA sample mongrel.god.erb is provided, though it assumes mongrel_runit is used. This can be used as a baseline for customization.\n\n= LICENSE and AUTHOR:\n \nAuthor:: Joshua Timberman (<joshua@opscode.com>)\nCopyright:: 2009, Opscode, Inc\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- "debian": [
-
- ],
- "ubuntu": [
-
- ]
- },
- "dependencies": {
- "runit": [
-
- ]
- },
- "recommendations": {
- },
- "suggestions": {
- },
- "conflicting": {
- },
- "providing": {
- },
- "replacing": {
- },
- "attributes": {
- },
- "groupings": {
- },
- "recipes": {
- "god": "Installs god and starts it as a runit service"
- },
- "version": "1.0.0"
-}
View
32 gunicorn/metadata.json
@@ -1,32 +0,0 @@
-{
- "name": "gunicorn",
- "description": "Installs/Configures Gunicorn",
- "long_description": "Description\n===========\n\nInstalls and configures the latest version of Gunicorn (via pip), aka `Green Unicorn`, a Python WSGI HTTP Server for UNIX. It's a pre-fork worker model ported from Ruby's Unicorn project. Includes an LWRP for managing Gunicorn config files. By default Gunicorn is installed system-wide but you can target a particular `virtualenv` by overriding the `node[\"gunicorn\"][\"virtualenv\"]` attribute.\n\nRequirements\n============\n\nPlatform\n--------\n\n* Debian, Ubuntu\n* CentOS, Red Hat, Fedora\n\nCookbooks\n---------\n\n* python\n\nAttributes\n==========\n\n* `node[\"gunicorn\"][\"virtualenv\"]` - the virtualenv you want to target Gunicorn installation into. The virtualenv will be created if it doesn't exist.\n\nResource/Provider\n=================\n\nThis cookbook includes LWRPs for managing gunicorn config files.\n\n`gunicorn_config`\n-----------------\n\nCreates a Gunicorn configuration file at the path specified. Meant to be deployed with a service init scheme/supervisor such as runit. Please see the `appliation::gunicorn` recipe for a complete working example. In depth information about Gunicorn's configuration values can be [found in the Gunicorn documentation](http://gunicorn.org/configure.html).\n\n# Actions\n\n- :create: create a Gunicorn configuration file.\n- :delete: delete an existing Gunicorn configuration file.\n\n# Attribute Parameters\n\n- path: name attribute. The path where the configuration file will be created\n- template: template to use when rendering the configuration file. default is `gunicorn.py.erb` (part of this cookbook)\n- cookbook: cookbook to look for template file in. default is this cookbook `gunicorn`\n- listen: the socket to bind to. A string of the form: 'HOST', 'HOST:PORT', 'unix:PATH'. default is `0.0.0.0:8000` or listen on port 8000 on all interfaces\n- backlog: The maximum number of pending connections. default is `2048`\n- preload_app: Whether application code should be loaded before the worker processes are forked. default is `false`\n- worker_processes: The number of worker process for handling requests. default is `4`\n- worker_class: The type of workers to use. default is `sync`\n- worker_timeout: The number of seconds to wait before a worker is killed and restarted. default is `60`\n- worker_keepalive: The number of seconds to wait for requests on a Keep-Alive connection. default is `2`\n- worker_max_requests: The maximum number of requests a worker will process before restarting. default is `0` or restarts disabled\n- server_hooks: A hash with whose values will be rendered as a [Gunicorn server hook](http://gunicorn.org/configure.html#server-hooks) callables (functions) named after the hash item's key name. default is `{}` or no serves hooks\n- owner: The owner for the configuration file.\n- group: The group owner of the configuration file (string or id).\n- pid: A filename to use for the PID file. default is no pidfile\n\n# Example\n \n # create a config with the default values\n gunicorn_config \"/etc/gunicorn/myapp.py\" do\n action :create\n end\n \n # tweak some worker related values...we're web scale baby\n gunicorn_config \"/etc/gunicorn/myapp.py\" do\n worker_processes 8\n backlog 4096\n action :create\n end\n \n # use the 'pre_fork' server hook to \n # sleep for a second before forking\n gunicorn_config \"/etc/gunicorn/myapp.py\" do\n server_hooks({:pre_fork => 'import time;time.sleep(1)'})\n action :create\n end\n \nUsage\n=====\n\nSimply include the recipe where you want Gunicorn installed.\n\nLicense and Author\n==================\n\nAuthor:: Seth Chisamore (<schisamo@opscode.com>)\n\nCopyright:: 2011, Opscode, Inc\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
- "maintainer": "Opscode, Inc.",
- "maintainer_email": "cookbooks@opscode.com",
- "license": "Apache 2.0",
- "platforms": {
- },
- "dependencies": {