This site is a static archive of the Aegir community site. Documentation has moved to Other community resources can be found on the Contacting the community page.
Skip navigation

1.0-rc3 release notes


1.0-rc3 release notes


Aegir 1.0-rc3 release notes

The Aegir team is very pleased to announce the third release candidate of Aegir 1.0!

This is the third Release Candidate from which we will test fixes to critical bugs from rc2, as well as fix any additional critical bugs found since, until we have no criticals and will then roll out the official 1.0.

This release also includes a fix for a security vulnerability (see below). We recommend you upgrade your Aegir instance to apply this fix.

Key changes in 1.0-rc3

  • A security vulnerability was fixed that prevents arbitrary configuration from being injected into Apache vhosts by way of the Site Aliases form. See #1098304

  • The 'Client' feature / node type has been significantly refactored and simplified, with the ultimate aim of hooking it into other CRM/databases (e.g. for LDAP support), and better Aegir-managed site/user security. This involved an exception to our current 'API freeze' for the sake of getting this important refactoring in. See this summary of the changes this imposes

  • We've upgraded to use Drush 4.4 and Drush Make 2.2 on fresh installs and upgrades. These have been tested and should work without any problems.

Known Issues

  • DNS has no access control - anybody can create any zone (#922252)
  • The site form suffers from some performance issues when you have a lot of platforms (#955854)
  • Cluster servers are probably broken right now (#1016890)
  • Aliases are not persisted across Migrate, (Rename), Clone (provision-deploy) (#1004526)
  • The version tag wasn't updated properly and still reads 1.0-rc2
  • See all the issues tagged as aegir-1.0 and issues marked as 'major' for our comprehensive list of outstanding issues.

Installing and upgrading

The canonical source of installation documentation has moved from the usual INSTALL.txt to the community site at:

In a similar fashion, the upgrade documentation has now been moved to the community site at

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes. You can download the script from

It is still imperative that you read the the Upgrade Guide ( and follow all version-specific upgrade instructions located at the end of the document before trying to run the upgrade script. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or rc1/2, there are unlikely to be any version-specific manual steps required to upgrade to 1.0-rc3, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

The script attempts to backup the existing backend components, download new versions, and then run the hostmaster-migrate command. It assumes you are upgrading from the previous release (hostmaster-6.x-1.0-rc2). If you are not, you may have to edit the script to change the OLD_DRUPAL_DIR variable.

Bugs fixed

New features

Need help?

If you struggle to install or upgrade your Aegir system, you have a number of options available to you for getting help.

Consult this page for more:

Thanks to our awesome community for their help, support and encouragement as always! Enjoy the new release :)

Referenced by Last post Author
Aegir 1.0-rc3 is released! Wed, 04/06/2011 - 13:21 mig5
Need help?


The notebook section provides a way for you to store and share information with your group members. With the book feature you can:

  • Add book pages and organize them hierarchically into different books.
  • Attach files to pages to share them with others.
  • Track changes that others have made and revert changes as necessary.
  • Archive books that are no longer of interest to the group. Archived books can be reactivated later if needed.