INTRO: I recently attended SoCal Code Camp to check out talks on some DevOps tools I’ve been looking into adding to my toolkit (Vagrant and either Chef or Ansible). The talk on Chef was in the second hour and looked like it would end up being standing room only, so in the first hour I went to the talk that was in the same room to make sure I’d have a seat for Chef. The talk was “Quickly spin up a new windows machine and get your software installed using Chocolatey” by Justin James. I quickly Googled Chocolatey; being a PowerShell guy I figured it sounded pretty cool and I’d be able to save a seat for Chef, win-win. Little did I know that Chocolatey would be the best thing I’d discover at Code Camp that weekend. 🙂
Also, I need to give credit to itToby for his article Setup Your Own Chocoloatey/NuGet Repository. It was a huge help in getting a jump start in understanding what was going on under the hood with the NuGet Server setup after seeing the demo at Code Camp. I used that walk-through when I built my first server, but then I kept thinking back to the demo and felt it was much easier… Thats when I remembered the Chocolatey.Server package that Justin used and figured I could Boxstarter the whole thing.
I can’t think of a better way to show off how cool Chocolatey and Boxstarter.org are than using them to build themselves. So, get yourself a Windows 2012 server, open up CMD.EXE and run the following: START http://boxstarter.org/package/nr/url?https://raw.githubusercontent.com/RichHopkins/chocolatey-server-build/master/chocolatey.server.build.txt
Click through a few Boxstarter prompts and kick back. Its that easy!
Next post… re-working the Chocolatey and Boxstarter installers and packaging them on your own repository for a fully internal build setup.