https://github.com/cloverinteractive/rails_env
https://github.com/cloverinteractive/rails_env
Last synced: 4 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/cloverinteractive/rails_env
- Owner: cloverinteractive
- Created: 2013-04-16T08:04:00.000Z (about 12 years ago)
- Default Branch: master
- Last Pushed: 2013-04-16T09:46:56.000Z (about 12 years ago)
- Last Synced: 2025-01-19T17:49:55.807Z (5 months ago)
- Language: Ruby
- Size: 105 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
rails_env 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` - rails_env needs toaster to brown your bagel.Attributes
----------
TODO: List you cookbook attributes here.e.g.
#### rails_env::default
Key
Type
Description
Default
['rails_env']['bacon']
Boolean
whether to include bacon
true
Usage
-----
#### rails_env::default
TODO: Write usage instructions for each cookbook.e.g.
Just include `rails_env` in your node's `run_list`:```json
{
"name":"my_node",
"run_list": [
"recipe[rails_env]"
]
}
```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 GithubLicense and Authors
-------------------
Authors: TODO: List authors