PuppetConf 2013

I made a terrible mistake during my first week on the job at Betable over a year ago: I built out our Linux staging and production environments first and ignored our Mac development environments. This is asking for trouble anywhere but especially in heavily service-oriented architectures such as ours. So consider this talk a postmortem of our recovery from that decision. We'll discuss when and whether Vagrant, Boxen, and other tools are and aren't appropriate, to have one Puppet codebase or two, and how we at Betable deal with multiple package managers and configuration styles, testing and promoting changes, and a lot of the details and warts in the tools we use: Go, Node.js, Cassandra, and more.