The way we manage is by using multiple File paths right now , for example
file { "/usr/local/bin/portstats.pl":
ensure => present,
owner => root,
group => root,
mode => 755,
source => ["puppet:///cacti/$pr
On Dec 12, 2010, at 8:00 PM, Josh wrote:
> Greetings,
> I'm just getting started with setting up Puppet in an environment of
> about ~15 servers, a mixture of Mac OS X servers and Ubuntu servers -
> each with different roles and obviously different versions of configs.
>
> Before I get too carri
Daniel Piddock wrote:
You can use a variable in the source path definition. e.g.
puppet:///files/$host/config.cfg.
Though, using puppet:///module/files/config.cfg.$hostname as the source
means it can sit inside the module, so all your configs can be in a
single class in a single module. I fin
On 13/12/10 04:00, Josh wrote:
> Greetings,
> I'm just getting started with setting up Puppet in an environment of
> about ~15 servers, a mixture of Mac OS X servers and Ubuntu servers -
> each with different roles and obviously different versions of configs.
>
> Before I get too carried away, I wa
Greetings,
I'm just getting started with setting up Puppet in an environment of
about ~15 servers, a mixture of Mac OS X servers and Ubuntu servers -
each with different roles and obviously different versions of configs.
Before I get too carried away, I was hoping to get advice on the "rule
of thu
