On Wednesday, March 2, 2011 at 5:52 PM, Patrick Connolly wrote: Still trying to sort out whether this use-case even makes sense, but what if I were to use Puppet to standardize development environments? > > It may be the case that someone makes a change or sets themselves up with a > tool/configuration that allows them to work more efficiently. I can imagine a > scenario where, after selling the benefit of these changes to a project lead, > we'd want to push that change back to the puppet master so that every dev > system would get them without developers having do it manually. Now > everyone's on the same page and working with the same tools. > > Any thoughts? I like the Git idea, and might pursue that, but wondering if > anyone has input :)
I use DevStructure's (full disclosure: I'm the CTO) Blueprint tool to promote configurations from development to production. Blueprint figures out what I did to my development server and then I commit the Puppet code it generates to Git. http://devstructure.com/tutorial.html http://devstructure.github.com/blueprint/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
