Aegir 0.3 RC3 released

We're proud to announce the third release candidate of the 0.3 branch of the Aegir hosting system for Drupal.
Ægir is a set of contributed modules for Drupal that aims to solve the problem of managing a large number of Drupal sites. It does this by providing you with a simple Drupal based hosting front end for your entire network of sites. To deploy a new site you simply have to create a new Site node. To backup or upgrade sites, you simply manage your site nodes as you would any other node.
This is the third release candidate of the 0.3 branch. This release is a maintenance release and the only project goal is the porting of Aegir 0.2 to Drupal 6. As such the code base is already feature complete and only bug fixes will be accepted before the final release is made.
Fixes in this release include :
- Various fixes in install.sh.txt to automate aegir installation on a debian/ubuntu host
- Fixed a critical error related to file permissions. see: http://groups.drupal.org/node/24854#fileperms
To install Aegir you need
- A unix based operating system.
Aegir will not work on windows.
- Full access to your own server or machine.
Shared hosting will not give you enough permissions to install new sites
- A Drupal installation that is web accessible with it's own hostname.
It is not possible to install Aegir in a subdirectory. You may need to add entries to your /etc/hosts file to test Aegir, as it does not provision DNS yet.
Installing Aegir
Aegir's architecture provides the ability to manage multiple backends through a single front end.
Each server that Aegir is installed on, needs to have it's own backend.
The canonical way of installing Aegir is to follow the INSTALL.txt file of the hostmaster profile. The instructions here are provided for your convenience but documentation bugs should be filed against the INSTALL.txt file.
- Installing Drush
The Aegir backend is an extension to the Drush 2.x release, which needs to be installed first.
- Download Drush 2.x
Extract it somewhere your user has access to it. I always extract it to
/home/adrian/drush.You may also choose to create an alias to it, or symlink the drush.php file into your /usr/sbin directory. More information on this is available in the Drush readme.
important note: Drush 2.x is not a module, and it should not be installed inside a Drupal directory. Any existing instances of Drush 1.x or the deprecated Drush Extras module should be deleted from the filesystem, to avoid PHP function name collisions.
- Download Drush 2.x
- Installing Provision
Provision is the backend of the Aegir hosting system, as with Drush, there should only be one instance of provision per server.
- Create the .drush directory in the home directory of the user Provision is being installed as.
Use this command :
mkdir -p ~/.drush - Download Provision 0.3 RC3
Extract it into the
~/.drushdirectory, so it is located at~/.drush/provision
- Create the .drush directory in the home directory of the user Provision is being installed as.
- Installing Hostmaster and Hosting
Hosting is the front end to the Aegir hosting system. The Hostmaster install profile initializes a new Drupal site with all the information
that Hosting requires to operate, and provides the installation wizard for configuration.- Download the Drupal 6.13 release
Extract it to the location you host sites from (example:
/var/www/aegir/drupal-6.13). You may also use an existing Drupal 5.x directory instead. - Download Hostmaster 0.3 RC3
Extract it into the profiles folder of your Drupal installation (example:
/var/www/aegir/drupal-6.13/profiles/hostmaster) - Create the profiles/hostmaster/modules directory.
(example:
mkdir -p /var/www/aegir/drupal-6.13/profiles/hostmaster/modules) - Download Hosting 0.3 RC3
Place it inside the newly created profiles/hostmaster/modules directory.
- Optional packages
These packages are not dependencies and can be skipped, but if they are present Aegir will take advantage of them to provide a better out of the box experience.
- Create the profiles/hostmaster/themes directory.
(example:
mkdir -p /var/www/aegir/drupal-6.13/profiles/hostmaster/themes) - Download Eldir 0.3 RC3 theme
Place it inside the newly created profiles/hostmaster/themes directory.
- Download Admin Menu 1.5 module
Place it inside the profiles/hostmaster/modules directory.
- Create the profiles/hostmaster/themes directory.
- Create a new database for the site, and create a new virtual host entry for it
This should be the last time you need to do this.
- Install a new site using the HostMaster install profile in sites/default
You will be directed along the server configuration process, and importing your sites.
- Download the Drupal 6.13 release
Upgrading Aegir
If you are a user of the previous 0.3 releases, replace the old packages with the newer releases of the main components (hostmaster, hosting, provision and eldir) and run update.php or drush updatedb
If you are a user of the 0.2 release, you can find complete upgrade documentation in the UPGRADE.txt file of the hostmaster profile.
If you have any problems, don't hesitate to contact us, by either making a support issue on the hostmaster project, or getting a hold of us on irc. We are trying to make the project as easy as possible to install, but we simply can't test every configuration possible. At the very least we would be able to provide more adequate documentation for such cases, so please let us know. Before submitting your request, make sure you have read the bug submission guidelines


Thanks for the release maybe you should add that
One need the "profile api module" (http://drupal.org/project/install_profile_api) and NOT download it with drush that will put it in the wrong "site/all/modules" place. One should put it directly into the "drupalxx/profiles/hostmater/modules" place.
I think you should remove the
sentence that seems really misleading now, since the install.txt still concerns the 0.2 release. for instance this text recommend using drush to download some modules witch will put them in the wrong place, it recommends to install aegir in another directory than the site/default one and several other things that could be confusing.
Just expanding by copy/pasting from the install.txt the virtual host creation and initial database setup would make this a clean install.
(linking to the requirements and fact would make that a complete up to date documentation)
(And using /var/www/aegir as the root is a great idea, since I did the same ;) )
thanks a lot for your time
errors in INSTALL.txt are RC bugs
Hi,
If there is an error in INSTALL.txt, it's a bug that should be filed in the hostmaster project as a critical issue. INSTALL.txt is supposed to be in sync with the code.
(As for using /var/www/aegir, I think it's a bad idea as by default /var/www is available to the webserver so that will expose private information like backups).
I agree,
using /var/www/aegir is a bad idea and it's also not compatible with some VPS setups where you have fixed and small partition for standard OS, while all added data space (disks) is mounted separately (see Gandi.net cloud hosting for example).
To avoid all above problems and to have compatible Aegir installs in every datacenter used (now we are using four), I prefer something like
/aegir/www:mkdir /aegirln -s /real/mounted/disk/space /aegir/www
~Grace -- Turnkey Drupal Hosting on Steroids -- http://omega8.cc
install_profile_api is required
In the "Installing Hostmaster and Hosting" section, it should include a step to install the install_profile_api module - which is now required to use aegir. For those wondering where to grab it - you can download it from drupal.org
Other than that (and a bug), the above steps have worked a treat for me.
There is a ticket for
There is a ticket for discussion of the INSTALL.txt and documentation issues here, thanks Annakan
rc3 rather broken
So it seems the dependency on install_profile_api broke quite a few things and clean rc3 installs are not working very well. People wanting to test Aegir from scratch are encouraged to try our rc2 instead or use HEAD while we roll out rc4.