Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I inherited our company's Chef repository and I'm learning as I go. One issue that I've found a workaround for (but would like to understand or avoid if possible) is that attribute defaults specified in cookbooks are not available to nodes in my development environment. So to get these things that work fine in production to run in development, I have to make a change like so:

Works in production

default[:webservices][:debug] = "False"
default[:webservices][:template_debug] = "False"

Works in development

set[:webservices][:debug] = "False"
set[:webservices][:template_debug] = "False"

Going forward, I want to be able to specify a default and then override it for development, say to use development database settings, etc. with the same templates. Why isn't the default accessor working in development? I can provide more configuration details upon request.

share|improve this question
By "development environment" do you mean a Chef environment or a separate system you are using for development? – Tim Potter Sep 19 '12 at 22:23
My bad. I mean a Chef environment called "development." – Justin Force Sep 19 '12 at 22:35

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.