I hear this question a lot - both from non-technical folk, as well as agencies who know they are 'missing something' in their approach to deploying, securing and scaling applications, but aren't sure if a sysadmin will solve it. 'What is it that you (a sysadmin) actually does (e.g the day-to-day, or in general)?'
Update: Aegir subfolder support is apparently now in Aegir 2.x proper. See the ticket
About 2 and a half years ago, a feature request was made for the Aegir project to support the creation/management of 'example.com/mysite1', 'example.com/mysite2' subdirectory Drupal sites.
Last weekend (on the 15th January) I delivered a talk on Aegir at DrupalDownUnder 2012. I tried to do something we've not done before in Aegir demos: demonstrate basic usage along with more advanced, automated use of Aegir.
Overall I was happy with my talk - I ran out of time, as I was a bit too ambitious, but I really wanted to show the advanced stuff without alienating the newbies.
Drupal has a big following in Australia, but it's somewhat overlooked due to the size of the country and the fact that the focus is spread out over such a large area. On top of that, the remote nature of this part of the world sees us even combine events with other nations such as New Zealand and various Asian countries.
This time two years ago, I wrote an article called Drupal deployment and workflows with version control, Drush Make and Aegir. It remains my most popular article on my site, according to my stats.
The session videos are going up very quickly at the London DrupalCon, as compared to previous conventions!
Here are the two Aegir sessions:
I'll be presenting a talk at Drupal Melbourne on Tuesday, July 12th 2011. The talk will be an overview of how the Aegir project uses Jenkins to continuously test the Aegir code, and how you can use a combination of Git, Drush Make, Aegir and Jenkins to test an installation of your site automatically every time you commit a change to your project.