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

Select Status

The application_buildpack cookbook has been deprecated

Author provided reason for deprecation:

The application_buildpack cookbook has been deprecated and is no longer being maintained by its authors. Use of the application_buildpack cookbook is no longer recommended.

You may find that the application cookbook is a suitable alternative.


application_buildpack (7) Versions 0.0.1

deploys and configures apps using heroku buildpacks

cookbook 'application_buildpack', '= 0.0.1', :supermarket
cookbook 'application_buildpack', '= 0.0.1'
knife supermarket install application_buildpack
knife supermarket download application_buildpack
Quality -%



This cookbook is designed to be able to deploy applications using heroku buildpacks.

The following buildpacks are tested and supported:

  • ruby
  • nodejs

Note that this cookbook is based on the application cookbook; you will find general documentation in that cookbook.


Chef 11.0.0 or higher required (for Chef environment use).

The following Opscode cookbooks are dependencies:


The LWRP provided by this cookbook is not meant to be used by itself; make sure you are familiar with the application cookbook before proceeding.


The compile sub-resource LWRP deals with compiling an app using a buildpack.

Attribute Parameters

  • buildpack: The buildpack to be used. Will be used to install dependencies and set the buildpack repository. Default: nil. Options: :ruby, :nodejs
  • buildpack_repository: A custom buildpack repository that should be used instead. Default: nil.
  • buildpack_revision: The revision of the buildpack to be used. Default: master.
  • buildpack_environmet: Additional ENV variables to be passed to the buidlpack compile script. Default: {}.


The scale sub-resource LWRP deals with configuring monit to start processes described in your Procfile.

Attribute Parameters

You can pass any attribute combination to scale the name of the attribute will be matched to a process describe in your Procfile.

scale do
  # scale with one process
  web 1

  # scale with multiple processes
  # PROCESS_NUM env variable will indicate the processes id
  worker 4

  # send a custom signal on reload to gracefully stop the process
  guard 1, reload: 'USR1'


A sample recipe that deploy a Ruby app:

application 'example' do
  path '/srv/example'

  owner 'ubuntu'
  group 'ubuntu'

  packages ['git']
  repository ''

  environment 'PORT' => 8000

  compile do
    buildpack :ruby

  scale do
    web 1

A sample recipe that deploys an scala app using a custom buildpack

application 'example' do
  path '/srv/example'

  owner 'ubuntu'
  group 'ubuntu'

  packages ['git']
  repository ''

  compile do
    buildpack_repository ''

  scale do
    web 1


  • If the buildpack fails to compile because some packages are missing, just define the packages in your application LWRP: packages ['lib-imagemagick'].
  • If the buildpack fails to compile due to a missing /app directory then the buidlpack uses hardcoded heroku paths. Create an issue on the repository or fork it.


Thanks to:

Dependent cookbooks

monit >= 0.0.0
application ~> 4.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

No quality metric results found