- From: snacktime <snacktime@gmail.com>
- To: chef@lists.opscode.com
- Subject: Re: chef solo from master
- Date: Sun, 7 Jun 2009 16:15:49 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=YQFCIGMHm4WCW61SO92Qy+lC+xskSwVYvCqNkGiMTwJ6SgoEnVNDwsVX1v/Ni7QD2x 2FekIzYgE3zufuWatjyK7dRcar7zs4HREy6ySDw9/LpkNO2dUicPaj6jii0CTd853hBw j222GB+laAOp8iqeYY+3APWEWyqyBQn1Klmr0=
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?
Archive powered by MHonArc 2.6.16.