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


tonicdns (3) Versions 1.0.2

Installs/Configures tonicdns

cookbook 'tonicdns', '= 1.0.2', :supermarket
cookbook 'tonicdns', '= 1.0.2'
knife supermarket install tonicdns
knife supermarket download tonicdns
Quality 100%

TonicDNS cookbook

Build Status

This cookbook is used to install TonicDNS - a RESTful API for PowerDNS.


You should have already installed PowerDNS and pdns-backend-mysql to use it without errors.

Depends on cookbooks:

  • apt
  • apache2
  • tar
  • database
  • chef-pdns (this one used for tests)

Supported Platforms

Tested and runs on:

  • Ubuntu 12.04
  • Ubuntu 14.04
  • CentOS 6.5
  • Debian 7.6
  • CentOS 7
  • Debian 6

Should also work with other RHEL and Debian based distos, but not tested yet.


node["TonicDNS"]["git_install"] - whenever to install TonicDNS from remote or local source. Default - true

node["TonicDNS"]["git_repo"] - download URL for TonicDNS. Default -

node["TonicDNS"]["package_name"] - name for local package located in files/default. Default - tonicdns-git.tar.gz

node["TonicDNS"]["install_dir"] - Docroot for apache2 where TonicDNS will be located. Default - /var/www/TonicDNS

node["poweradmin"]["http_port"] - port where TonicDNS API could be found. Default - 8080

node["tonicdns"]["user"] - User that will be created to serve API requests. Default - tonicdns

node["tonicdns"]["user_email"] - email for user created to serve API requests. Default -

Here is a block of mysql connection settings - it should be easy to understand what value stands for.

Should be the same, previously used to configure pdns-backend-mysql.

node["tonicdns"]["hostname"] = 'localhost'

node["tonicdns"]["username"] = 'powerdns'

node["tonicdns"]["password"] = 'p4ssw0rd'

node["tonicdns"]["dbname"] = 'powerdns'



Use recipe[tonicdns::default] to deploy TonicDNS API on your working copy of PowerDNS with mysql-backend.


Use recipe[tonicdns::test] to deploy TonicDNS API alongside with test deployment of PowerDNS+mysql-backend used in this chef-pdns test cookbook.

But it's not recomended to use it in such way. At least right now.


Your contributions is highly appreciated.
Here is standart instruction how to do so:

  1. Fork the repository on Github
  2. Create a named feature branch (i.e. add-new-recipe)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request

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

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.

Dependent cookbooks

apt >= 0.0.0
apache2 >= 0.0.0
tar >= 0.0.0
database >= 0.0.0
chef-pdns >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.


  • added support for centos7 and debian6


  • fixed converge error if deployed on top of poweradmin cookbook
  • fixed critical php5 dependency
  • fixed foodcritic FC002 warning
  • fixed apache port selection
  • added serverspec tests
  • added travis-ci integration


Initial release of tonicdns

Foodcritic Metric

1.0.2 passed this metric