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

RSS

gitzone (1) Versions 1.0.6

Installs/Configures gitzone managed zone files for Bind

Berkshelf/Librarian
Policyfile
Knife
cookbook 'gitzone', '~> 1.0.6'
cookbook 'gitzone', '~> 1.0.6', :supermarket
knife cookbook site install gitzone
knife cookbook site download gitzone
README
Dependencies
Quality

gitzone cookbook

Chef cookbook for git-shell managed BIND zone files. The gitzone scripts are developed by the dyne.org.

NOTE: This cookbook is in DRAFT stage. Even the best practices are applied some conceptual failures may exist.

Pull requests & suggestions are welcome.

Supported Platforms

Tested on:

  • ubuntu 12.04
  • centos 6.4

Acknowledgement: * On centos 6.4 is small issue with git < 1.7. It's described here: https://github.com/dyne/gitzone/issues/1 * At the present time, there is the small inconvenience that zone files are not deployed, until manual push from cloned repository.

Attributes

<table> <tr> <th>Key</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>['gitzone']['preffix']</tt></td> <td>String</td> <td>gitzone install preffix</td> <td><tt>/usr</tt></td> </tr> <tr> <td><tt>['gitzone']['home']</tt></td> <td>String</td> <td>where to create gitzone home dir</td> <td><tt>/home</tt></td> </tr> <td><tt>['gitzone']['bind_repos_dir']</tt></td> <td>String</td> <td>Path where are bind configuration files reffering to gitzone repo are stored</td> <td><tt>/etc/bind/repo</tt></td> </tr> <tr> <td><tt>['gitzone']['user']</tt></td> <td>String</td> <td>gitzone system user to be created</td> <td><tt>gitzone</tt></td> </tr> <tr> <td><tt>['gitzone']['group']</tt></td> <td>String</td> <td>gitzone system group for gitzone user</td> <td><tt>g</tt></td> </tr> <tr> <td><tt>['gitzone']['user_ssh_pub_keys']</tt></td> <td>String</td> <td>ssh keys to be stored in authorized_keys (for remote access or dyn DNS feature)</td> <td><tt>nil</tt></td> </tr> <tr> <td><tt>['gitzone']['admin']</tt></td> <td>String</td> <td>system account where the repo clone is first created</td> <td><tt>nil, by default uses gitzone_user home dir</tt></td> </tr> <tr> <td><tt>['gitzone']['domains']</tt></td> <td>Array</td> <td>2nd level domain names to be created/searched</td> <td><tt></tt></td> </tr> <tr> <td><tt>['gitzone']['repo_url']</tt></td> <td>String</td> <td>where to clone gitzone code</td> <td><tt>https://github.com/dyne/gitzone.git"</tt></td> </tr> <tr> <td><tt>['gitzone']['repo_dir']</tt></td> <td>String</td> <td>where to clone gitzone source code</td> <td><tt>/srv/repos/git</tt></td> <tr> <tr> <td><tt>['gitzone']['repos']</tt></td> <td>String</td> <td>extends gitzone.conf $repos configuration</td> <td><tt></tt></td> </tr> </table>

Usage

gitzone::default

Include gitzone in your node's run_list:

{
  "run_list": [
    "recipe[gitzone::default]"
  ]
}

Managing zone files

su - bob
git clone gitzone@localhost:zones/gitzone gitzone-admin
cd gitzone-admin
#edit zone files
git checkout master
git commit -am "updates"
git pull --rebase origin master
git push origin master
git pull

Dynamic DNS feature

TBD: Not yet tested. See original gitzone repository for usage details.

Contributing

  1. Fork the repository on Github
  2. Create a named feature branch (i.e. add-new-recipe)
  3. Write you 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

Author:: Petr Michalec (epcim@apealive.net)

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

1.0.6 failed this metric

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

Contributing File Metric
            

1.0.6 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
            

1.0.6 failed this metric

FC039: Node method cannot be accessed with key: gitzone/recipes/configure_zones.rb:39
FC064: Ensure issues_url is set in metadata: gitzone/metadata.rb:1
FC065: Ensure source_url is set in metadata: gitzone/metadata.rb:1
FC066: Ensure chef_version is set in metadata: gitzone/metadata.rb:1
FC069: Ensure standardized license defined in metadata: gitzone/metadata.rb:1
FC072: Metadata should not contain "attribute" keyword: gitzone/metadata.rb:1
Run with Foodcritic Version 11.1.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

1.0.6 passed this metric

No Binaries Metric
            

1.0.6 passed this metric

Publish Metric
            

1.0.6 passed this metric

Supported Platforms Metric
            

1.0.6 passed this metric

Testing File Metric
            

1.0.6 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
            

1.0.6 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