provision

The Aegir project would like to present our 0.4 alpha 13 release. This release is primarily a bug fix release, fixing the site imports which have been causing issues with alpha 12.

New in this release is the ability to specify a makefile when you create a platform, which can be either a file on the hostmaster filesystem or a URL. Aegir will automatically build the platform from the specified makefile when it attempts to verify the path, and detects that it is not there.

Features:
#373062 : 0.4 - automate platform creation

We are proud to announce the 0.4 Alpha 11 release of the Aegir Hosting System. The previous alpha release did not provide a suitable upgrade path for users who were already running alpha 9 and later. The only addition is the relevant fix to allow these users to safely upgrade their systems.

As before, this release requires you to use Drush 3.3.

We are proud to announce the 0.4 Alpha 10 release of the Aegir Hosting System. This release contains several important bugfixes found in alpha 9. There were also a number of problems found in Drush 3.1 and Drush 3.2, which required a release of Drush 3.3 to be made to support this release.

#874716 : Loss of files directory on remote web servers on migrate/clone
#874794 : Wrong command for granting aegir shell on remote server in INSTALL.txt

alpha6, drupal 6.15

Just upgraded, had to modify aegir.make to use drupal 6.15 and used vset to get verify to work

when attempting site migration, here is what i get:

Status: Failed
Executed: Tue, 04/13/2010 - 01:29
Execution time: 41 sec

Log message
Task starts processing
Running: /var/aegir/drush/drush.php --root='/var/aegir/atrium-1-0-beta3-1' provision-migrate 'intranet.mysite.ca' '/var/aegir/atrium-1-0-beta6' --backend
Drush bootstrap phase : _drush_bootstrap_drush()
Drush bootstrap phase : _drush_bootstrap_drupal_root()

I click on verification and get this:

Warning: include_once(./sites/aegir.example.com/settings.php) [function.include-once]: failed to open stream: Permission denied in /private/var/aegir/hostmaster-HEAD/includes/bootstrap.inc on line 322

It is set to 440
user: aegir
owner: aegir
group: _www (on a mac)

I am using hostmaster-HEAD btw.

I see that /var/aegir/config/vhost.d/aegir.example.com_80 is there and the variables are set

I changed the settings.php permissions to 444 and got:

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

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.

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.

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.

Read more

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.