Simple answer: don't. Use apache's conf.d construct to manage virtual hosts
for each so they can contain their own config. See the puppetlabs apache
module:
https://github.com/puppetlabs/puppetlabs-apache
On Wednesday, April 3, 2013 10:57:30 AM UTC-6, Cesar Covarrubias wrote:
>
> So I am workin
You don't
You'd manage a static httpd.conf which includes from a conf.d directory
containing site-specific configs. At the end of the day you want a define
that allows you do work like this psuedo code:
http:site {
thisawesomesiteisenabledbydefault:;
thisisold: ensure => absent;
}
--
Yo
