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

modman (2) Versions 2.2.2

installs/configures modman

Berkshelf/Librarian
Policyfile
Knife
cookbook 'modman', '~> 2.2.2'
cookbook 'modman', '~> 2.2.2', :supermarket
knife cookbook site install modman
knife cookbook site download modman
README
Dependencies
Changelog
Quality 44%

<a href="http://www.ffuenf.de" title="ffuenf - code • design • e-commerce"><img src="https://github.com/ffuenf/Ffuenf_Common/blob/master/skin/adminhtml/default/default/ffuenf/ffuenf.png" alt="ffuenf - code • design • e-commerce" /></a>

chef-modman

GitHub tag Build Status PayPal Donate

chef-modman installs modman and provides access to a corresponding LWRP.

Dependencies

This cookbook has no direct dependencies.

Description

Installs modman and provides access to a corresponding LWRP.

Platform

The following platforms are supported and tested:

  • Debian 6.x
  • Debian 7.x
  • Ubuntu 14.04.x

Other Debian family distributions are assumed to work.

Usage

Simply include the recipe in your application recipe, where you setup/deploy magento. ruby include_recipe "modman"

ATTENTION: name this cookbook "modman" if you want to use the LWRP like this: ruby modman "MODULENAME" do path "/MAGENTO_ROOT" action :clone end

See Command-Reference for available commands. Keep an eye on the associated actions in the LWRP (providers/default.rb) since some commands had to be rewritten using no "-".

As a sidenote for vagrant users: - You may set up a bash function to use a pseudo-tty with magerun in the vagrant box.

e.g. in your local ~/.bash_profile place: bash modman () { vagrant ssh -- -t modman $@ }

Open a new bash prompt at your Vagrant project and interact with n98-magerun as if it were local. $ modman help $ modman deploy-all

Your commands will be run inside the Vagrant box.

Development

  1. Fork the repository from GitHub.
  2. Clone your fork to your local machine:

    $ git clone git@github.com:USER/chef-modman.git
    
  3. Create a git branch

    $ git checkout -b my_bug_fix
    
  4. Write tests

  5. Make your changes/patches/fixes, committing appropriately

  6. Run the tests: rake style, rake spec, rake integration:vagrant

  7. Push your changes to GitHub

  8. Open a Pull Request

Testing

The following Rake tasks are provided for automated testing of the cookbook:

$ rake -T
rake spec                 # Run ChefSpec examples
rake style                # Run all style checks
rake style:chef           # Lint Chef cookbooks
rake style:ruby           # Run Ruby style checks
rake travis               # Run all tests on Travis

See TESTING.md for detailed information.

License and Author

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.

CHANGELOG for modman

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

2.2.2:

2.2.1:

  • update/integrate testsuites: test-kitchen, foodcritic, rubocop, travis-ci
  • prepare for release on supermarket.chef.io

2.2.0

  • fix provider (missing modman call in all actions) thanks to Fantus

2.1.1

  • update/integrate testsuites: test-kitchen, foodcritic, rubocop, travis-ci

2.1.0

  • update/integrate testsuites: test-kitchen, foodcritic, rubocop, travis-ci
  • pin modman version (because newer versions break proper symlinking)

2.0.0:

  • move installation of modman from LWRP to default recipe

1.0.1:

  • Refactoring: removed @new_resource.exists statements and fixed missing force parameter.

1.0.0:

  • Initial release of modman

Collaborator Number Metric
            

2.2.2 failed this metric

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

Contributing File Metric
            

2.2.2 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
            

2.2.2 failed this metric

FC059: LWRP provider does not declare use_inline_resources: modman/providers/default.rb:1
FC064: Ensure issues_url is set in metadata: modman/metadata.rb:1
FC065: Ensure source_url is set in metadata: modman/metadata.rb:1
FC066: Ensure chef_version is set in metadata: modman/metadata.rb:1
FC069: Ensure standardized license defined in metadata: modman/metadata.rb:1
Run with Foodcritic Version 12.0.1 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

2.2.2 passed this metric

No Binaries Metric
            

2.2.2 passed this metric

Publish Metric
            

2.2.2 passed this metric

Supported Platforms Metric
            

2.2.2 passed this metric

Testing File Metric
            

2.2.2 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
            

2.2.2 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 include a tag that matches this cookbook version number