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


ssl (9) Versions 1.1.1

Sets up SSL certs and keys from an encrypted data bag

cookbook 'ssl', '~> 1.1.1'
cookbook 'ssl', '~> 1.1.1', :supermarket
knife cookbook site install ssl
knife cookbook site download ssl
Quality 50%


A recipe for setting up system-wide SSL certs on Ubuntu / Debian systems.


Ubuntu or Debian Linux system and an encrypted data bag named "ssl".


node['ssl']['certs_dir'] = '/etc/ssl/certs'
node['ssl']['keys_dir']  = '/etc/ssl/keys'
node['ssl']['group']     = 'ssl-cert'
node['ssl']['domain']     = '*'


The certs and keys are retrieved from an encrypted data bag named "ssl". Inside the data bag, the cert should be in a key named "cert", the domain name should be in the "id" key, with periods replaced by underscores (i.e. -> foo_com), the cert's key should be in "key", and if you have a chain of certs to validate your domain's cert, put them in an array under "chain" and the recipe will set them up for you. If you have a local CA, you can store that in a key named "ca", and the recipe will install and symlink it in the certs_dir.

NOTE: The certs and keys should all be on one line, with their newlines replaced by "\n". They will be stored correctly once placed on the server.

Sample way to generate the data bag:

bundle exec knife solo data bag create ssl -d --data-bag-path data_bags -j '{"id":"caregeneral_com", "key":"private_key_of_caregeneral","cert":"certificate","chain":["cert", "cert"]}'

A sample data bag options data_bags\keys\domain_com.json:


After running the default recipe, your certs will be in /etc/ssl/certs/{}.crt, and the keys will be in /etc/ssl/private/{}.key. Any chain certs will be combined into /etc/ssl/certs/{}.chain.crt and the whole cert chain will be put into /etc/ssl/certs/{}.combined.crt. The separate chain cert is for Apache, and the combined one is for Nginx. A CA cert will be stored as /etc/ssl/certs/{}-ca.crt, however you can put the CA in a data bag of it's own if you'd prefer a different prefix than

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

lamp_role Applicable Versions

Collaborator Number Metric

1.1.1 failed this metric

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

Contributing File Metric

1.1.1 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.1 failed this metric

FC064: Ensure issues_url is set in metadata: ssl/metadata.rb:1
FC065: Ensure source_url is set in metadata: ssl/metadata.rb:1
FC066: Ensure chef_version is set in metadata: ssl/metadata.rb:1
FC069: Ensure standardized license defined in metadata: ssl/metadata.rb:1
Run with Foodcritic Version 13.1.1 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric

1.1.1 passed this metric

Publish Metric

1.1.1 passed this metric

Supported Platforms Metric

1.1.1 passed this metric

Testing File Metric

1.1.1 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.1 passed this metric