The Aegir hosting system allows developers and site administrators to automate many of the common tasks associated with deploying and managing Drupal websites. Aegir makes it easy to install, upgrade, deploy, and backup an entire network of Drupal sites.
Although it's great for managing large numbers of sites, it can also be useful for smaller environments.
In this presentation, we'll cover how Aegir models:
- and Servers
How you can use Aegir to (individually or in bulk):
- Upgrade sites.
- Clone sites
- Backup sites
- Importing sites
As time allows, we'll get into installation, best practices, strategies, and gotchas.
- High level installation
- Makefiles for platforms
- Domain vs subdirectory sites
- Multi-server vs single server
- Install profiles vs site specific code
- Interactive install profiles
- Security considerations
- Nasty bugs & project updates
- Callouts to other cool Aegir things (pack, wedful, koumbit omega8cc, mig5's jenkins setup)
At OSU Engineering, we've been using Aegir in a multi-server environment for around 18 months. We currently have over 100 sites in our deployment and have written a couple of Aegir add-ons. For us, using Aegir resulted in an order of magnitude reduction in time and complexity of our upgrade/maintenance processes.