Tagged with opscode

Chef: Cook your own automated environment

Posted by Edmund Haselwanter on Mar 13, 2009
Tags: chef, environment 2.0, iclassify, opschef, opscode, opscookbook, puppet
Technorati Tags: chef, environment 2.0, iclassify, opschef, opscode, opscookbook, puppet

There is a new kid on the configuration management block Chef from Opscode. Here is a blog post about Puppet vs. Chef.

Chef is kind of Puppet with integrated iClassify and a rubyish configuration DSL. No wonder, Adam Jacob joined forces on Chef.

You can find it on github

• http://github.com/opscode/chef/tree/master
• http://github.com/opscode/chef-repo/tree/master
• http://github.com/opscode/cookbooks/tree/master

Extending Chef from Opscode with header params for http_request

Posted by Edmund Haselwanter on Jul 31, 2009
Tags: http_request, opschef, opscode
Technorati Tags: http_request, opschef, opscode

Added support for custom header options in chef for the http_request

Opscode Chef Ticket
Resolved on Github

webalizer cookbook and definition for chef from opscode

Posted by Edmund Haselwanter on Oct 13, 2009
Tags: apache2, chef, opschef, opscode, opscookbook, sysadmin
Technorati Tags: apache2, chef, opschef, opscode, opscookbook, sysadmin

Install and run the webalizer with Chef from Opscode

http://github.com/ehaselwanter/cookbooks/tree/COOK-195/webalizer

As DRY as possible ;-)

chef from opscode and the power of ruby

Posted by Edmund Haselwanter on Oct 14, 2009
Tags: chef, opschef, opscode, opscookbook, sysadmin
Technorati Tags: chef, opschef, opscode, opscookbook, sysadmin

Recent releases of chef from opscode provide a new resource: ruby_block

This is really great news as this allows for interesting problem solving.

Consider you want to do a very special HTTP request. E.g. a GET to localhost but with custom “Host” header information.