Documentation

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 switched to using Git to work on aegir.

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

WARNING: outdated instructions

those instructions are not the canonical install instructions and are outdated. You should follow the canonical instructions in INSTALL.txt from now on (which include the use of a more resilient, multiplatform and generic install script.

The rest of this document is kept for posterity.

Note that those instructions are DEPRECATED, see the new installation guide.

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.

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 (older versions of drush will be "drush provision 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

(PLEASE NOTE: This is a wiki page so you can edit it if you are logged into and part of the group.)

Aegir is a powerful system that sits on a LAMP server to create, deploy and manage Drupal sites. Once installed you can setup a drupal site in a few clicks - with Aegir setting up the apache config files and the MySQL database.

Aegir is in development, but is stable enough that many are already using the Release Candidates in production environments.

This documentation will tell you what you need to know to get Aegir setup and running.

So you've installed Aegir, arrived at the home page of your installation and are waiting for the magic to begin. On this page we'll show you some of the things you can do with Aegir and how easy it is to use.

1. Get to Know the Interface

Once you've successfully completed an Aegir installation, you'll be presented with the homepage, titled 'Hosted Sites'.

Creating a brand new website in Aegir is really really easy. This makes it so much more possible to quickly roll out a sandbox to test a module, a demo site for a client, or even a full team and project management portal with Open Atrium.

Here's how easy it is:

1. Create a New Website in Aegir

Under 'Create Content' select 'Site'. Enter the domain name for the new site ('example.com' rather than 'www.example.com').
Select the Platform you would like it to be installed on (this option doesn't appear if you haven't added other platforms as well as the one Aegir runs on).

One of the most powerful features of Aegir is the way it can help you to upgrade large numbers of websites. You might have dozens of sites hosted on a drupal 6.12 codebase for example - but then the 6.13 release comes out with vital security fixes. Previously you'd have to go to each site, back up the files and database, upload the new codebase, run update.php, check everything worked and then onto the next site.