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

[Ranjib Dey < >]

model the site specific configs as a template and drop it inside  node[:apache][:dir]}/sites-available/default, and then use the apache_site definition to enable this site specific config.

Look ate the last lines of the default recipe inside apache cookbook, the way default site is enabled (the [template "#{node[:apache][:dir]}/sites-available/default" ] directive and the [apache_site "default"] directive)

On Wed, Oct 12, 2011 at 2:42 AM, Brad Knowles < "> > wrote:

On Oct 11, 2011, at 3:04 PM, Ranjib Dey wrote:

> 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)

It took me a while to warp my brain around the debian-style configuration, and to understand it well enough to be able to figure out whether or not I wanted to drink the kool-aid and how to do so.

Now that I've figured out how to manually create a working skeleton prototype of a name-based virtual host SSL-only server, I'm popping back up the stack a few levels so that I can get Chef to create that for me based on the configuration information I provide.

At the moment, the stumbling block in front of me is figuring out how to provide the SSLCertificateFile and SSLCertificateKeyFile configuration lines, as well as the corresponding self-signed wildcard cert & key that I am testing with.

--
Brad Knowles < "> >
SAGE Level IV, Chef Level 0.0.1