Chef solo from master


#1

So I just pulled down master and was playing around with chef solo. When
processing a template it’s trying to connect to the server at
localhost:4000.
Is it too early to be playing around with this?

Chris


#2

On 8/06/2009, at 11:07 AM, snacktime wrote:

So I just pulled down master and was playing around with chef solo.
When processing a template it’s trying to connect to the server at
localhost:4000.

Ticket has been opened and fixed (twice, doh), pending merge (http://tickets.opscode.com/browse/CHEF-330
)

Is it too early to be playing around with this?

I believe we’re hoping to start full public testing of master once our
last round of internally tested bugs are closed, however, feel free to
test as normal and open tickets for any bugs you encounter if there
are any :slight_smile:


AJ Christensen, Software Engineer
Opscode, Inc.
E: aj@opscode.com


#3

Appears that Chef::Config[:solo] isn’t getting set. Should this be getting
set in Chef::Application::Solo or do we need to put it in the config file
now?

On Sun, Jun 7, 2009 at 4:07 PM, snacktime snacktime@gmail.com wrote:

So I just pulled down master and was playing around with chef solo. When
processing a template it’s trying to connect to the server at
localhost:4000.
Is it too early to be playing around with this?

Chris