The other day I posted an article about
upgrading Chef and Vagrant, and the pains you can end up having by relying on third-party vagrant boxes instead of building your own with VeeWee.
Getting started was initially confusing to me, as I knew VeeWee was a gem, so I just tried installing it directly into my application gemset. The trouble here is that VeeWee depends on the Vagrant gem version v1.0.x and Vagrant is now not only on 1.2.2 but not actually a gem anymore.
Read More »
The other day I thought to myself, I really should be using a RVM gemset for my "devops" repo, which contains all my Vagrant and Chef logic (along with submodules for everything else). This broke everything, but I got there in the end.
Read More »
Working for Kapture I've been charged with something I've never really had to do before: Managing a big-ass architecture of different servers that all handle different tasks. Theoretically I've always known how it works, and I've worked in projects that have had these systems, but I've never been put in charge of how that whole situation works out. So this little web developer had to do a lot of learning.
Read More »
Back in the UK at PHPNE this May I saw an awesome talk from Ian Chilton, who explained very simply why using Vagrant for your development environments was a good idea. He mentioned briefly server provisioning but didn't get fully into it, and suggested we go out and play with Puppet and Chef to see which fit our needs.
Read More »