Chef cookbook to install and configure Dovecot.

Xabier de Zuazo d08489f233 fixed to work in chef-10 10 years ago
attributes 6b469f1e97 fixes to make it work on centos: "none" when no protocols and ldap template fix 11 years ago
libraries d08489f233 fixed to work in chef-10 10 years ago
recipes d08489f233 fixed to work in chef-10 10 years ago
templates 2ff8f679ea compatibility with chef-10 improved 10 years ago
.gitignore 3decd8ea38 some cleaning 11 years ago
.kitchen.yml a38f2fd59c added test-kitchen files required for testing 11 years ago
Berksfile a38f2fd59c added test-kitchen files required for testing 11 years ago
CHANGELOG.md 12a23afc52 First commit: basic packages installation 11 years ago
Gemfile a38f2fd59c added test-kitchen files required for testing 11 years ago
README.md 12a23afc52 First commit: basic packages installation 11 years ago
Vagrantfile a38f2fd59c added test-kitchen files required for testing 11 years ago
metadata.rb 510549fadb metadata: added ubuntu, centos and debian support 11 years ago

README.md

dovecot Cookbook

TODO: Enter the cookbook description here.

e.g. This cookbook makes your favorite breakfast sandwhich.

Requirements

TODO: List your cookbook requirements. Be sure to include any requirements this cookbook has on platforms, libraries, other cookbooks, packages, operating systems, etc.

e.g.

packages

  • toaster - dovecot needs toaster to brown your bagel.

Attributes

TODO: List you cookbook attributes here.

e.g.

dovecot::default

Key Type Description Default
['dovecot']['bacon'] Boolean whether to include bacon true

Usage

dovecot::default

TODO: Write usage instructions for each cookbook.

e.g. Just include dovecot in your node's run_list:

{
  "name":"my_node",
  "run_list": [
    "recipe[dovecot]"
  ]
}

Contributing

TODO: (optional) If this is a public cookbook, detail the process for contributing. If this is a private cookbook, remove this section.

e.g.

  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  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 using Github

License and Authors

Authors: TODO: List authors