This session is best suited for Drupal users who have a working knowledge of Systems Administration. We will walk through a working tutorial on how to use Ansible to spin up Drupal staging servers on demand, so only a relatively basic understanding of Systems Administration is required to follow the session. We will publish this tutorial, and open source the code libraries we use to complete it, so users can do their own research after the session to put the work to good use.
You've done the hard yards and your latest Drupal site build has been pushed live. When the dust settles the project ticks over into the support and maintenance phase. Periodically you're going to need to apply Drupal updates and push minor new features and bug fixes to the live site. You're a professional so you always follow the 'Development -> Staging -> Live' release process. So, you leave a staging version of the site up and running so that you can test your work and demo it to clients before pushing to live. Thanks to the miracles of cloud computing it's easy enough to setup the staging server, but there's still enough legwork involved that it's more cost effective to leave the staging server running rather than destroying and rebuilding on demand. But...there's a cost to this aside from the small financial one which you pass on to the end client anyway, and that's the carbon footprint of the staging server itself.
Cloud computing accounts for a sizeable chunk of global carbon emissions. Imagine how much that could be reduced if we all ditched the idea of permanently retaining staging servers and created them on demand instead.
In this session we demo a working example of how to ‘flat pack’ your Drupal staging servers, so you can spin them up on demand in a matter of minutes. We’re open sourcing the code library we use to achieve this, and will publish the accompanying tutorial online, so come along and learn how you can turn off all your staging servers and help save the planet!