On Sun, Dec 20, 2009 at 4:57 AM, R.I.Pienaar <r...@devco.net> wrote: > hello, > > ----- "Douglas Garstang" <doug.garst...@gmail.com> wrote: > >> I'd like to be able to split out my puppet production and test >> environments so that I can continue to develop puppet >> modules/manifests without breaking production. How are people doing >> this? Puppet environments may be one way. I guess I'd have a >> main(prod) environment and a test one. When I was finished with >> testing, I could rsync the files over to the prod environment. Is >> this >> how others are doing it? > > http://www.devco.net/archives/2009/10/10/puppet_environments.php > > That's how I do it, aim is to avoid many copies of the same module just > because we have multiple environments, but still have the ability to create > those versions during the dev cycle. > > not for everyone, but maybe it help you in the right direction.
Thanks to everyone for the replies. Are you using multiple environments though? And, if using multiple environments, how do you structure it? The puppet documentation is a bit vague on the subject. For instance, it's not clear to me if you would structure it so that you have a top level dir ABOVE puppet called prod, test etc, or if you would create subdirs BELOW manifests, modules etc called prod, test. The next question is, where do you branch? If you have a top level dir above puppet, I guess that's pretty easy, but if you have multiple dirs below manifests, modules etc, then you'd need to branch each which becomes more complex. Doug -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
