Aegir

From Things and Stuff Wiki
Jump to navigation Jump to search


System/process overview

Aegir uses Drupal multisite features to share one Drupal codebase install as a 'platform' between sites. Distributions are equal to platform+site, i.e., turnkey solutions. Content can be shared (migrated) between sites using an updated or different platform (with the same content modules, natch). A platform and site distribution is created from a .make and .info using Drush Make. 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.

Barracuda box setup

Octopus

Like Barracuda, but a satellite Aegir instance with pressflow and other distros.

Aegir usage

Dev/production workflow guides

Drush

Drush Make

Provision

Distros and provision

Example make files

Profiles

Profiler library

Features and settings

See also: Features

  • Strongarm gives site builders a way to override the default variable values that Drupal core and contributed modules ship with. [1]
  • Global variables

Misc tools