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


reprepro (18) Versions 1.1.0

Installs/Configures reprepro for an apt repository

cookbook 'reprepro', '= 1.1.0', :supermarket
cookbook 'reprepro', '= 1.1.0'
knife supermarket install reprepro
knife supermarket download reprepro
Quality 50%

reprepro Cookbook

Cookbook Version
Build Status

Sets up an APT repository suitable for using the reprepro tool to manage distributions and components.

See the reprepro documentation for more information about reprepro itself, including the man(1) page in the package

Help Wanted

This repository has been archived for now, but if you want to help us with this cookbook drop by our slack channel #sous-chef on the chef community slack and let us know!


This cookbook is maintained by the Sous Chefs. The Sous Chefs are a community of Chef cookbook maintainers working together to maintain important cookbooks. If you’d like to know more please visit or come chat with us on the Chef Community Slack in #sous-chefs.



  • Debian/Ubuntu


  • Chef 13+


  • build-essential
  • nginx
  • apache2
  • gpg

You'll need to generate the PGP key separately and provide the data in the databag.


Attributes in this cookbook are set via the default recipe with data from the data bag. The following attributes are used, in the reprepro namespace.

  • fqdn - the fqdn that would go in sources.list
  • description - a description of the repository
  • pgp_email - the email address of the pgp key
  • pgp_fingerprint - the finger print of the pgp key

Data Bag based repository

Create a data bag to store the repository information. It should be named reprepro. The recipe uses the main data bag item.

  "id": "main",
  "fqdn": "",
  "repo_dir": "/srv/apt",
  "incoming": "/srv/apt_incoming",
  "description": "APT Repository for our packages.",
  "codenames": [
    "lucid", "hardy", "sid", "squeeze", "lenny"
  "allow": [
    "unstable>sid", "stable>squeeze"
  "pgp": {
    "email": "",
    "fingerprint": "PGP Fingerprint for the key",
    "public": "-----BEGIN PGP PUBLIC KEY BLOCK-----\n-----END PGP PUBLIC KEY BLOCK-----\n",
    "private": "-----BEGIN PGP PRIVATE KEY BLOCK-----\n-----END PGP PRIVATE KEY BLOCK-----\n"
  "pulls": {
    "name": "sid",
    "from": "sid",
    "component": "main"
  "architectures": [
  • fqdn: the fully qualified domain name of the apt server, used in
  • in the Apache vhost template and as the Origin in the distributions
  • configuration. Also saved to the node as
  • node['reprepro']['fqdn].
  • repo_dir: directory on disk where reprepro will serve the packages
  • incoming: the incoming directory, used in the incoming
  • configuration.
  • description: description about the repository, also saved to the
  • node as node['reprepro']['description'].
  • codenames: array of codenames to set up for the repository, used
  • with allow for the Allow directive in the incoming configuration
  • allow: [optional] array of additional codenames to use in the incoming
  • configuration
  • pgp: hash of options for the pgp setup. the
  • pgp['email']: email address of the signing key
  • pgp['fingerprint]: fingerprint of the PGP key
  • pgp['public]: the public PGP key, should be a single line
  • (replace line endings with \n)
  • pgp['private]: the private PGP key, should be a single line
  • (replace line endings with \n)
  • pulls: hash used in the pulls configuration.
  • architectures: array of architectures to create in distributions configuration

Attribute based configuration

Configuration of the repository can also be driven via attributes. The same keys available for the data bag are available via node attributes with the exception of the pgp hash. Using attribute based configuration will have a PGP key pair auto generated on the node when it is built.


This project exists thanks to all the people who contribute.


Thank you to all our backers!


Support this project by becoming a sponsor. Your logo will show up here with a link to your website.

reprepro Cookbook CHANGELOG

This file is used to list changes made in each version of the reprepro cookbook.

v1.1.0 (2019-08-08)

  • Migrate to circleci 2 orb
  • Fix for setting apache listen attribute

v1.0.0 (2018-05-08)

  • Remove compat_resource usage and require Chef 13+ instead
  • Use build_essential resource not the recipe to allow this to run without the cookbook on chef 14+
  • Convert the resource from a LWRP to a custom new_resource
  • Switch from chef_nginx to nginx cookbook and update the nginx_site usage for the new nginx_site custom resource
  • Use the correct action for ruby_block to resolve foodcritic warnings
  • Don't manually update the convert status on the resource. Let Chef do this the right way
  • Properly set the name_property on the resource
  • Property set the distribution default value in the resource
  • Switch from symbols to strings in the templates to resolve warnings

v0.5.0 (2017-05-31)

  • Turned on use_inline_resource in the provider
  • Switched from nginx to chef_nginx
  • Set reasonable minimum versions of the required cookbooks
  • Increased the required chef release to 12.1+
  • Added source_url, issues_url, and chef_version to the metadata
  • Removed "suggests" metadata as this doesn't actually do anything
  • Updated notification to the Chef 10+ syntax
  • Added a test cookbook that includes both apache and nginx testing
  • Swapped apt cookbook for compat_resource on older chef releases
  • Stopped including the default apt cookbook within the recipe. Getting apt-update run is outside the scope of this cookbook. It should be done in a base recipe with the apt_update resource
  • Fixed the apache listen attribute to use the current attribute name
  • Stopped using node.set, which is deprecated
  • Removed test gems from the Gemfile
  • Added a Delivery local mode config for simple testing
  • Setup Travis CI to use ChefDK and kitchen-dokken for integration testing
  • Switched from rubocop to cookstyle
  • Switched from kitchen-docker to kitchen-dokken

v0.4.2 (2015-11-20)

  • Remove Opscode/Chef as the maintainer.
  • Updated Travis to run full integration tests with kitchen-docker
  • Added Chef default .rubocop.yml file and resolved all warnings
  • Reformatted readme and set the minimum required Chef release to 11.0
  • Added basic Chefspec to test the converge
  • Add chefignore to limit files uploaded to the Chef server
  • Updated Berksfile format and removed yum, which wasn't actually required
  • Removed the Chef contributing doc that isn't valid anymore
  • Updated development deps in the Gemfile
  • Update .gitignore to the chef default


  • Allow option to use nginx (thanks gilles)


  • COOK-3545 - Support multiple distribution releases


  • [COOK-2111] - Add LWRP for reprepro interactions. Allow attribute driven configuration


  • [COOK-922] - add allow to data bag
  • Update the readme with data bag info

Collaborator Number Metric

1.1.0 passed this metric

Contributing File Metric

1.1.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Foodcritic Metric

1.1.0 failed this metric

FC075: Cookbook uses to save partial node data to the chef-server mid-run: reprepro/recipes/default.rb:41
Run with Foodcritic Version 14.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric

1.1.0 passed this metric

Testing File Metric

1.1.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Version Tag Metric

1.1.0 passed this metric