https://github.com/regadas/opsworks-docker
OpsWorks docker recipes
https://github.com/regadas/opsworks-docker
Last synced: about 1 year ago
JSON representation
OpsWorks docker recipes
- Host: GitHub
- URL: https://github.com/regadas/opsworks-docker
- Owner: regadas
- Created: 2015-03-26T15:45:25.000Z (about 11 years ago)
- Default Branch: master
- Last Pushed: 2015-03-26T17:35:25.000Z (about 11 years ago)
- Last Synced: 2025-01-29T08:24:11.637Z (over 1 year ago)
- Language: Ruby
- Homepage:
- Size: 113 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
Awesome Lists containing this project
README
docker Cookbook
===============
TODO: Enter the cookbook description here.
e.g.
This cookbook makes your favorite breakfast sandwich.
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` - docker needs toaster to brown your bagel.
Attributes
----------
TODO: List your cookbook attributes here.
e.g.
#### docker::default
Key
Type
Description
Default
['docker']['bacon']
Boolean
whether to include bacon
true
Usage
-----
#### docker::default
TODO: Write usage instructions for each cookbook.
e.g.
Just include `docker` in your node's `run_list`:
```json
{
"name":"my_node",
"run_list": [
"recipe[docker]"
]
}
```
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 your 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