Applying Drupal Security Updates with Aegir: Screencast
We manage a cluster of Open Atrium sites for clients using Aegir. To get a sense of how powerful Aegir is for running a hosted service here is an under 3 minute video of Jeff and I applying today's Drupal security patch to all of our sites.
A Little More Background
A few hours ago, a critical Drupal core security vulnerability that allowed cross site scripting in Drupal 6 core OpenID and a possible apache file executable issue with the File API was identified and fixed by Drupal's Security team. Since Open Atrium Beta 2.1 was running on Drupal 6.13 core, our Open Atrium sites were potentially vulnerable to this security release and we needed to patch our sites with Drupal 6.14. The Open Atrium team released Beta 3 less than two hours after the security announcement, and we were good to run the upgrades.
@Wim Mostrey: adding a new
@Wim Mostrey: adding a new core or ‘platform’ in Aegir is a trivial task of downloading the platform (drush or wget/tar/whatever) and adding a ‘Platform’ node in Aegir.
In other words, in Aegir, you are not ‘updating’ an existing core but adding a new one altogether and then moving the site onto it.
I’ve similar steps on my blog which show screenshots of creating a new platform first, along with all the other steps.
Loading the new Open Atrium?
On the video you mention that you already loaded the new Open Atrium. In a tutorial about applying security updates it might be important to also show how you actually do this since you’re not just updating a couple of modules but the complete Drupal core to the latest version.