On Mon, Aug 2, 2010 at 4:50 AM, Kenneth Holter <[email protected]> wrote: > > Let me briefly mention that we're going to use external nodes to tell > which environment (prod, qass, ...) a node belongs to, and use the > build in puppet enironments to separate code between the environments > (production clients will pull modules from a different module area > than clients in for example qass, and so forth).
The organization of using environments in puppet with module paths referencing multiple, different working copies of the same version control repository checked out to different branches works quite well for many people. Git is particularly good in this case since it's designed to quickly switch the working copy among branches quickly and easily. Doing so in git doesn't result in a different filesystem path which is convenient when setting the modulepath in each environment. -- Jeff McCune http://www.puppetlabs.com/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
