2014-08-15 08:34:57 -04:00
redis Cookbook
==============
2014-03-30 13:50:53 -04:00
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
2014-08-15 08:34:57 -04:00
- `toaster` - redis needs toaster to brown your bagel.
2014-03-30 13:50:53 -04:00
Attributes
----------
TODO: List you cookbook attributes here.
e.g.
2014-08-15 08:34:57 -04:00
#### redis::default
2014-03-30 13:50:53 -04:00
< table >
< tr >
< th > Key< / th >
< th > Type< / th >
< th > Description< / th >
< th > Default< / th >
< / tr >
< tr >
2014-08-15 08:34:57 -04:00
< td > < tt > ['redis']['bacon']< / tt > < / td >
2014-03-30 13:50:53 -04:00
< td > Boolean< / td >
< td > whether to include bacon< / td >
< td > < tt > true< / tt > < / td >
< / tr >
< / table >
Usage
-----
2014-08-15 08:34:57 -04:00
#### redis::default
2014-03-30 13:50:53 -04:00
TODO: Write usage instructions for each cookbook.
e.g.
2014-08-15 08:34:57 -04:00
Just include `redis` in your node's `run_list` :
2014-03-30 13:50:53 -04:00
```json
{
"name":"my_node",
"run_list": [
2014-08-15 08:34:57 -04:00
"recipe[redis]"
2014-03-30 13:50:53 -04:00
]
}
```
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