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

RSS

redis2 (13) Versions 0.5.1

Installs/Configures redis

Berkshelf/Librarian
Policyfile
Knife
cookbook 'redis2', '~> 0.5.1'
cookbook 'redis2', '~> 0.5.1', :supermarket
knife cookbook site install redis2
knife cookbook site download redis2
README
Dependencies
Quality 56%

Description

This cookbooks installs Redis 2 key-value datastore server. Redis can be installed from packages (where available) or source.

Requirements

For compiling from source: build-essential, ark

Attributes

  • Set node.default["redis2"]["install_from"] = "package" to install from distro packages, any other value to install from source.
  • node["redis2"]["instances"]["default"] - default attributes for all redis instances, will be merged with per instance attributes
  • node["redis2"]["instances"][_instance_name_] per instance configuration attributes tree

If compiling from source using the redis2::source recipe, note the following attributes:

  • node["redis2"]["source"]["url"] = Source tarball URL
  • node["redis2"]["source"]["checksum"] = sha256 checksum of the source tarball
  • node["redis2"]["source"]["version"] = Redis version

Usage

This cookbook implements redis instances as a definition. If you plan to run only one instance, use the <tt>redis::default_instance</tt> recipe which call a "redis_default" <tt>redis_instance</tt>. To spawn instances of redis, use the +redis_instance+ definition, usage is pretty straight forward:

redis_instance "datastore" do
  port 8866
  data_dir "/mnt/redis/datastore"
  master master_node
  nofile 16384
end

nofile, port, <em>data_dir</em> and master are the only attributes directly configurable using the definition syntax. Other attributes can be configured using the normal attribute interface under the node["redis2"]["instances"][instance_name] scope. Missing attributes will be merged from node["redis2"]["instances"]["default"]

The master attribute will set up redis as a slave of a the same redis instance on another server. It will not set node["redis2"]["instances"][instance_name]["replication"]["role"] (which can be slave or master), because redis can be both at the same time (e.g. chained masters).

Recipes

  • redis2::auto - automagically call redis_instance for every instance defined in the node["redis2"]["instances"] tree.
  • redis2::default_instance - use this if you want a simple recipe with a single redis instance called "redis_prime" It's generally not a good idea to use the redis2::default_instance recipe. If you want a single redis instance, either use redis_instance definition or redis2::auto and define your instance in the attributes tree.

Collaborator Number Metric
            

0.5.1 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

0.5.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.5.1 failed this metric

FC039: Node method cannot be accessed with key: redis2/definitions/instance.rb:14
FC039: Node method cannot be accessed with key: redis2/definitions/instance.rb:15
FC039: Node method cannot be accessed with key: redis2/definitions/instance.rb:17
FC039: Node method cannot be accessed with key: redis2/definitions/instance.rb:27
FC039: Node method cannot be accessed with key: redis2/definitions/instance.rb:35
FC039: Node method cannot be accessed with key: redis2/definitions/instance.rb:40
FC039: Node method cannot be accessed with key: redis2/definitions/instance.rb:41
FC039: Node method cannot be accessed with key: redis2/definitions/instance.rb:46
FC039: Node method cannot be accessed with key: redis2/definitions/instance.rb:52
FC039: Node method cannot be accessed with key: redis2/definitions/instance.rb:54
FC064: Ensure issues_url is set in metadata: redis2/metadata.rb:1
FC065: Ensure source_url is set in metadata: redis2/metadata.rb:1
FC066: Ensure chef_version is set in metadata: redis2/metadata.rb:1
FC069: Ensure standardized license defined in metadata: redis2/metadata.rb:1
FC072: Metadata should not contain "attribute" keyword: redis2/metadata.rb:1
Run with Foodcritic Version 12.0.1 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

0.5.1 passed this metric

No Binaries Metric
            

0.5.1 passed this metric

Publish Metric
            

0.5.1 passed this metric

Supported Platforms Metric
            

0.5.1 passed this metric

Testing File Metric
            

0.5.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.5.1 passed this metric