On 05/07/2014 07:04 PM, Alex Scoble wrote: > All in all, I love the product, don't get me wrong, and maybe it looks > pretty stable when you're at the guru level and figuring out new stuff > is fairly easy, but for me, it's just me and a coworker trying to mature > our linux and puppet infrastructure, processes and workflows. Neither of > us are developers, so are learning that side of things as best as we can > while we learn Puppet, git, hiera, Geppetto (which is the bee's knees, > just be super careful when you try to merge two significantly different > branches together using it), beaker, rspec, ruby and so on.
Thanks for the in-debt write-up, Alex. So what I took from it is that, for all the documentation and buzzing blog-sphere, it can be daunting to pick the patterns, solutions and tool chain that are best fitted for one's particular needs and goals. Is that a fair summary? I can get behind that, I guess, but I have a hard time coming up with a real good strategy to handle this. Yes, it's a rich ecosystems, and that has its own downsides. Perhaps the Learning Puppet course should culminate in the ultimate advice to join the list and ask for hints regarding one's own goals and environment? But then such threads run an elevated risk of starving, I feel, because some new users tend to ask quite broadly with too little to go on for the senior members to take interest in resolving the challenge. </ramble> Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5379EFF2.7020409%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
