In the long term, what we have in mind is providing a proper testing suite for the developers and testers in the company to use. But to get to grips with the software and what it's capable of doing, he came up with a great idea: transition our routine cron tasks into Jenkins 'builds'.
I did not know this until just last week. Seems everyone I've mentioned it to already did, so I thought I'd better prove my noobness in bulk to you all now by writing about it.
It seems when you crypt a password with htpasswd and use (at least) basic mod_auth in Apache, the crypt only takes the first 8 characters of your password for use in authenticating a user.
Aegir is a pretty powerful tool that allows you to very quickly provision new Drupal sites out of the box and manage them throughout their lifespan through a variety of tasks.
Its ability to understand different install profiles and thus 'distributions' shoots the awesome factor through the roof once you can deploy instances of OpenAtrium, Pressflow, ManagingNews or your own custom distro in just a couple of clicks.
The session was designed in lieu of potentially presenting a future series of Aegir-related dojo sessions that progress in terms of topic complexity (i.e beginner through to expert).
For this reason, the session was largely an introduction to the system and how to use it, with some 'under the hood' peeks where possible for those users who are comfortable with the terminology and process already.
Many Aegir users ask whether there is a way to schedule backups of all sites provisioned in Aegir. Currently at the time of writing, no such scheduling exists within Aegir itself, since we have a few design decisions to work out (such as where to store the backups, especially when multi-server comes in!)
For the meantime, here's a crude little shell script that might help you. You should execute it as the aegir user.
I did a screencast on how you can use Drush Make to generate 'builds' based on Drupal core, with optional components such as install profiles + module/theme/library dependencies. The example given is the Managing News news aggregation system.
I then show how you can add the build as a Platform in Aegir, and rapidly provision sites on it in a multisite structure.
Here's a simple perl script that uses curl to search for a regex pattern on a website.
It returns status values that are Nagios compatible. This means you can write a command definition for Nagios that looks like this: