[chef] Re: Re: chef-server on a VM

[Cassiano Leal < >]

Hmm… I'll try that, then. Still, it's a bit annoying that the guide on docs.opscode.com doesn't work.

I was under the impression that the cookbook had not been updated to work with Chef 11, since it says:

REQUIREMENTS

Chef ~> 0.10.0, 10.0 is required.

on README.md… :)

Also, the guide on docs.opscode does not mention how to configure knife.rb (hosted chef has the option to download a pre-configured one). Not even the API URL is mentioned in the doc (used to be http://host:4000, now it's https://host).

- cassiano

On Thursday, February 28, 2013 at 12:06, Pete Cheslock wrote:

Yea - I recently noticed the same thing when testing on a VM - I ended up using the chef-server community cookbook and in there are  series of options you can change - including the hostname and a few hundred other options.

https://github.com/opscode-cookbooks/chef-server/blob/master/attributes/default.rb#L27

On Thu, Feb 28, 2013 at 10:01 AM, Cassiano Leal < " target="_blank"> > wrote:

Ohai Chefs,

Why does the omnibus chef-server deb not work by default on a VM?

I'm following http://docs.opscode.com/chef/install_server_scenario_vm.html but at the end, if I hit the webserver on port 80 it redirects me to the VM's hostname, which is obviously not accessible from outside of the VM unless I edit my hostsfile.

I'm wondering why it's set like that by default; it seems like an anti-pattern. Also, how do I change this behaviour? 

Other than that, the omnibus package is a breeze to install. Fantastic job!

- cassiano