I’ve seen some tweets and blog post mentioning Chocolatey and Puppet and then this podcast popped up. It’s PowerScripting Podcast episode 243, Rob Reynolds on Puppet and Chocolatey.

Some days I feel that I’m all over the place and you might think the same. That does not have to be a bad thing. I’m currently working as a Technical Product Manager and Solution Architect and in a role like that it’s good to have some knowledge of what’s out there in order to plan ahead. In my spare time I do web development but not as much at the moment.

Chocolatey is a PowerShell execution engine using the NuGet packaging infrastructure. For Linux there is apt-get and Chocolatey is like apt-get for Windows. It’s a global silent installer for applications and tools that can do anything you can do with PowerShell. Think about what that means when you set up machines for development, test or deployments.

Puppet is IT automation software and using it you can easily automate repetitive tasks, quickly deploy critical applications and more. There are lot’s of modules for Puppet, for example Chocolatey.

How do they come up with names for all these things? Now we have Chocolatey Nuget. Someone with a sweet tooth? And then we have the Puppet central server, the master. So what you end up with on your machine is a Puppet master serving Chocolatey Nuget?