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

chef-server-with-letsencrypt (2) Versions 4.0.0

Installs/Configures chef-server-with-letsencrypt

Policyfile
Berkshelf
Knife
cookbook 'chef-server-with-letsencrypt', '~> 4.0.0', :supermarket
cookbook 'chef-server-with-letsencrypt', '~> 4.0.0'
knife supermarket install chef-server-with-letsencrypt
knife supermarket download chef-server-with-letsencrypt
README
Dependencies
Quality 17%

Cookbook: Chef Server with Let's Encrypt

A simple wrapper cookbook that sets up Chef Server with a trusted SSL/TLS certificate from Let's Encrypt.
Uses chef-server cookbook and [Lego library](lego).

Usage

Validation

You must override lego_email attribute to obtain a certificate.

default['chef-server-with-letsencrypt']['lego_email'] = 'you@example.com'

Validation by DNS

By default, HTTP method is used to validate domain lego --http :80).

Override default attributes to use DNS method.
Consult lego dnshelp for required environment variables.

Example:

default['chef-server-with-letsencrypt']['lego_params'] = '--dns dnsimple'
default['chef-server-with-letsencrypt']['lego_env'] = {'DNSIMPLE_EMAIL' => '...', 'DNSIMPLE_OAUTH_TOKEN' => '...'}

Other attributes

Look up attributes/default.rb for available overrides
and kitchen.yml for ideas how to use them in practice.

Development

Bundler

We use chef gem from Rubygems. We don't use Chef DK.
Always call all Chef utilities (e.g. chef, knife, berks, kitchen or whatever) via Bundler.
Example:

x knife node list

First setup

  1. alias x='bundle exec'
  2. curl -sSL https://get.rvm.io | bash -s stable
  3. gem install bundler

Daily routine

At the very minimum, before git commit and after git pull.

  1. bundle
  2. x berks

Testing

We use Test Kitchen to test cookbooks.
The basics:

  • x kitchen converge to provision the test machine with Chef
  • x kitchen verify to run tests on the machine
  • x kitchen login to manually inspect the machine

License and Authors

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

chef-server >= 0.0.0
cron >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

4.0.0 failed this metric

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

Contributing File Metric
            

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

Foodcritic Metric
            

4.0.0 failed this metric

FC067: Ensure at least one platform supported in metadata: chef-server-with-letsencrypt/metadata.rb:1
FC069: Ensure standardized license defined in metadata: chef-server-with-letsencrypt/metadata.rb:1
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric
            

4.0.0 passed this metric

Testing File Metric
            

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

Version Tag Metric
            

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