Aegir One Drupal to Rule Them All

503 views

Published on

The Aegir hosting system allows developers and site administrators to automate many of the common tasks associated with deploying and managing large websites. Aegir makes it easy to install, upgrade, deploy, and backup an entire network of Drupal sites.

Published in: Technology
  • Be the first to comment

Aegir One Drupal to Rule Them All

  1. 1. One Drupal To Rule Them All
  2. 2. Who am I? • Gareth Hall • Communica (http://communica.co.nz) • Freelancer / Contractor
  3. 3. Why do I need Aegir?
  4. 4. Running Drupal is hard and complicated
  5. 5. We got Drupal • It awesome and great. • But now we need a way to share a common code base. • Why have 50 sites and all of them have their own copy of views, token, ctools, admin, wysiwyg ...
  6. 6. Then came Multisite • Shared code base FTW! • But doing common tasks is hard. • Upgrading modules and core. • Different module versions. • It takes a long time to upgrade 50 sites.
  7. 7. Drush • Command line tool to Drupal! • Argh another thing to learn. • It’s command line only ... forget it! • Experience ... shit I broke something how do I fix it in command line.
  8. 8. What is Aegir? • Drupal Multisite + Drush + Steroids • It’s a Drupal front-end to manage common Drupal tasks like create, update and deploy. • Manages Apache • Manages MYSQL
  9. 9. Advantages • Automation • Roll back • Easy to use • Built on Drupal • Contributed modules • Multi server support
  10. 10. Disadvantages • Poor fail over • Built on Drupal 6 • Future road map • Drupal only so it not framework agnostic • Collaboration hard to do well • No resource allocation • No statistics • You need a server admin
  11. 11. The aegir framework • Hostmaster = Front end and is Drupal. • Provision = Back end and is Drush.
  12. 12. Terminology
  13. 13. WTF?
  14. 14. Platform • Shared code base. • It’s one multisite. • It’s the root of a Drupal site. • The Platform name should describes it’s intent. • Commerce, Basic Brochure, Ubercart 6
  15. 15. Site • It’s a site within a Platform. • It shares the code from the Platform. • Has it’s own database.
  16. 16. Task • Backend Drush operation that will or has run. • It’s node containing an audit trail of the operation. • Common tasks are: • Verify • Install • Migrate • Enable / Disable • Backup
  17. 17. Verify • Checklist of expected behaviour to confirm normal operation. • It checks that your site, platform or server is working.
  18. 18. Creating a platform • Create a Drush make file. • core = 7.x • api = 2 • projects[] = drupal • projects[ctools][subdir] = contrib • projects[token][subdir] = contrib • projects[views][subdir] = contrib • projects[webform][subdir] = contrib • projects[] = omega • libraries[ckeditor][download][type] = "get" • libraries[ckeditor][download][url] = "http://url/ckeditor_3.6.6.1.zip" • libraries[ckeditor][directory_name] = "ckeditor"
  19. 19. Upgrading a site • Never upgrade a platform • Create a new platform • Migrate site to new platform • Or migrate the whole platform
  20. 20. Remember to test! • Selenium • Selenium Webdriver (RC) • Codeception
  21. 21. Questions
  22. 22. DEMO

×