chef-solo

I'd like to use Ruby 2.0 on Amazon OpsWorks, so I'm trying the following: Choose custom cookbooks and set them to my fork of https://github.com/aws/opsworks-cookbooks Update all version numbers here https://github.com/aws/opsworks-cookbooks/blob/master/ruby/attributes/ruby.rb to 2.0 values. This doesn't seem to have any effect, though. Do custom cookbooks override their built in counterparts? Does OpsWorks use the Ruby recipe from the cookbook for basic Ruby setup? The same question applies to Nginx too - can I control versions and settings by changing my fork for the cookbooks? OpsWorks now

Just ran nginx::source recipe on my vagrant box, and I have very unusual behaviour. When I include a recipe from the Vagrantfile (as below), everything works like a charm, chef.add_recipe("project::nginx") chef.add_recipe("nginx::source") ( project::nginx recipe is very simple. Using it to override default attributes of the nginx cookbook) but if I include a recipe at the very end of project::nginx (mentioned up), everything falls apart: node.default['nginx']['server_names_hash_bucket_size'] = 128 include_recipe "nginx::source" Until now I didn't know there's any difference in behaviour

I just installed java using chef cookbook and updated PATH environment variable for all users (added new file to /etc/profile.d/). Is it possible to tell chef to reload PATH variable? When I do something like this: execute "java_check" do command "java -version" end Is says that java could not be found. It works fine when I log out, log in again and then run chef recipe. I'm not 100% sure you can update the PATH variable for future chef runs, but you can set it up manually using the environment attribute within the execute stanza. This can also be used on other Resources as well. See: http:/