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

[Jesse Campbell < >]

A more normal redirect pattern I have seen is to save the host name from the request parameter and simply change the scheme from http to https...

here's how we do it on an F5:

HTTP::redirect https://[HTTP::host][HTTP::uri]

I'm not sure off hand what the proper syntax is for nginx or apache, but it should be straightforward

-Jesse

On Thu, Feb 28, 2013 at 12:36 PM, Cassiano Leal < " target="_blank"> > wrote:

Out of curiosity, why redirect in the first place? :)

- cassiano

On Thursday, February 28, 2013 at 14:06, Adam Jacob wrote:

It's a reasonable default for most situations – the alternative is to use the IP Address, which is actively icky as well.

Adam

From: Cassiano Leal < " target="_blank"> >
Reply-To: " " target="_blank"> " < " target="_blank"> >
Date: Thursday, February 28, 2013 7:01 AM
To: " " target="_blank"> " < " target="_blank"> >
Subject: [chef] chef-server on a VM

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