The Aegir Project has moved!
This Drupal group is no longer actively used.
To get involved and learn more about Aegir, you should go to our community site,
which also contains our official documentation section and the official discussion group.
Discussion
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.
Read more
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.
Read more
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
Read more
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
Read moreTell 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.
Read more
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.
Read moreAegir 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.
Read moreDrush 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.
Read moreUsing 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.
Read moreÆgir plattform predefined custom Drupal 6.12 templates
Hi!
Because of the great documentation in the Ægir hosting system, I was able to get my own running copy of Ægir 0.2rc1! I love the power and the easy to use interface. Thank you so much for making this. You guys are geniuses!
My goal is to create a community site using Ægir Signup Form, that lets all my users communicate together and let them deign thei own homepages.
Is it possible to create a template of af a drupal 6.12 plattform? I wold like to change the layout, set predefined active modules, define user access and make an easy to use/understand admin UI.
File permissions
Here is the wiki page I've just updated - http://groups.drupal.org/node/12066 - Managing permissions on a shared Drupal hosting .
I've expanded the part about mpm-itk. Can somebody comment my contribution.
Thanks, guys. Cheers.
Read moreWhy is Aegir only on Drupal 5, what about a Drupal 6 version?
One of the most common questions that I get asked is why we are developing Aegir on Drupal 5. People who have been involved with the project for a while already know the answer, but I thought I'd post this executive summary.
Due to it's design, the Aegir system is fully capable of installing and managing Drupal 5, Drupal 6 and Drupal 7 sites, including managing upgrades of sites between all those versions. Only the front end (namely the hosting module, hostmaster install profile and now, the eldir theme) is Drupal 5 based.
Read moreAegir from scratch - Installing Aegir 0.2 RC1 screencast
Just to give this some more visibility, I have made a very thorough screencast showing how to install the newest release.
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.
Read more
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.
Read moreAegir (almost) self-upgradeable and possible 6.x support for the next 0.2 release
I have been able to upgrade Aegir with the provision module (that is, manually, on the commandline), but not with Aegir (that is, the hosting frontend) itself directly, because it's much trickier. Nevertheless, the problems impeding manual migration of the base Aegir platform are now behind us, which allows us to easily upgrade (say) the Drupal core behind the frontend. I have documented how in the UPGRADE.txt file.
This brings me to announce some of the IRC discussions we are having right now. We are seriously considering doing a release of 0.2 that will support both Drupal 5 and 6.
Read moreHow to Run 'hosting dispatch' Manually
The 'hosting setup' command you ran during Aegir installation
attempted to install a cron job which processes the tasks in Aegir's
task queue every minute. If you would prefer to run this command
manually here's how:
# replace /path/to/php with appropriate path
# e.g. /usr/bin/php
# replace /path/to/drush.php with appropriate path
# e.g. /usr/local/sbin/drush/drush.php
# replace /path/to/aegir/drupal with appropriate path
# e.g. /var/aegir/drupal-5.x
How to Create an Alias for Drush
On unix/linux this alias can be added to a user's .profile
# replace /path/to/drush with appropriate path
# e.g. /usr/local/sbin/drush/drush.php
alias drush='/usr/bin/php /path/to/drush.php'
