Skip to content

Instantly share code, notes, and snippets.

@dysinger
dysinger / gist:1480120
Created December 15, 2011 06:55
Always with the json conflicts
chef ➤ cat Gemfile git:develop*
source :rubygems
gem "chef", "~> 0.10.6"
gem "foodcritic", "~> 0.5.1"
chef ➤ bundle install --path vendor/bundle --binstubs git:develop*
Fetching source index for http://rubygems.org/
Bundler could not find compatible versions for gem "json":
In Gemfile:
chef (~> 0.10.6) ruby depends on
json (<= 1.6.1, >= 1.4.4) ruby
@jasonrudolph
jasonrudolph / 00-about.md
Created September 21, 2012 18:42
Rough Notes from Strange Loop 2012
@stevendanna
stevendanna / gist:5582647
Last active December 17, 2015 08:49
Foodcritic Exceptions Explanation

Explanation of Foodcritic Exceptions

The following are brief justifications of the foodcritic exceptions being used in the first pass of foodcritic bug-bashing. In most cases we are excluding rules to make the amount of work more manageable for this first pass. In a few cases, the core cookbook team doesn't think that a rule is appropriate for the Opscode community cookbooks.

FC003 Check whether you are running with chef server before using server-specific features

Ensuring that a cookbook works without a Chef Server is often more work than a simple if statement around a call to search. The READMEs for these cookbooks should clearly state that they currently require a Chef Server and adding conditionals throughout a recipe to also account for this limitation often only serves to clutter the recipe.

In the long run, we welcome better support for chef-solo-style use cases.