Drush

Using Vagrant in Production

After presenting on 'Fearless Development with Drush, Vagrant and Aegir' at DrupalCamp Montreal, I was approached about a rather interesting project. It involved synchronizing data between a couple dozen Drupal sites running on Windows systems. To be able to better manage the Drupal components on these systems, we decided to deploy Aegir on Vagrant-based virtual machines (VMs).

Easy Switching Between Drush 4.x and 5.x

Drush 5 was released a few months ago and has pretty much become the standard by now. Thanks to lots of work by anarcat and others, Aegir's upcoming 2.x will support it natively. He's also been busy packaging Drush 5 for Debian, and I look forward to making the switch, as it's the default in Wheezy/Testing.

Aegir-up: a Vagrant project templating framework

!!! WARNING: This blog post contains code !!!

Quite a bit of it, actually. It's in Ruby. I've never coded in Ruby before this, so in all likelihood it sucks. But I probably won't be able to recognize that until I've had more experience hacking on Ruby code (maybe in Vagrant or Puppet). Also, my academic and professional background is in philosophy and marketing, so there's no help there. Anyway, consider yourself warned. That said, I'm very open to constructive criticism, so feel free to make suggestions.

Subscribe to RSS - Drush