Chef cookbook to install and configure Dovecot.

Xabier de Zuazo 51955efcab improved namespace config support 11 éve
attributes 51955efcab improved namespace config support 11 éve
libraries 51955efcab improved namespace config support 11 éve
recipes d08489f233 fixed to work in chef-10 11 éve
templates 422f49f099 added two new config files: 10-tcpwrapper.conf and 15-mailboxes.conf 11 éve
test 1cbb7dadad some basic integration tests added and a kitchen.yml file 11 éve
.gitignore 1cbb7dadad some basic integration tests added and a kitchen.yml file 11 éve
.kitchen.yml 1cbb7dadad some basic integration tests added and a kitchen.yml file 11 éve
Berksfile a38f2fd59c added test-kitchen files required for testing 11 éve
CHANGELOG.md 12a23afc52 First commit: basic packages installation 11 éve
Gemfile 1cbb7dadad some basic integration tests added and a kitchen.yml file 11 éve
README.md 12a23afc52 First commit: basic packages installation 11 éve
Vagrantfile 1cbb7dadad some basic integration tests added and a kitchen.yml file 11 éve
metadata.rb 1cbb7dadad some basic integration tests added and a kitchen.yml file 11 éve

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