[chef] Re: Re: Apache2 cookbook on CentOS?


Chronological Thread 
  • From: Ranjib Dey < >
  • To:
  • Subject: [chef] Re: Re: Apache2 cookbook on CentOS?
  • Date: Wed, 12 Oct 2011 01:34:56 +0530

Brad,
the cookbook should work as it is.  As adam has already said, change the default[:apache][:listen_ports]  = ["80"],
we are using the same cookbook to run our infrastructure (centos 5.5)

On Wed, Oct 12, 2011 at 12:49 AM, Adam Jacob < "> > wrote:
Sure - you set the listen_ports attribute to only 443, drop off a
virtual host using the included definition, disable all the default
sites, and enable only that vhost. The vhost has the SSL config
inside.

Best,
Adam

On Tue, Oct 11, 2011 at 7:59 AM, Brad Knowles < "> > wrote:
> Folks,
>
> So, looking at the systems we have deployed with the standard Chef apache2 cookbook, it has become clear to me that this was cargo-culted straight from Debian -- lock, stock, and two smoking barrels (named a2ensite and a2dissite).
>
> However, what is not obvious to me is how to take this configuration on a CentOS 5.6 box and turn it into a proper working apache configuration, especially one that does name-based virtual hosting on https only (with a wildcard cert) and completely skips port 80 altogether.
>
>
> Does anyone have any favourite resources on the subject of "Debian Apache for Dummies who are not running Debian", or something related?
>
> Thanks!
>
> --
> Brad Knowles < "> >
> SAGE Level IV, Chef Level 0.0.1
>
>



--
Opscode, Inc.
Adam Jacob, Chief Product Officer
T: (206) 619-7151 E: ">




Archive powered by MHonArc 2.6.16.

§