On Wed, Feb 8, 2012 at 3:46 PM, the_fonz wrote:
> Hi,
>
> I'd like to start using Puppet to manage an httpd.conf file across
> several webservers.
Others have already correctly steered you towards templates for this sort
of thing, but I have one aside...
> each httpd.conf
> file has multiple
Further, you should remember that there is no reason for an Apache
configuration to be monolithic. Apache is perfectly happy to have a bunch
of files to include. Throw in a naming convention (e.g. files named
foo.ssl will be included by my SSL config file) and you've got some real
flexibility.
O
On Wed, Feb 8, 2012 at 3:46 PM, the_fonz wrote:
> Hi,
>
> I'd like to start using Puppet to manage an httpd.conf file across
> several webservers. I have a Puppet server and client config setup and
> have followed a couple of simple "How To's" to get off the ground. I'm
> syncing a couple of files
Hi,
I'd like to start using Puppet to manage an httpd.conf file across
several webservers. I have a Puppet server and client config setup and
have followed a couple of simple "How To's" to get off the ground. I'm
syncing a couple of files and ensuring certain packages are installed
etc on the clie
