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

RSS

letsencrypt-boulder-server (3) Versions 0.1.2

Installs/Configures Boulder, the ACME-based CA server by Let's Encrypt.

Policyfile
Berkshelf
Knife
cookbook 'letsencrypt-boulder-server', '~> 0.1.2', :supermarket
cookbook 'letsencrypt-boulder-server', '~> 0.1.2'
knife supermarket install letsencrypt-boulder-server
knife supermarket download letsencrypt-boulder-server
README
Dependencies
Changelog
Quality 17%

Let's Encrypt: Boulder cookbook

This is a cookbook for provisioning Boulder, an
ACME-based certificate authority, written in Go. The
Boulder application is an official effort of Let's Encrypt
project
.

Warning: This cookbook was created for testing other cookbooks, not
production purposes.

Supported Platforms

  • Ubuntu 14.04
  • Centos 7

Attributes

Key Type Description
['boulder']['config']['boulder-config'] Hash Deep-merged into eponymous config file.
['boulder']['config']['issuer-ocsp-responder'] Hash Deep-merged into eponymous config file.

Recipes

default

Install and starts the Boulder server.

Notes

  • Pay close attention to the output of any failed attempts. By default,
    Boulder tries to use all ports in the range 8000 to 8010, among
    others. If there is a conflict with other applications, you can use this
    cookbook's attributes to force Boulder onto a different port.

  • If you're running the boulder server during testing, and it's on the
    same server as the webserver, you'll likely want to edit the
    hostsfile. The hostfile cookbook is great for this.

Development

To tag and publish a new version of this cookbook, first ensure:

  • the metadata.rb version has been bumped appropriately,
  • the CHANGELOG.md has been updated, and
  • all changes have been committed to git.

Once that has been done:

bundle exec rake publish

This will create a git tag and push a new release to the Supermarket.

License and Authors

Sponsors

Code contributions have been generously made by the following
organizations:

Dependent cookbooks

golang >= 0.0.0
rabbitmq >= 0.0.0
mariadb >= 0.0.0
build-essential >= 0.0.0
yum >= 0.0.0
hostsfile >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

0.1.2

  • Added more specific platform version specification.
  • Get boulder git revision from attribute

0.1.1

  • Added metadata for Supermarket.

0.1.0

Collaborator Number Metric
            

0.1.2 failed this metric

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

Contributing File Metric
            

0.1.2 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 https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.1.2 failed this metric

FC066: Ensure chef_version is set in metadata: letsencrypt-boulder-server/metadata.rb:1
FC121: Cookbook depends on cookbook made obsolete by Chef 14: letsencrypt-boulder-server/metadata.rb:1
FC122: Use the build_essential resource instead of the recipe: letsencrypt-boulder-server/recipes/default.rb:38
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric
            

0.1.2 passed this metric

Testing File Metric
            

0.1.2 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 https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.1.2 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 https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number