Progress update - nearing RC2 release, HEAD (0.2) no longer needs a bootstrapped platform.

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
adrian's picture

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.

One of the major issues we have found, was regarding the mysql users being created with the wildcard as the host. A lot of distributions provided a default catch-all that disallowed that permission structure, so we have reverted to both creating a local mysql account and a remote one. People using an external database server will require a small amount of additional configuration, but aegir will work out of the box again. So if you ran into database permission issues with RC1 (http://drupal.org/node/354050), RC2 will probably resolve that.

More exciting news is that Provision HEAD (our gestating 0.2 release) is now nearly in synch with Drupal 6 - 0.1, with the major difference being that as 0.2 is based on Drush 2.x, you no longer need to install a full drupal site for it to act as a platform, with multiple copies of the files.

The only thing outstanding for feature parity with 0.1 is http://drupal.org/node/368294, so the package handling in the front end is not completely right.

Next on the 0.2 bandwagon is moving provision_drupal into it's own drupal project, and figuring out a way to download the right provision_drupal version for the specific drupal release you are interacting with. This also opens the door to a provision_joomla or provision_wordpress module.

Pretty soon we will be able to provide a command line based install script for the whole system, so it's exciting times.

To install :
1) download the latest drush HEAD (through cvs), and place it in your path.
2) download the latest provision HEAD (through cvs) and place it in ~/.drush
3) download a new drupal by doing : 'drush.php dl drupal'
4) cd drupal; drush.php provision setup.
5) add the path as a platform in hosting. (optional)

Comments

And in 2009...

Boris Mann's picture

...AegirNET became self-aware, and started downloading copies of itself.

Nice work Adrian and crew!

robin.puga's picture

Just installed RC1 last week on a Bryght VPS for a client. Stoked to upgrade to RC2 soon.

Boris, hehehe, you kill me. :P

~ Robin

Full install instructions

physicsdude's picture

Sounds great! Are those the full install instructions? The last step 'add the path as a platform in hosting' seems to imply that first I need to install the hostmaster component first??

This is to deploy new platforms automatically

anarcat's picture

The idea is to use drush + provision to deploy new platforms automatically. I have been able to install a platform with those commands. Before that, in 0.1, to install a new "platform", you had to actually install a drupal: uncompress a tarball, create a database and user, go clikety your way through the drupal install wizard and only then create your platform node.

Now, just with those few shell commands, you can create a new platform:

cvs -d :pserver:anarcat@cvs.drupal.org:/cvs/drupal-contrib co -d drush contributions/modules/drush
mkdir .drush
cd .drush
cvs -d :pserver:anarcat@cvs.drupal.org:/cvs/drupal-contrib co -d provision contributions/modules/provision
cd ..
./drush/drush.php dl drupal
cd drupal-6.9/
~/drush/drush.php provision setup

... and the idea behind that change is that now provision can provision itself. The system is becoming self-provisionnable, ie. we will see the day where you don't even have to do those command yourself and Aegir will do it for you.

So in short, no, those are not full install instructions, for that you still want the wiki, which will need to be updated with those instructions before 0.2 comes out.

Aegir hosting system

Group organizers

Group categories

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week