Aegir
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.
Setup
Usage
- Aegir usage (to sort)
- Dev provision
Workflow guides
- 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)
Drush
- Drush - issues
- Drush.ws
- example.aliases.drushrc.php Drush context alias example
Drush Make
- Drush Make readme
- Drush Make theory for happy profile development
- Using drush_make to optimize workflow - Basics of make/profile management from mig5's first article
Provision
Distros and provision
Example make files
Profiles
- Developing installation profiles
- Install Profile Packaging
- Packaging a profile on drupal.org (make file -> install profile)
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]
- System variables (D6)