Why you should be using Aegir: The Drupal-oriented hosting system
•Als PPT, PDF herunterladen•
3 gefällt mir•4,272 views
Aegir is a hosting management system and control panel that allows easy installation, maintenance, and deployment of Drupal sites. It streamlines tasks like creating new sites, managing platforms with updated versions of Drupal core and modules, and migrating sites between environments. Using Aegir avoids the need to request assistance from system administrators for common site management tasks and allows developers to focus on Drupal development rather than system administration.
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Why you should be using Aegir: The Drupal-oriented hosting system
Ähnlich wie Why you should be using Aegir: The Drupal-oriented hosting system (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Why you should be using Aegir: The Drupal-oriented hosting system
- 1. Why you should be using Aegir Seth Viebrock - Origin Eight
- 2. Ægenda • Intro to Aegir • Installing Aegir • Aegir in the workplace • Using Aegir • Aegir platform maintenance • Aegir deployment
- 4. Intro to Aegir • What is Aegir? • Who is using Aegir? • Why use Aegir?
- 6. •A Hosting Management System (HMS) •A Control Panel •A Drupal platform management tool •A site deployment tool
- 7. Who is using Aegir?
- 8. • Individual developers • Web development companies • Universities • Hosting companies
- 10. • Only takes minutes to install Aegir itself! • Easy site spin-up • Easy platform management • Allows you to focus on Drupal over sysadmin
- 11. Installing Aegir
- 12. Installing Aegir • Where to install Aegir • Installation demo • Securing your server
- 13. Where to install Aegir
- 14. • A VPS or dedicated server with root access • A Virtual Machine on your own computer • Check out the “aegir-up” project, or at least Vagrant. • Don’t install on a machine that is already flushed out.
- 16. Prerequisites • Basic command line skills • The ability to type “apt-get” and copy-paste instructions. • Basic UNIX text editor skills (i.e. vim, emacs, nano, pico, etc) • For production use: Ability to handle basic server maintenance and security, or the ability to pay someone to do it for you. • Willingness to let go, and do things The Aegir Way.
- 17. • Thisdemo uses the the “Automatic install on Debian” approach outlined at http://community.aegirproject.org/node/400 • Uses a Debian 6 install on a Linode (linode.com)
- 18. Versus a manual install
- 19. Linode install
- 21. Aegir install
- 26. Linode install
- 28. • Install it on a bare server or VPS • Keep Aegir up to date • Follow basic security measures for your particular server, i.e. http://www.thefanclub.co.za/how-to/how-secure-ubu
- 29. Aegir IN The workplace
- 30. • Do you have to make a request to a sysadmin just to get a new dev site set up? • Do you have a hackneyed or nonexistent process for upgrading Drupal core and performing security updates? • Do you have to ask someone to find out where any given site is hosted? • Arepermissions on your files and folders unpredictable?
- 31. Using aegir
- 32. Basic workflow 1. Create a platform (say, Drupal 7.14) 2. Create one or many sites in the platform. Clone a site if you wish! 3. Createanother platform (say, with security updates in place, i.e. Drupal 7.18) 4. Migrate a site on another platform to the new platform. 5. Repeat
- 33. OTHER workflow 1. Add SSL certs via the Aegir UI. 2. Delete sites. Disable sites. Backup sites. 3.Optional: drush sql-drop -y && drush sqlc < some-other- database.sql
- 34. HMS 1. Sites, tasks, platforms are “content” (nodes) in Aegir. 2. Content is mapped to configuration on the filesystem. 3. drushrc files
- 35. interesting use cases • Create throw-away experimental sites in seconds. • Want to try a new distribution? i.e. Panopoly? Just download it, point a new Aegir platform at it, and create a site in that platform with a path to the .make file. • If you have developers, just give them access! You can restrict access perms as needed. Let them spin up sites. Don’t make them ask and wait for sysadmins! • Use it to provision dev environments for developers, in the case where each dev instance has its own database.
- 36. • I’ll give a quick look at the UI. (Live demo!) • Does anyone have any questions on how to do something specific?
- 37. Eccentricities • Can’t install a new site on a custom platform a client handed over to you? Just install a site on your own platform and migrate to this platform. • The aegir UNIX user owns all the code, and the www-data user owns the files. We’ve found that individual developer user accounts should be placed in the www-data and aegir groups to avoid permissions issues and allow access to modify the code.
- 39. • Live demo!
- 40. Aegir Deployment
- 41. • Ifyou have a really beefy server, especially one that can scale on demand, and/or you have very few sites to manage, dev/integration/staging/production could technically be on the same server. • Recommend having separate server for dev and integration, and a separate server for staging and production. • Can only deploy the first release of a site (i.e. the first release from dev/integration to production).
- 42. Why should you be using aegir?
- 43. • Aegir is awesome! And free! And extensible! • Aegir as a SaaS business model. • It helps ease awkward tasks: • platform maintenance and security upgrades • site installation and multisite architecture • These awkward tasks are pain points for many users that might prevent them from using Drupal. • Aegir and Drupal are symbiotic.
Hinweis der Redaktion
- * I call it an HMS, because, really, it is a CMS/CMF (Drupal) that provides an interface to managing a hosting environment. * Doesn’t necessarily play well with other control panels b/c it has to take control of the server. So, Aegir runs best on a bare-bones server. * Upgrade a site between versions of Drupal, facilitates a multisite architecture with many sites living on the same “platform.” * Not code deployment. Can also migrate sites between servers.
- * Easy and fast to spin up a test site, try out a new distribution, etc, on your own local or remote machine. * Origin Eight. Individual dev instances managed by Aegir. dev -> int -> stage -> prod. * George Washington Uni, U of Oregon, Ohio State University, College of Arts and Sciences. * Koumbit and omega8.cc. omega8.cc uses Nginx, advanced caching that they upgrade somewhat often, and gives you a restricted admin interface so you don’t screw up your Aegir instance. I personally prefer full access and extensibility. Also, those who have a lot of experience with caching can appreciate the uncertainty/unpredictability that comes with the benefits it can provide. And, when a module is developed on Apache, as most are, it’s not guaranteed to work on Nginx. Either way, different scenarios / hosting options can be better or worse for different use cases.
- * Aegir is running on Drupal core, so any anonymous user attack vulnerabilities will apply, and possibly
- * * Not recommended to install on your own computer directly, although you probably can. * i.e. has lots of control panels, or does not have root access (i.e. shared hosting)
- There are other options, such as Rackspace, or anyone who gives you a really basic/clean install of an OS.
- There are other options, such as Rackspace, or anyone who gives you a really basic/clean install of an OS.
- These are notes from a coworker in 2011.
- Note: On Debian 6.0 I should have set the “pin priority” for drush to a later version, as shown here, so that I could grab the later version of drush (4.x) necessary for the install.
- * Aegir is running on Drupal core, so any anonymous user attack vulnerabilities will apply, and possibly
- * Aegir can alleviate this! * Aegir can help! * Aegir can give you a list of all of your sites on the current server. * Aegir fixes this for you!
- * * * i.e. doing a dev database refresh from integration or production.
- * * * i.e. when deleting a site, check out drushrc files
- * * drupal.org/project/panopoly * If for some reason the .make file fails, just migrate a site to that platform, blow away the database (drush sql-drop -y), and reinstall the site via a browser. * One problem can be telling developers where a site is located on the filesystem.
- * * Possibly both a separate staging and prod should have their own server in some cases, i.e. if you are doing load testing, you should do it on staging with all performance measures in place rather than production. * Koumbit did some work on the module to allow remote import among servers.
- * http://drupal.org/project/hosting_varnish , http://drupal.org/project/provision_civic rm , http://drupal.org/project/provision_boo st , http://drupal.org/project/devshop , http:/ /drupal.org/project/remote_import , http:/ /drupal.org/project/provision_newrelic , htt p://drupal.org/project/hosting_so lr * http://community.openatria.co m/team/saas-business-model * * * Start learning Aegir so you can contribute bac k to it!