On Mon, Dec 21, 2009 at 8:32 AM, R.I.Pienaar <r...@devco.net> wrote: > hello, > > > ----- "Douglas Garstang" <doug.garst...@gmail.com> wrote: > >> >>>> http://www.devco.net/archives/2009/10/10/puppet_environments.php > >> > [staging] >> > modulepath = >> /etc/puppet-staging/modules:/etc/puppet-staging/services >> > manifest = /etc/puppet-staging/manifests/site.pp >> > >> > [development] >> > modulepath = >> > /etc/puppet-development/modules:/etc/puppet-development/services >> > manifest = /etc/puppet-development/manifests/site.pp > > > >> >> So, Matt, it looks like you have three completely different puppet >> areas (/etc/puppet, /etc/puppet-development and so on). That's kind >> of what I thought I might need to do. There's no point in branching a >> specific directory inside puppet because then you don't have the rest >> of the stuff puppet needs to run, and... I'm not sure how svn feels >> about a branch INSIDE a working copy. >> >> But... how do you serve up those multiple puppet environments? Are > > you really should take some time to just play with this, or at least read the > links, wiki pages and samples we've been posting here. > > Internally - when configured as in the quote above, or on the url in the top > bit or on the puppet wiki environment page - puppet will take care of all the > serving needs for you. > > if your client says it's in the environment 'development' then for Matts > example it would find files/modules/etc in > /etc/puppet-development/modules:/etc/puppet-development/services > > The devco.net url shows you how you could branch - using svn but git can work > too - just a specific module and why that might be a good choice. > > Just play with it, setup a master and experiment, all the needed information > is there, once you play with you'll no doubt have a 'Oh, thats how it work!' > moment.
I did read the reductive labs documentation (which is unclear as usual), and the devco site before posting here, and again after someone referenced it. I understand the concept of multiple environments quite well, and that's not the issue. The issue is how I integrate this functionality back into subversion such that I don't have to be constantly copying files between development and production. The devco site does NOT show you how you can branch. It says you can do it, and that's about it. It does not address for example the issue of when making a branch, and checking the branch out to work on it, you suddenly have no puppet environment to work in. How do you test? Lastly, I have a functional config presently. I don't want to muck around with it and break it. There's been many a time where I've gotten svn confused by doing constant moves of directories etc to the point where I have to completely blow everything away in that tree and start again. 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.
