Documentation

Aegir install on OSX Snow Leopard

Aegir install instructions are fantastic if you run Debian/Ubuntu Linux. Some of the steps for OS X are a quite different

I've attached some more detailed instructions on how to install Aegir on CentOS.

The instructions may not be 100% perfect, but I'm due to install Aegir on CentOS again next week, which should given me an opportunity to fine-tune the instructions further.

I've had no trouble setting up a multi-webserver setup as well. If you're trying it yourself and get stuck, ping me on IRC (resonancedev in #aegir) or post a comment.

This page, like all our documentation, is a Wiki - please feel free to add and edit.

The Aegir project is growing rapidly, and more and more people are installing and testing the code. Many users ask about how to help out and give something back to the project - so that's what this page is about.

Finding and Reporting Bugs

So you've found a bug? Although bugs obviously aren't good, in a complex project like this they're bound to exist - so it's brilliant you found it. Now we'd really like your assistance to help us fix it.

Here's how:

This page is just intended to be for the development team to make notes about needed documentation for the project. It's a scratchpad for notes, thoughts etc.

Existing Documentation to revise (perhaps because the code has changed):

Features Yet to be documented:

Troubleshooter tips to write up:

FAQs to write up:

In some situations you may wish to allow different people access to Aegir, but restrict which sites they can manage.

• Use Case 1:

  As a developer you may simply wish to segregate your sites in Aegir by different clients for your own internal management reasons.

• Use Case 2:

  If you have many staff working on different projects, you may wish to issue them with different logins and restrict which sites they can access on the Aegir system.

• Use Case 3:

So we have started using Git to work on aegir. We would gladly completely move away from CVS, but since Drupal.org does not yet support anything else, we will still have to sync the CVS tree with our git repositories. This describes the workflow I use.

There may come a time when you want to remove a website from your Aegir powered server. As you'd expect, Aegir handles this for you too. It'll even clean up after the site properly

But resist the first temptation of someone used to working with Drupal's nodes - don't go to the site's node, select the edit tab and press the 'delete' button! (in coming releases of Aegir this is to be made clearer).

Here's the proper way to do it:

1. Disable the Site

The easiest way to install Aegir is by using the Shell Install Script that has been developed. Here are the steps to take

Setup the Server

Set up a brand new Linux server, to which you have shell access as the root user. You don't need to install Apache, MySQL or PHP or many of the other steps in Prepare your Server for Aegir - because the script does all of this. However, it doesn't matter if you already have these installed.

Get the Install Script

The manual installation instructions on this page assume that you have followed the steps in Preparing a Server for Aegir. You may need to change some elements of these instructions to fit your own servers setup.
You can also follow the instructions in the INSTALL.TXT file that is packaged with the Hostmaster installation profile.

Here's a manual procedure to migrate sites between servers. This can also be used to test upgrades without removing the original site.

Source webserver/platform

1. backup
   

   drush provision backup sourcesite.example.com

2. copy files over to the new server (skip this if just deploying on a local platform)
   

   scp ~aegir/backups/sourcesite.example.com-2009-07-31.tar.gz aegir@destsever.example.com:backups

Destination webserver/platform

1. go to the right platform
   
   cd /var/aegir/drupal-x.y