Chef cookbook to install and configure Dovecot.

Xabier de Zuazo 3619ebdc4d put the config path name in attribute files to avoid confusion 11 years ago
attributes 3619ebdc4d put the config path name in attribute files to avoid confusion 11 years ago
libraries d40a1652d9 default attribute values fixed and support for hashes in listeners 11 years ago
recipes e3f5568dee some attributes/templates have been cleaned to be like de originals 11 years ago
templates e3f5568dee some attributes/templates have been cleaned to be like de originals 11 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 12a23afc52 First commit: basic packages installation 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