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


bsdznc (1) Versions 0.0.1

FreeBSD ZNC server.

cookbook 'bsdznc', '~> 0.0.1', :supermarket
cookbook 'bsdznc', '~> 0.0.1'
knife supermarket install bsdznc
knife supermarket download bsdznc
Quality 33%


Cookbook Version
[Apache 2.0 License](./LICENSE.txt)
Dependency Status
Build Status
Coverage Status


FreeBSD ZNC server.


Include either the bsdznc::default recipe,
or use the LWRP directly, e.g.,

bsdznc 'default' do
  action :create

# Now make sure the SSL certificate exists, then start ZNC.

bsdznc 'default' do
  action :start

You must provide a valid SSL certificate.
If you use the default recipe, this is handled by the certificate cookbook.
You must have an encrypted data bag under certificates with id znc.
See the certificate cookbook docs for how to create this.

Access the web admin at
The ZNC server will listen for IRC connections on port 194.

A minimal znc.conf will be created
with user admin and password password.
This should be changed immediately.

The znc.conf file is only created if it does not exist:
it will not be touched otherwise.
You should backup this file regularly as it contains
all server and user settings configured through the web admin.



  • Freebsd (~> 10.1)


  • certificate (~> 1.0.0)
  • sysctl (~> 0.6.2)


Attribute Description Default Choices
node['bsdznc']['user'] User to run znc as. "znc"
node['bsdznc']['group'] Group to run znc as. "znc"
node['bsdznc']['uid'] User id for the znc user. 194
node['bsdznc']['gid'] Group id for the znc group. 194
node['bsdznc']['version'] ZNC version to use for the default config. "1.6.0"
node['bsdznc']['config_path'] Path to the ZNC configuration directory. "/usr/local/etc/znc"
node['bsdznc']['cert_file'] SSL certificate filename. "znc.pem"
node['bsdznc']['irc_port'] Port to listen on for IRC connections. 194
node['bsdznc']['web_port'] Port to listen on for https connections. 443
node['bsdznc']['uri_prefix'] Prefix to serve the web admin under. "/"


  • bsdznc::default - Install, configure, and start the ZNC server.




  • create: create the znc server. Default action.
  • destroy: stop and destroy the znc server.
  • nothing: do nothing.
  • restart: restart the znc server.
  • start: start the znc server.
  • stop: stop the znc server.

Development and Testing

Source Code

The bsdznc source
is hosted on GitHub.
To clone the project run

$ git clone


Run rake -T to see all Rake tasks.

rake all                          # Run all tasks
rake doc                          # Build documentation
rake foodcritic                   # Lint Chef cookbooks
rake kitchen:all                  # Run all test instances
rake kitchen:default-freebsd-101  # Run default-freebsd-101 test instance
rake kitchen:znc-freebsd-101      # Run znc-freebsd-101 test instance
rake readme                       # Generate from
rake rubocop                      # Run RuboCop
rake rubocop:auto_correct         # Auto-correct RuboCop offenses
rake spec                         # Run RSpec code examples
rake test                         # Run kitchen integration tests
rake yard                         # Generate YARD Documentation


Run thor -T to see all Thor tasks.


Guard tasks have been separated into the following groups:

  • doc
  • lint
  • unit
  • integration

By default, Guard will generate documentation, lint, and run unit tests.
The integration group must be selected manually with guard -g integration.


Please submit and comment on bug reports and feature requests.

To submit a patch:

  1. Fork it (
  2. Create your feature branch (git checkout -b my-new-feature).
  3. Make changes. Write and run tests.
  4. Commit your changes (git commit -am 'Add some feature').
  5. Push to the branch (git push origin my-new-feature).
  6. Create a new Pull Request.


Copyright 2015 Evan Sosenko

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

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.


This software is provided "as is" and without any express or
implied warranties, including, without limitation, the implied
warranties of merchantibility and fitness for a particular

Dependent cookbooks

certificate ~> 1.0.0
sysctl ~> 0.6.2

Contingent cookbooks

There are no cookbooks that are contingent upon this one.



Initial release.

Collaborator Number Metric

0.0.1 failed this metric

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

Contributing File Metric

0.0.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

0.0.1 failed this metric

FC066: Ensure chef_version is set in metadata: bsdznc/metadata.rb:1
FC069: Ensure standardized license defined in metadata: bsdznc/metadata.rb:1
FC072: Metadata should not contain "attribute" keyword: bsdznc/metadata.rb:1
FC121: Cookbook depends on cookbook made obsolete by Chef 14: bsdznc/metadata.rb:1
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric

0.0.1 passed this metric

Testing File Metric

0.0.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

0.0.1 passed this metric