Adoptable Cookbooks List

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.

simple_passenger Chef cookbook

Usage

Pretty straightforward, this cookbook only has one required attribute. Specify ['passenger']['git_repo'] pointing to your git repository (with the .git on the end) and call the default recipe to run your app with passenger standalone.

This cookbook depends on the build-essential cookbook, which generally requires that apt-get update is run. build-essential provides this note:

Note for Debian platform family: On Debian platform-family systems, it is recommended that apt-get update be run, to ensure that the package cache is updated. It's not in the scope of this cookbook to do that, as it can create a duplicate resource. We recommend using the apt cookbook to do this.

This cookbook also creates a Passengerfile.json using the attributes under
['passenger']['passengerfile']. Refer to the
Passengerfile.json reference
and the attributes directory for help with these attributes.

Testing

Chefspec unit tests and Test Kitchen integration tests are run on all pushes to GitHub by Travis CI.

Test Kitchen integration tests are on Travis CI use Docker via kitchen-docker. If you'd like to use Docker to run Test Kitchen integration tests locally:

# Ensure docker is running first
# On Mac OS X you may need to have sudo commands available with no password,
# the easiest way to do this is run a command as sudo so the next command won't prompt
# for a password
sudo ls
# Run Test Kitchen integration tests with docker (uses concurrency)
bundle exec rake integration:docker