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


modman (2) Versions 2.2.1

installs/configures modman

cookbook 'modman', '= 2.2.1'
cookbook 'modman', '= 2.2.1', :supermarket
knife supermarket install modman
knife supermarket download modman
Quality 100%


GitHub tag Build Status Gittip

chef-modman installs modman and provides access to a corresponding LWRP.


This cookbook has no direct dependencies.


Installs modman and provides access to a corresponding LWRP.


The following platforms are supported and tested:

  • Debian 6.x
  • Debian 7.x
  • Ubuntu 14.04.x

Other Debian family distributions are assumed to work.


Simply include the recipe in your application recipe, where you setup/deploy magento. ruby include_recipe "modman"

ATTENTION: name this cookbook "modman" if you want to use the LWRP like this: ruby modman "MODULENAME" do path "/MAGENTO_ROOT" action :clone end

See Command-Reference for available commands. Keep an eye on the associated actions in the LWRP (providers/default.rb) since some commands had to be rewritten using no "-".

As a sidenote for vagrant users: - You may set up a bash function to use a pseudo-tty with magerun in the vagrant box.

e.g. in your local ~/.bash_profile place: bash modman () { vagrant ssh -- -t modman $@ }

Open a new bash prompt at your Vagrant project and interact with n98-magerun as if it were local. $ modman help $ modman deploy-all

Your commands will be run inside the Vagrant box.


  1. Fork the repository from GitHub.
  2. Clone your fork to your local machine:

    $ git clone
  3. Create a git branch

    $ git checkout -b my_bug_fix
  4. Write tests

  5. Make your changes/patches/fixes, committing appropriately

  6. Run the tests: rake style, rake spec, rake integration:vagrant

  7. Push your changes to GitHub

  8. Open a Pull Request


The following Rake tasks are provided for automated testing of the cookbook:

$ rake -T
rake spec                 # Run ChefSpec examples
rake style                # Run all style checks
rake style:chef           # Lint Chef cookbooks
rake style:ruby           # Run Ruby style checks
rake travis               # Run all tests on Travis

See for detailed information.

License and Author

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

CHANGELOG for modman

This file is used to list changes made in each version of modman.


  • update/integrate testsuites: test-kitchen, foodcritic, rubocop, travis-ci
  • prepare for release on


  • fix provider (missing modman call in all actions) thanks to Fantus


  • update/integrate testsuites: test-kitchen, foodcritic, rubocop, travis-ci


  • update/integrate testsuites: test-kitchen, foodcritic, rubocop, travis-ci
  • pin modman version (because newer versions break proper symlinking)


  • move installation of modman from LWRP to default recipe


  • Refactoring: removed @new_resource.exists statements and fixed missing force parameter.


  • Initial release of modman

Foodcritic Metric

2.2.1 passed this metric