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

bricks (5) Versions 0.1.4

Installs/Configures Bricks application

Berkshelf/Librarian
Policyfile
Knife
cookbook 'bricks', '= 0.1.4'
cookbook 'bricks', '= 0.1.4', :supermarket
knife cookbook site install bricks
knife cookbook site download bricks
README
Dependencies
Changelog
Quality

OWASP Bricks Cookbook

Deploy a bricks environment. Build Status

Requirements

Platform

  • Ubuntu 10.04
  • Ubuntu 12.04

Cookbooks

Supported versions - codename

  • 1.9 - Barak
  • 1.8 - Atrai
  • 1.7 - Phalgu
  • 1.6 - Raidak
  • 1.5 - Lachen
  • 1.4 - Punpun
  • 1.3 - Torsa
  • 1.2 - Feni
  • 1.1 - Betwa
  • 1.0 - Narmada

Attributes

bricks::default

  • ['bricks']['db']['name'] - Bricks database name
  • ['bricks']['db']['username'] - Bricks username
  • ['bricks']['db']['password'] - Bricks user password
  • ['bricks']['codename'] - Bricks codename to deploy
  • ['bricks']['path'] - Path where application will be deployed
  • ['bricks']['server_name'] - Apache2 server name
  • ['bricks']['server_aliases'] - Array of apache2 virtualhost aliases

Usage

bricks::default

Just include bricks in your node's run_list:

{
  "name":"my_node",
  "run_list": [
    "recipe[bricks]"
  ]
}

Running tests

  • First, install dependencies:
    bundle install

  • Install cookbook dependencies:
    berks install

  • Run strainer tests:
    bundle exec strainer test

Contributing

  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 Github

License and Authors

Authors: Sliim sliim@mailoo.org

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.

Dependent cookbooks

database >= 0.0.0
php >= 0.0.0
mysql >= 0.0.0
apache2 >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

CHANGELOG for Bricks

This file is used to list changes made in each version of bricks cookbook.

0.1.0:

  • Initial release of bricks

0.1.1:

  • Added Phalgu codename support.
  • Added a bit of readme.

0.1.2:

  • Added Atrai and Barak codename support.

0.1.3:

  • Integration testing with serverspec and test-kitchen

0.1.4:

  • Changed license for Apache 2.0

Foodcritic Metric
            

0.1.4 passed this metric