Aegir hosting system
Ægir is a set of modules for Drupal that helps you maintain several 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.
In Norse mythology, Ægir was the god of the oceans and if Drupal is a drop of water, Ægir is the deity of large bodies of water.
More information is available on the overview wiki Entry
Quick links
AEgir is made of multiple Drupal projects and modules, be sure to check those out!
Aegir meeting schedule
All meetings take place on : #aegir on irc.freenode.net
- Weekly development meeting : Fridays at 16:00GMT
- Daily scrum sessions : Monday through Friday at 16:00GMT
As a project we find it useful to meet regularly to discuss current progress and future goals. Due to the geographically dispersed nature of the team, it is impossible to meet at a time that would work for everyone, and as such you will probably find people in the IRC channel at most times.
Aegir 0.3 release candidate 1
We're proud to announce the first 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 first release candidate of our 0.3 release. The primary focus of this release is porting the existing 0.2 release to Drupal 6. We had originally planned to also number this release 0.2, but to simplify support we have opted to give this release it's own version number.
Due to the nature of this release, it is already feature complete and only bug fixes will be accepted.
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 + ISPConfig
Hi,
Aegir looks great beyond belief and I am seriously keen to try it out. However, I run ISPConfig on my server and I think the two will clash. Any thoughts/suggestions?
Cheers.
heebie
Herramientas para administrar sitios en Drupal (Drush y Aegir)
El texto de la charla Herramientas para administrar sitios en Drupal (Drush y Aegir) presentada en el Drupalcamp de Buenos Aires el pasado Junio 25, 2009 se encuentra disponible en esta serie de tres articulos:
Saludos
Tell Us How Drush Has Made Your Life Easier and Get a Free Shirt
To celebrate the launch of Drush 2.0, we’re handing out several I <3 Drush t-shirts.
If you want a shirt, what you need to do is make a screencast or blog post about how Drush has made your life easier. Show or explain how you used to do something manually, and how it’s much quicker and simpler with Drush. Once you’ve posted about Drush, tweet about it with the #drushrush tag, and we’ll select the top three posts and those authors will receive a t-shirts in the mail.
So start posting and happy drush’ing. Oh yeah, you can also buy the shirt over here but what fun is that.
Can Drush make communication between Ægir Drupal sites, possible?
I need to create several sites that can communicate with each other in a twitter like manner. Has anyone done this before, if yes how? I can bypass this problem by using a third party webapp, but I don't want to this if I can use Drupal!
I would like to create an Ægir "site group" and let all members of this group be able to communicate with each other.
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.
Drush 2.0 is out , Aegir 0.2 release is imminent
This has been the major blocker for our 0.2 release, which will happen very very soon.
Using Aegir
(i'm trying to make some documentation of using drush & aegir, please give me some feedback)
Start with watching the screencasts:
Installing Aegir from scratch & Aegir in action
Migrating sites to aegir
- aegir doesn't import sites/default
- mv sites/default sites/actualdomain.com
- leave a symlink to sites/default in place
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.