Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms


noosfero (48) Versions 1.1.0

Install/configure Noosfero social-economic network

cookbook 'noosfero', '= 1.1.0'
cookbook 'noosfero', '= 1.1.0', :supermarket
knife cookbook site install noosfero
knife cookbook site download noosfero

noosfero Cookbook

Install/configure Noosfero social-economic network (see



The default recipe runs others recipes according to the settings <table> <tr> <th>Attribute</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>node[:noosfero][:service_name]</tt></td> <td>The Noosfero's service name, which define the init.d script name and paths</td> <td><tt>"noosfero"</tt></td> </tr> <tr> <td><tt>node[:noosfero][:rails_env]</tt></td> <td>The Rails environment to be used</td> <td><tt>"production"</tt></td> </tr> <tr> <td><tt>node[:noosfero][:rvm_load]</tt></td> <td>The ruby string to be load (e.g. "ree@noosfero")</td> <td><tt>"system"</tt></td> </tr> </table>


<table> <tr> <th>Attribute</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>node[:noosfero][:install_from]</tt></td> <td>What is used to install noosfero: "git" (default) to fetch code from git and "package" to install noosfero from debian repository</td> <td><tt>"git"</tt></td> </tr> </table>

noosfero::git_install (on install_from == "git")

<table> <tr> <th>Attribute</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>node[:noosfero][:user]</tt></td> <td>The user to create and to run noosfero</td> <td><tt>default[:noosfero][:service_name]</tt></td> </tr> <tr> <td><tt>node[:noosfero][:group]</tt></td> <td>The group to create and to run noosfero</td> <td><tt>default[:noosfero][:service_name]</tt></td> </tr> <tr> <td><tt>node[:noosfero][:git_url]</tt></td> <td>The git repo containing Noosfero to be used</td> <td><tt></tt></td> </tr> <tr> <td><tt>node[:noosfero][:git_revision]</tt></td> <td>The branch, tag or commit to be used</td> <td><tt>"stable"</tt></td> </tr> <tr> <td><tt>node[:noosfero][:upgrade_script]</tt></td> <td>A script to be run on git sync</td> <td><tt>''</tt></td> </tr> <tr> <th colspan=3>Paths</th> </tr> <tr> <td><tt>node[:noosfero][:path]</tt></td> <td>Set the path to clone the git repo to be the base path for code, log, tmp and others noosfero directories</td> <td><tt>nil</tt> (use default system dirs, see below)</td> </tr> <tr> <td><tt>node[:noosfero][:code_path]</tt></td> <td>Overwrite the code's path</td> <td> <tt>node[:noosfero][:path]</tt> (with node[:noosfero][:path]) <br> <tt>"/usr/share/#{service_name}"</tt> (without node[:noosfero][:path]) </td> </tr> <tr> <td><tt>node[:noosfero][:data_path]</tt></td> <td>Overwrite the data path</td> <td> <tt>node[:noosfero][:path]</tt> (with node[:noosfero][:path]) <br> <tt>"/var/lib/#{service_name}"</tt> (without node[:noosfero][:path]) </td> </tr> <tr> <td><tt>node[:noosfero][:config_path]</tt></td> <td>Overwrite the config path</td> <td> <tt>"#{node[:noosfero][:path]}/config"</tt> (with node[:noosfero][:path]) <br> <tt>"/etc/#{service_name}"</tt> (without node[:noosfero][:path]) </td> </tr> <tr> <td><tt>node[:noosfero][:log_path]</tt></td> <td>Overwrite the log path</td> <td> <tt>"#{node[:noosfero][:path]}/log"</tt> (with node[:noosfero][:path]) <br> <tt>"/var/log/#{service_name}"</tt> (without node[:noosfero][:path]) </td> </tr> <tr> <td><tt>node[:noosfero][:run_path]</tt></td> <td>Overwrite the run path</td> <td> <tt>"#{node[:noosfero][:path]}/run"</tt> (with node[:noosfero][:path]) <br> <tt>"/var/run/#{service_name}"</tt> (without node[:noosfero][:path]) </td> </tr> <tr> <td><tt>node[:noosfero][:tmp_path]</tt></td> <td>Overwrite the tmp path</td> <td> <tt>"#{node[:noosfero][:path]}/tmp"</tt> (with node[:noosfero][:path]) <br> <tt>"/var/tmp/#{service_name}"</tt> (without node[:noosfero][:path]) </td> </tr> </table>

noosfero::package_install (on install_from == "package")

Install noosfero using the Colivre's apt repository <table> <tr> <th>Attribute</th> <th>Description</th> <th>Default</th> </tr> </table>

noosfero::dependencies (on install_from == "git")

<table> <tr> <th>Attribute</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>node[:noosfero][:dependencies_with]</tt></td> <td>How to install dependencies: "quick_start", "bundler" or "packages" </td> <td> <tt>"quick_start"</tt> </td> </tr> </table>

noosfero::database (on install_from == "git")

Generate Rails' database.yml <table> <tr> <th>Attribute</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>node[:noosfero][:db][:name]</tt></td> <td>Database name</td> <td> <tt>node[:noosfero][:service_name]</tt> </td> </tr> <tr> <td><tt>node[:noosfero][:db][:hostname]</tt></td> <td>Database host</td> <td> <tt>"localhost"</tt> </td> </tr> <tr> <td><tt>node[:noosfero][:db][:port]</tt></td> <td>Database port</td> <td> <tt>""</tt> </td> </tr> <tr> <td><tt>node[:noosfero][:db][:username]</tt></td> <td>Database username</td> <td> <tt>node[:noosfero][:user]</tt> </td> </tr> <tr> <td><tt>node[:noosfero][:db][:password]</tt></td> <td>Database password</td> <td> <tt>""</tt> </td> </tr> </table>

noosfero::environment (on install_from == "git")

Create, if there isn't any default yet, a default Noosfero Environment <table> <tr> <th>Attribute</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>node[:noosfero][:environment]</tt></td> <td>A hash with the config. If nil, skip environment check and creation</td> <td> <tt>nil</tt> </td> </tr> <tr> <td><tt>node[:noosfero][:environment][:name]</tt></td> <td>The name of the environment. This is used in all pages' &lttitle&gt</td> <td> <tt>-</tt> </td> </tr> <tr> <td><tt>node[:noosfero][:environment][:domain]</tt></td> <td>The name of the environment. This is used in all pages' &lttitle&gt</td> <td> <tt>-</tt> </td> </tr> </table>



Just include noosfero in your node's run_list, the below configuration is an example: ```json { "rvm": { "user_installs": [ { "user": "noosfero", "rubies": [ "ree" ], "default_ruby": "ree", "gems": { "ree@noosfero": [] } } ] },

"postgresql": { "version": "9.3", "password": { // needed for chef-solo "postgres": "iqHDDo1o" }, },

"memcached": { "memory": 128, "listen": "" },

"varnish": { "version": "2.1", "listen_address": "", "listen_port": 80, "storage": "file", "storage_size": "1G", "vcl_cookbook": "noosfero" },

"nginx": { "listen_ports": [81], "keepalive_timeout": 20, "default_site_enabled": false },

"apache": { "version": "2.4", "listen_addresses": [""], "listen_ports": [82], "keepalivetimeout": 20, "keepaliverequests": 1000 },

"noosfero": { "service_name": "noosfero", "path": "/home/braulio/", "user": "braulio", "group": "braulio",

"git_url": "",
"git_revision": "master",

"dependencies_with": "bundler",
"rvm_load": "ree@noosfero",

"server_name": "",
"custom_domains": [

"server": {
  "proxy": "nginx",
  "backend": "unicorn",
  "workers": 1
"cache": {
  "server": "varnish"

"db": {
  "name": "",
  "port": 5433

"environment": {
  "name": "ESCAMBO",
  "domain": ""
"plugins": ["cms_learning", "currency", "escambo", "evaluation", "exchange", "sniffer", "solr"],

"settings": {
  "exception_recipients": ["", ""]

"plugin_settings": {
  "solr": {
    "port": 8983,
    "memory": 128


} "run_list": [ "recipe[noosfero]" ] } ```


  • Support others besides RVM (rbenv), by replacing rvm_shell with a generic noosfero_shell


  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github

After 3 consistent patches you become a commiter :)

Dependent cookbooks

java >= 0.0.0
rvm >= 0.0.0
memcached >= 0.0.0
varnish >= 0.0.0
postgresql >= 0.0.0
database >= 0.0.0
apache2 >= 0.0.0
nginx >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

No quality metric results found