Puppet

Nifty trick for simpler testing of provisioning in Vagrant

I'm a huge fan of Vagrant and have been using it pretty extensively lately. In particular, I'm using it to develop, test and debug a number of Puppet modules. Obviously I keep these modules under version control, for which I strongly prefer Git. The problem I was coming across was that, in order to run git commands, I have to be in the appropriate module's sub-directory, but to run 'vagrant provision' I needed to be in the root of the vagrant project.

Setting up a proper dev environment with VirtualBox and Vagrant

For awhile now, I've been meaning to experiment with Puppet to get my server (and maybe even desktop!) config management under control. Since I've called in sick today (I guess I'll just have to miss that budget meeting...), I figure this is a fine opportunity to invest in some skill-building.

Note that I'm not a sysadmin or developer by training; but thankfully, I have the privilege to work with several incredibly competent ones at Koumbit Networks.

Syndicate content