provision
Working provision to integrate with plesk(or generically any web hosting control panel with some api)
i dont want to reopen this issue of aegir installed alongside web hosting control panels but i have some potential work lined up with a clients migration to new servers and from another cms to drupal for running there cms hosting service.
as a touch of background they have got a shell script that works with plesk api's to be able to create plesk accounts with home directories which get symlinks in the drupal code base sites directory - eg /drupal/sites/domaina.com is actually a symlink to /sites/domaina.com which is the plesk accounts home folder in normal circumstances
Problems with Provision Verify on CentOS 5.3
When running drush.php provision verify, it seems provision is unable to find the master_db_host, master_db_user and master_db_passwd, resulting in an error: Could not connect to the master database. An error occurred at function : drush_provision_mysql_provision_verify_validate. If I pass the three options to the verify command as arguments, (eg. drush.php provision verify --master_db_host=localhost --master_db_user=user --master_db_passwd=passwd), provision verify works, and proceeds to creating the drushrc.php file, with NULL values for master_url and master_db.
Aegir 0.2 released.
We're proud to announce the final 0.2 release 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 release is the final release of our 0.2 development cycle, which has been focused on complete support for running multiple concurrent Drupal releases, and managing upgrades of sites between Drupal releases. The only changes from the release candidate were some miscellaneous bug fixes and bringing the system in line with the Drush 2.0 final release.
Aegir presentation at the Washington DC Drupal User Group meetup tonight
I’m working out of Development Seed’s main office here in Washington, DC for a few weeks, which gives me the opportunity to show off some of the cool stuff we’ve been working on at the Drupal Meetup tonight at Stetsons. I’ll talk about Aegir, a hosting system that streamlines deploying and upgrading multiple Drupal sites, and show its support of installation profiles and multiple languages.
Aegir 0.2 release candidate 1 released.
We're proud to announce the first release candidate of the 0.2 release 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 release is the first release candidate of our 0.2 development cycle, which has been focused on complete support for running multiple concurrent Drupal releases, and managing upgrades of sites between Drupal releases. This release has been focussed on improving some our experimental multi-client functionality, as well as fixing bugs for our final release.
Aegir is in code freeze, and only bug fixes and usability improvements will be allowed in. The final release of Aegir will occur shortly after the 2.0 final release of Drush, and we will only be making changes to Aegir to maintain compatibility with Drush upstream.
Aegir 0.2 beta 1 released.
We're proud to announce the first beta of the 0.2 release 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 release is the first beta release of our 0.2 development cycle, which has been focused on complete support for running multiple concurrent Drupal releases, and managing upgrades of sites between Drupal releases. This release has also primarily been focussed on fixing bugs and polishing the final release of the 0.2 release.
Progress Update: We've decided to fast track the 0.2 release
Me and antoine were discussing, and we're at a point where we REALLY have to look to find bugs in the alpha. We feel that the new features are more than adequate to make a proper release, so we've decided to basically go into a pseudo feature freeze.
We're going to look into adding http://drupal.org/node/371769 and possibly http://drupal.org/node/337485 still, but out main objective is to get a drush 2.x final release out as soon as humanly possible (it's the only real thing blocking release at the moment)
Aegir 0.2 ALPHA 1 released.
We're proud to announce the first alpha of the 0.2 release 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 release is the first alpha release of our 0.2 development cycle, which has been focused on complete support for running multiple concurrent Drupal releases, and managing upgrades of sites between Drupal releases. This release has also primarily been focussed on improving and simplifying the back end system, by incorporating a lot of our custom API's upstream into the Drush 2.x project.
Update: Check out this screencast for a quick walkthrough of the features available in this release.
Drupal 'ports' collection
What is it?
My recent work on Aegir has been very deeply oriented with Drupal package management and dependency checking.
From the perspective I have been working from (unix command line scripts), the currently existing functionality of the update module is simply not useful.
I am in need of an easily mirrorable meta-info repository of all the drupal projects, and all the drupal modules. I need to be able to figure out dependencies
Progress update: Package management and dependency checking
Progress towards our main development goals.
Drush stuff
Last week I completed what is basically a major rewrite of Drush, save the actual command files. Everything is a lot more sensible and normalized now. This also led to me massively refactoring Provision (our drush based back end) to make use of these new API's. I wrote up a small post about what's been happening with Drush for those that want more in depth information.
The major thing that is coming out of Drush becoming more like Provision every day, is that the drush_extras project is being re-integrated into Drush itself, using the provision conditional include API for the Drupal version specific code. Once that is done, we will be migrating Drupal install and update commands upstream to provision, which provide a much larger user base for the code, getting it far more testing. It will also significantly reduce the size of provision, and make it easier to maintain and will hopefully become the standard way that 'real' Drupal developers run update.php on their sites.
Because we are so deeply involved in Drush now, we are also tied to their release cycle. We are at a point where we want to release an alpha, but moshe has decided to re-integrate Drush_extras first, which should take about as long as it would to have gotten each version of drush_extras ready for an alpha too.
Enabled packages on a site
Aegir stuff
I haven't been resting on my laurels though, I've been tackling many of our critical issues (take a look at how good our issue queue is looking). I have been continuing in my crusade to make the Aegir project easier to build and maintain.
In the last week I finally nailed down the biggest issue that was holding us off on an alpha, namely the package management features. With drush 1.x we could rely on each platform being a site, to have access to the database, unfortunately with 0.2 that isn't possible anymore, so I wrote some routines that index entire Drupal platforms and find all the modules, themes etc for the whole platform, all the profiles and each of the sites, which I then import on the front end to build relationships between the package entities and the sites etc.
This now allows us to do some dependency checking, which we sorely needed. Previously it would let you attempt to migrate any site to any platform, no matter of the version.
This is much nicer. Imagine how great it will be once we have spaces, context and features properly playing along with all this stuff. You'll be able to roll out new features incredibly easily, and seeing that you can extract features with Drush, we can automate that too.
Package compatibility between platforms
As you can see, we're already very close to an alpha, so we're going to be working towards that along with the Drush guys. After the alpha there's going to be another phase of refactoring going on, as we'll have solved all our major issues for the release, and now it's time to make sure the codebase is up to scratch. We're also going to take some time and get some of the contrib modules playing nicely with 0.2, so that will take some time too.
I have also spent a few hours today on the community side of things, mostly fixing up the groups.drupal.org page. It looks way better now, and displays the release status proudly (keeps us honest, heh).
We'll be continuing forward in the next week or two on both the Aegir and Drush projects, and we'll probably have more announcements soon.
