Virtualbox

Last week I blogged some Vagrant tips and pretty much jinxed the run I had in the past months. Here’s how: I decided to upgrade to Vagrant 1.1, which broke bento: the current bento master is incompatible with Vagrant 1.1. But selecting the right rbenv env and installing the latest available Vagrant gem (inside the rbenv environment) fixed it. My base box build, but for some reason, the guest addition setup broke and while it worked on Mac OSX, it broke the image completely on Ubuntu....

Development, testing, staging and production — this is how most people devide up different environments for application development. Maintenance and setup of these environments is often not a trivial goal to achieve. Having worked with a couple different code bases and setups over the last decade, I often noticed things like environment specific hacks (if ($env == 'testing') { ... }) in application code and service configurations and a lot of manual labour all around....

If you followed my blog, you probably know about chef and vagrant. So the other day I managed to upgrade to VirtualBox 4.0. The upgrade just happened by accident, so to speak. I noticed that Virtualbox 4.0 had moved from nonfree to contrib on Oracle’s repository which is why I had previously missed it. With 4.0, I am now able to run the latest and greatest Vagrant — and with Vagrant being pre-1....

Ever since I started playing around with Unix ~13 years ago, I’ve been a fan of automating things. What started out as writing little (maybe pointless) shell scripts slowly but surely morphed into infrastructure automation today. As for my, or maybe anyone’s, motivation to do these things, I see three main factors: I’m easily bored — because repeating things is dull. I’m easily distracted (when I’m bored). I’m German: Of course we strive for perfection and excellence....