First, I apologize for any confusion and inconvenience.
I’ve updated the “Installing Chef from HEAD” page to reflect changes
that 0.5.7 brings.
The bootstrap-0.5.6.tar.gz cookbook bundle doesn’t configure clients,
just server. Version 32  of the main Installation page describes
how to install using the older method. Do note that the 0.5.6 version
will start Chef Server as a runit service, and 0.5.7+ will run Chef
Server as a Rack app under Passenger+Apache. Also, we have a page that
describes how to switch from a runit-based chef-server to Passenger .
We think the new procedure is better, as fronting chef-server with
Apache+Passenger allows stronger security control.
 Version 32 page: <http://wiki.opscode.com/pages/viewpage.action?pageId=1835069
On Apr 25, 2009, at 9:09 PM, snacktime wrote:
Ya 0.5.7 looks like what I should be testing with, as the
installation stuff looks quite a bit more complete.
On Sat, Apr 25, 2009 at 8:01 PM, Arjuna Christensen <firstname.lastname@example.org
I believe Josh is working through some changes on the wiki for the
upcoming 0.6 release (which can be tested as 0.5.7), so this
information may not necessarily be “in sync”.
On 26/04/2009, at 2:57 PM, snacktime wrote:
Still working on it, but at first glance the chef client
installation as documented on the wiki is not working correctly. It
installs the server even when specifying chef::client, chef path is
not set to /srv/chef as the default as stated in the readme, and the
file mode in the recipe is a string, chef seems to expect an
integer. The recipes also assume that all the gem binaries are in /
This is version 0.5.6.
Joshua Timberman | www.opscode.com
email@example.com | 720.878.4322