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

ut_base (12) Versions 1.0.6

Unicorn Tears Base Cookbook

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

<a name="title"></a> Unicorn Tears Base Chef Cookbook

Build Status

<a name="description"></a> Description

Chef cookbook for a Unicorn Tears baseline node.

This is a wrapper (or application) cookbook and is therefore good and
opinionated about application and configuration defaults. Feel free to try it,
fork and modify it, or just read and learn.

<a name="usage"></a> Usage

Simply include recipe[ut_base] in your run_list.

<a name="requirements"></a> Requirements

<a name="requirements-chef"></a> Chef

Tested on 11.6.0 but newer and older version should work just fine.
File an issue if this isn't the case.

<a name="requirements-platform"></a> Platform

The following platforms have been tested with this cookbook, meaning that the
recipes run on these platforms without error:

  • ubuntu
  • debian
  • mac_os_x

Please report any additional platforms so they can be added.

<a name="requirements-cookbooks"></a> Cookbooks

This cookbook depends on the following external cookbooks:

<a name="installation"></a> Installation

Depending on the situation and use case there are several ways to install
this cookbook. All the methods listed below assume a tagged version release
is the target, but omit the tags to get the head of development. A valid
Chef repository structure like the Opscode repo is also assumed.

<a name="installation-site"></a> From the Opscode Community Site

To install this cookbook from the Community Site, use the knife command:

knife cookbook site install ut_base

<a name="installation-berkshelf"></a> Using Berkshelf

Berkshelf is a cookbook dependency manager and development
workflow assistant. To install Berkshelf:

cd chef-repo
gem install berkshelf
berks init

To use the Community Site version:

echo "cookbook 'ut_base'" >> Berksfile
berks install

Or to reference the Git version:

repo="ut-cookbooks/ut_base"
latest_release=$(curl -s https://api.github.com/repos/$repo/git/refs/tags \
| ruby -rjson -e '
  j = JSON.parse(STDIN.read);
  puts j.map { |t| t["ref"].split("/").last }.sort.last
')
cat >> Berksfile < 'git://github.com/$repo.git', :branch => '$latest_release'
END_OF_BERKSFILE
berks install

<a name="installation-librarian"></a> Using Librarian-Chef

Librarian-Chef is a bundler for your Chef cookbooks.
To install Librarian-Chef:

cd chef-repo
gem install librarian
librarian-chef init

To use the Community Site version:

echo "cookbook 'ut_base'" >> Cheffile
librarian-chef install

Or to reference the Git version:

repo="ut-cookbooks/ut_base"
latest_release=$(curl -s https://api.github.com/repos/$repo/git/refs/tags \
| ruby -rjson -e '
  j = JSON.parse(STDIN.read);
  puts j.map { |t| t["ref"].split("/").last }.sort.last
')
cat >> Cheffile < 'git://github.com/$repo.git', :ref => '$latest_release'
END_OF_CHEFFILE
librarian-chef install

<a name="recipes"></a> Recipes

<a name="recipes-default"></a> default

Main recipe which includes all internal recipes.

<a name="attributes"></a> Attributes

There are no attributes.

<a name="lwrps"></a> Resources and Providers

There are no resources and providers.

<a name="development"></a> Development

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

<a name="license"></a> License and Author

Author:: Fletcher Nichol (fnichol@nichol.ca) endorse

Copyright 2013, Fletcher Nichol

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

No quality metric results found