Firstly, forgive me if I get my terminology mixed up. Being sold on
the virtues of TDD, I have a growing itch to test our puppet
manifests. Now by this I dont mean testing, say, the mechanics of a
define to test that the right things *happen*, I mean being able to
say that given a collection of
seen some issues with
2.6 http://projects.puppetlabs.com/issues/4409) .
I would recommend either:
1. trying your use case with 2.6
2. keep a single copy of your plugins in the puppetmaster's modulepath.
hope this helps,
Dan
On Wed, Aug 18, 2010 at 3:38 AM, Darren Worrall iwebdar
Hey folks,
I have just created a puppet environment called testing by adding the
following to puppet.conf on the puppetmaster:
[testing]
manifest = /etc/puppet/testing/manifests/site.pp
modulepath = /etc/puppet/testing/modules
We are collecting all our customisations into a module,
Hey folks,
We're on the verge of deploying puppet into production so have changed
from using webrick to mongrel with an apache reverse proxy. The nodes
were behind a NAT firewall under webrick but it didnt seem to mind,
however something isnt right with my reverse proxy configuration and I
cant
