google_app_engine 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
- google_app_engine needs toaster to brown your bagel.
Attributes
TODO: List you cookbook attributes here.
e.g.
google_app_engine::default
Key | Type | Description | Default |
---|---|---|---|
['google_app_engine']['bacon'] | Boolean | whether to include bacon | true |
Usage
google_app_engine::default
TODO: Write usage instructions for each cookbook.
e.g.
Just include google_app_engine
in your node's run_list
:
{
"name":"my_node",
"run_list": [
"recipe[google_app_engine]"
]
}
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.
- Fork the repository on Github
- Create a named feature branch (like
add_component_x
) - Write you change
- Write tests for your change (if applicable)
- Run the tests, ensuring they all pass
- Submit a Pull Request using Github
License and Authors
Authors: TODO: List authors
Check the Markdown Syntax Guide for help with Markdown.
The Github Flavored Markdown page describes the differences between markdown on github and standard markdown.