[chef] Re: Fail to connect to chef server when using vagrant

[Knox Lively < >]

That’s exactly what I did, I asked a co-worker and he said he utilized a 
symlink and chefvm.  He placed a config.json in each of the appropriate 
configuration directories and a simple symlink from his “~/.chef/config.json” 
(which will be changed to the appropriate chef environment each time you 
switch with chefvm) to “~/.berkshelf/config.json”.

Thanks.


On Apr 10, 2014, at 19:16, Julian C. Dunn 
<
 >
 wrote:

> On Wed, Apr 9, 2014 at 10:13 PM, Knox Lively 
> <
 >
>  wrote:
>> That was it, thanks again.  I do have one more question though.  We have 
>> two completely separate chef environments
>> for each of our products.  I ran berks configure which indeed wrote 
>> config.json which allowed me to complete the
>> handshake.  However, that json document has information particular to only 
>> one of the environments we run in, is there
>> some sort of 'vm' solution for berksfile that would allow switching 
>> between environments?
> 
> Not that I'm aware of at the moment, although you could probably cook
> something up using shell aliases and symbolic links (which is
> essentially what the equivalents for .chef, like chefvm, do)
> 
> I would also anticipate that as Berkshelf gets absorbed more into the
> Chef ecosystem, this separate "config.json" will go away.
> 
> - Julian
> 
> -- 
> [ Julian C. Dunn 
> <
 >
>           * Sorry, I'm    ]
> [ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ;]
> [ gopher://sdf.org/1/users/keymaker/           * compliant!    ;]
> [ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]