Discussion

I have been feeling the pain of using wamp for my testing server (im on vista). Mainly I cant get drush to work and cygwin really sucks! I have recently gotten into vmware and have been testing out different LAMP virtual appliances. Im guessing this will be the best setup for a test environ but I've yet to find just the right lamp rig.

One of the major changes to Aegir for the 0.2 release, is integrating with Drush 2.x.

What this comes down to is that, like Drush, Provision has ceased being a 'module' in the traditional sense.
Each server that Aegir manages will now need to have one instance of Drush, and one instance of Provision.

This resulted in some refactoring in the Hosting module, as it was depending on Provision being available as a module for a number of things.

One of the other things that I added to the code in HEAD, once the refactoring had taken place, is the ability to call instances of Drush and Provision on remote servers. This means that you can now install, enable, disable, delete, backup, roll back , and upgrade Drupal sites on multiple servers, that are managed by Aegir.

New hostmaster installs are currently broken on 0.2/HEAD since the hosting module (and hostmaster.profile) expects provision to be installed alongside it in the platform, which is no longer a requirement. This issue tracks that particular problem. We have to port hosting to that new paradigm before 0.2 can be installed from scratch again.

We're currently experiencing a bit of a roadmap issue. I spent a few hours running hosting through the absolutely amazing Deadwood module. I've updated the ticket for this issue

One of the major goals of this project is to keep it easy to maintain, which in many cases means not biting off more than we can chew,
but it also means avoiding hacks and non-standard code as much as possible.

We're proud to announce the first release of the Aegir hosting system for Drupal.

Ægir is a new 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 release is feature complete with the main roadmap of Aegir. It will allow you to install, back up, restore, enable, disable and delete your hosted sites. We were originally considering releasing an extra release candidate to make sure the first release was really rock solid, but since 0.2 (HEAD) progressed so quickly, we are now shortening the release cycle. We therefore want to shorten the release cycle to get more features out and favour greater adoption.

Just a quick note to let everyone know that we're very close to releasing RC2. We're just putting a last bit of polish on the permissions system.

As our 0.1 release is nearing, I have been making some steps toward our 0.2 release. The onus for this progress has been some really exciting changes happening upstream in the Drush project.

Our 0.1 release was originally only going to manage a Drupal platform, with no support for hosting sites on Drupal 6. As the project wore on, we realized we needed to become invested in Drupal 6 very quickly, so we ported only the back end to Drupal 6, and have been maintaining the releases in parallel.

Living in sin with Drush 1.x