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


depot (6) Versions 0.3.0

Installs/Configures Habitat Depot

cookbook 'depot', '= 0.3.0', :supermarket
cookbook 'depot', '= 0.3.0'
knife supermarket install depot
knife supermarket download depot
Quality 33%

Habitat Depot

This cookbook will set up a private Habitat Depot, running all the required services on one machine.

While this is tested and may work for other users, private depots are not yet supported by Chef Software, Inc. nor the Habitat project. Use at your own risk, and be aware that there is no planned migration strategy.


Platform Support

  • Ubuntu 16.04


Place a dependency on the depot cookbook in your cookbook's metadata.rb.

depends 'depot', '~> 0.2.0'

Then, in a recipe:

include_recipe 'depot'

A service will be created as hab-depot.


name default description
node['depot']['oauth']['client_id'] nil Github Client ID for OAuth
node['depot']['oauth']['client_secret'] nil Github Client Secret for OAuth
node['depot']['fqdn'] node['fqdn'] or This will be set to the node['fqdn'] attribute, and fall back to the

If the client_id and client_secret are not set, users will not be able to sign in, create origins, or upload packages to the Depot. Create an OAuth application on Github first, and then use the values for these attributes.

Local Test

Run a local Depot for testing with test kitchen.

$ kitchen converge

A VM will start up on, and will be accessible at from the host machine.

Once this is provisioned, it can be used for local testing. In order to upload packages, a Github OAuth application and personal access token must be created and the kitchen VM re-configured.

  1. Create a new OAuth application on Github. Name it kitchen-habitat-depot or similar. The homepage URL should be The Authorization Callback URL must be Save the client ID and client secret to a shell script file that looks like this: export GITHUB_CLIENT_ID=1edd05b4912af4eed6e16b9a export GITHUB_CLIENT_SECRET=4fdedc08a0a0d9c035a321edd05b4912af4eed6e16b9a Source this file in the shell and rerun kitchen converge. $ . ~/.github/kitchen-habitat-depot-oauth $ kitchen converge
  2. Create a personal access token on Github. Name it kitchen-habitat-depot or similar. Give it permission to user and user:email. Save the token to a file, for example ~/.github/kitchen-habitat-depot
  3. Open the local Depot at
  4. Sign-in using Github on the sign-in page.
  5. Create a new origin in the UI.
  6. Create a new origin key on the local system and upload it to the Depot. $ hab origin key generate kitchen-tester $ hab origin key upload --url kitchen-tester -z $(cat ~/.github/kitchen-habitat-depot)
  7. Create packages using that origin, and then upload them to the depot! $ hab pkg upload --url somepackage.hart -z $(cat ~/.github/kitchen-habitat-depot)

Dependent cookbooks

habitat ~> 0.3.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric

0.3.0 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Foodcritic Metric

0.3.0 failed this metric

FC033: Missing template: depot/recipes/default.rb:53
FC033: Missing template: depot/recipes/default.rb:68
Run with Foodcritic Version 8.2.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric

0.3.0 passed this metric