New Supermarket Announcements!

The Chef Community Cookbooks Survey

We would love to know more about what you think about community cookbooks and are runnning a quick survey. This will help us understand the role they play in your use of Chef. As a community member, you are invited to participate. You have a unique understanding of the role community cookbooks have in your work, and we value your opinion. Most people take about 5 minutes to complete this survey. There are no right or wrong answers; we are interested in your opinions.
Chef Community Cookbooks Survey

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 supermarket mailing list or in Gitter.

Select Supported Platforms

RSS

pinto (11) Versions 0.1.10

Installs/Configures pinto

Berkshelf
Librarian
Knife
cookbook 'pinto', '~> 0.1.10'
cookbook 'pinto', '~> 0.1.10'
knife cookbook site install pinto
knife cookbook site download pinto
README
Dependencies

Synopsis

Installs, configures Pinto application

Recipes

  • pinto::application - installs Pinto application in standalone mode
  • pinto::server - installs Pinto server ( should be run after pinto::application recipe )

Attributes

May be overridden to alter recipes behaviour

  • node[:pinto][:user], node[:pinto][:group] - The owner and group of pinto application. The application will be installed into ~/opt/local/pinto directory
  • node[:pinto][:user_shell], shell for pinto application owner, default is '/bin/bash'
  • node[:pinto][:host] - pinto server bind host, default value is 0.0.0.0
  • node[:pinto][:port] - pinto server bind port, default value is 3111
  • node[:pinto][:workers] - number of pinto server workers, default value is 3

Tested on

  • CentOS-6.4-x86_64, , Chef 10.14.0
  • CentOS-6.3-x86_64-minimal, Chef 10.14.2
  • Debian-6.0.4-64-bit, Chef 11.4.4
  • Ubuntu 10.04.1 LTS, Chef 11.4.4

Current release

http://community.opscode.com/cookbooks/pinto

Contributing

I use berkshelf for developing / testing pinto cookbook. Berkshelf is a framework for testing / managing chef cookbooks. So if you are interested in contributing, hacking - berkshelf is the best way to go ahead. Next commands will explain how to start.

Install berkshelf

$ gem install berkshelf

Install vagrant

Vagrant is the tools for running / provisioning VirtualBox machines. Berkshelf and Vagrant are tightly integrated. Berskhelf requires latest version of vagrant. Visit the Vagrant downloads page - http://downloads.vagrantup.com/ and download the latest installer for your operating system.

Install vagrant-berkshelf plugin

Second thing we need is berkshelf vagrant plugin. Following command will install the plugin

$ vagrant plugin install vagrant-berkshelf 

Fork cookbooks

$ git clone https://github.com/melezhik/cookbooks.git

Run vagrant box

Following command will boot vagrant virtual machine, deploy pinto on it and run tests.

$ cd cookbooks/pinto
$ vagrant up

Make changes

Change code and revision your changes running tests again. For standard vagrant work-flow checkout - http://docs.vagrantup.com/v2/

$ mcedit recipes/application.rb
$ vagrant provision

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.