Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status

RSS

graphite (29) Versions 1.0.1

Installs/Configures graphite

Policyfile
Berkshelf
Knife
cookbook 'graphite', '= 1.0.1', :supermarket
cookbook 'graphite', '= 1.0.1'
knife supermarket install graphite
knife supermarket download graphite
README
Dependencies
Quality -%

Graphite Cookbook

Build Status
Code Climate
githalytics.com alpha

Description

Library cookbook for installation and configuration of Graphite
http://graphite.wikidot.com/ via Chef

Consult the Graphite documentation for more information:

Platforms

  • Ubuntu 10.04 / Ubuntu 12.04
  • Debian
  • RHEL and derivatives (Centos, Amazon Linux, Oracle Linux, Scientific Linux)
  • Fedora

Data Bags

TODO (sure, use em if you like, even encrypt them)

Usage

It's a library cookbook, intended to be used in your custom wrapper
cookbook to behave as needed. It's the building materials, not the
house.

For example usage consult the reference cookbook example

Feel free to ask us questions anytime on irc: #heavywater on freenode

Custom Resources

TODO (resource usage documentation coming)

Amazon Web Services

Due to the old version of Chef used on Amazon Web Services in order to
succesfully run this cookbook you will need to add the
delayed_evaluator
recipe to your run list before the graphite recipe.

Development / Contributing

  • Source hosted at [GitHub][repo]
  • Report issues/questions/feature requests on [GitHub Issues][issues]

Pull requests are very welcome! Make sure your patches are well tested.
Ideally create a topic branch for every separate change you make. For
example:

  1. Fork the repo
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Write some tests, see ChefSpec
  4. Commit your awesome changes (git commit -am 'Added some feature')
  5. Push to the branch (git push origin my-new-feature)
  6. Create new Pull Request against the develop branch

No quality metric results found