Aegir

half-way through a big refactor. todo; move things from here to other places.

Aegir is a site management distribution.

• Aegir
• Aegir file system structure
• Aegir contexts

Overview

Aegir is a Drupal installation that uses the Hostmaster front-end to control the Provision module with its Drush integration. Aegir uses Drupal multisite features to share one Drupal codebase install as a Platform which multiple Sites can be hosted on. If you want to create a site for a particular Distro, you install the Distro as a Platform then create a Site on that Platform.

Content can be shared (migrated) between Sites using an updated or alternate platform with managed module dependance.

to refactor

The Profiler library is installed with the .make and uses a .info file to specify modules to be initialised, including site sections/etc. from the Features module plus configuration settings via the Strongarm module. Provision initialises a site on that platform and installs the platform+site in Aegir.

Features and theme are stored using Git, --working-copy can be used to build a dev site then content can be migrated from live for testing. Dev platform is perfected, then rebuilt as live without --working-copy.

todo; use hosting_site_git and working-copy patch

Dev/production workflow

• Drupal deployments & workflows with version control, drush_make, and Aegir (mig5, Oct 28 2009)
• Using drush hosting-import to auto-create your platform node (and other entities) (mig5, Jan 11 2011) - Updated workflow on Aegir mailing list
• From Zero to Distribution using Features, Profiler, and Drush Make (dimitri, March 9, 2011)

Provision

• http://drupal.org/project/provision

• Provision - the Aegir backend
• API reference
• purge option for platforms (--force)

php /var/aegir/drush/drush.php @hostmaster hosting-cron --debug

• Manage your Aegir system from the command-line

Hostmaster

• http://drupal.org/project/hostmaster

Creating a platform

Use a build make file to call the main make (possibly on-top of a base profile).

Creating a site

Things to remember for a site build:

• Don't forget full domain name!
• Create dev.* alias for BOA cache-busting

Importing a site

• http://community.aegirproject.org/content/importing-complete-drupal-platform
• http://community.aegirproject.org/content/importing-existing-aegir-backups

• remote_import - Drush extension that allows you to fetch remote sites from remote Aegir servers
  • http://drupal.org/project/hosting_remote_import hosting_remote_import] - module that provides a UI for remote_import

Clone sites

• http://community.aegirproject.org/node/24

Aegir provides an easy method of making entire copies of a site. This includes the actual site files, modules and so on, as well as a copy of the actual database. This feature is called 'Clone' in Aegir, because it is a method of duplicating a site with a new URL or 'site name'.

The feature is very closely linked to the Migrate feature because it is almost the same, except that rather than move the site, it leaves the existing site in place and just copies it to a new name. For this reason, enabling the Clone feature also enables the Migrate feature.

Migrating and updating platforms

• http://community.aegirproject.org/node/23

One of the most powerful features of Aegir is the way it can help you to upgrade large numbers of websites safely. For example, you may have dozens of sites hosted on a drupal 6.18 codebase. But suddenly the 6.19 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.

With Aegir you simply click a button in the frontend and it handles everything. This is called 'migrating' sites in Aegir terminology, because it might be used in more cases than simply upgrading the main codebase. For example you may have different 'platforms' with different mixes of contrib modules and themes and charge clients for tiers of 'basic', 'advanced' and 'gold' packages. When they choose to move from basic to advance, you simply migrate their site.

• http://community.aegirproject.org/migration-tips

• Migrate sites from one Aegir to another (Apache)

Aegir contrib

• http://community.aegirproject.org/contrib-modules

• http://community.aegirproject.org/node/75

Access

• https://github.com/computerminds/aegir_http_basic

• http://drupal.org/project/provisionacl - Drush module, granular shell access for users

Backups

• http://drupal.org/project/provision_reinstall
  • http://drupal.org/project/hosting_reinstall

• http://drupal.org/project/hosting_backup_gc - allows you to specify how long Aegir should retain backups for

Migration between Aegirs

• Remote import - Provision, Remote import - Hostmaster - Drush extension allows you to fetch remote sites from remote Aegir servers.

Managing workflow

• http://drupal.org/project/hosting_queue_runner - tasks are run as soon as possible instead of waiting for a cron run. This makes Aegir appear much more responsive. [1]

• https://github.com/computerminds/aegir_make_working_copy - provides git working copy option un hostmaster gui for dev sites. - broken [2]

• http://drupal.org/project/hosting_site_git - hostmaster+provision
• http://drupal.org/project/provision_git - backend only

• Hosting Features - provides a Task to Hostmaster that provides integration with a site's Features. It is currently in development but works for the most important task: Update & Commit Features

• http://drupal.org/project/devshop_provision
• http://drupal.org/project/devshop_hosting

Stack

Relating to installing Aegir on bare servers.

See: BOA - 'Barracuda, Octopus, Aegir' bash install script.

Also;

• http://drupal.org/project/puppet-aegir
• http://drupal.org/project/puppet-drush
• https://redmine.koumbit.net/projects/puppet-apt
• https://labs.riseup.net/code/projects/shared-common
• https://github.com/Vertice/puppet-aegir

Scripting

See the API links above, see also fimafeng, my older bash provision script for Aegir/Drush.