This document discusses approaches for deploying Drupal websites from development to production environments. It covers considerations for initial site installation ("cold start") as well as ongoing updates. Simple setups can use basic scripts for deployment, but more complex enterprise sites require tools to manage multiple hosts, roles, environments and tasks. The document evaluates options like Webistrano, DrushDeploy, Jenkins and Aegir and discusses related tools for automation, testing and continuous integration.

1. With One Click Marcus Deglos Principal Engineer - Capgemini@manarth

2. Can you make a build with ONE step?

3. Starting from square one Contract ✔ Business analysis ✔ Design and wireframes ✔ Ready to start coding – right?

4. Where do you start? Linux VM/WAMP/MAMP/XAMPP/manual install of apache, MySQL, PHP…? Create an empty repository Download latest Drupal to your checkout Start coding? Downloading contrib modules Click + configure Custom modules and themes?

5. Stop! Have you thought about… Environmental consistency? Deploying to live? Testing?

6. Two phases Cold start: installing from scratch Updating a live site

7. Cold start considerations Script everything. Tools include: drush drush make install profiles distributions (which typically use a complex install profile)

8. Start simple DB Web server Varnish

9. Deployment – what’s in a name? At its simplest, it’s:Move code from repo to server But there’s more… Switching symlinks Linking up file paths? Clearing caches Running update.php Post-deploy tasks: DB changes? Drush commands? Notify external systems?

10. Pushing codeIt’s all been done before FTP Manual deployment – SSH/rsync Bash script Rube goldberg machine Capistrano/Webistrano Ant/Phing Jenkins Aegir Drush Git commands RPM packages

11. Simple tools for simple problems With a simple setup – a single host, or a separate db and web server – a simple deployment tool may be enough.

12. A simple deployment script #!/bin/bash # Version to deploy version=release-1.0 # SVN source of tags. Presume that credentials are already cached. svn=https://svn.example.com/my_web_site/tags # Docroot is a symlink to the current checkout. docroot=/var/www/current # Folder which contains each checkout. destination_folder=/var/www/ # Checkout to a timestamped folder (format: YYYYMMDD-HHMM) timestamp=`date +%Y%m%d-%H%M` destination=$destination_folder/$timestamp svntag=$svn/$version svn co $svntag $destination # Switch symlink. rm -f $docroot ln -s $destination $docroot # Clear caches with Drush. drush -l $docroot cc all Slides will be on slideshare.

13. Enterprise sites: simple HA Proxy HA Proxy Varnish Varnish Web Web DB (master) DB (slave)

14. Enterprise sites: complex+ HA Proxy HA Proxy Varnish Varnish Web Web Memcache SOLR DB (master) DB (slave) NAS/SAN

15. Enterprise sites: complex++ HA Proxy HA Proxy Zeus Zeus Varnish Varnish Web Web Memcache LDAP SOLR ESB DB (master) DB (slave) NAS/SAN

16. Why is this complex to deploy? Multiple hosts Multiple roles Different actions for different roles

17. Managing this with a bash script will drive you insane

19. Reverse proxy

20. Network management

21. Data cache

22. Database

28. Restart memcacheTasks / Recipes Actions Roles

29. Pushing codeIt’s all been done before FTP Manual deployment – SSH/rsync Bash script Rube goldberg machine Capistrano/Webistrano Ant/Phing Jenkins Aegir Drush Git commands RPM packages

30. Rube Goldberg deployment

31. Webistrano

32. Webistrano: under the hood(live demo)

33. Alternatives

34. Alternatives to Webistrano Wednesday 12:30“Aegir: One Drupal to Rule Them All!” Wednesday 15:00“dog: A New Era for Drupal Sitebuilding” Thursday 14:45“DrushDeploy” Jenkins (hudson) Conference sessionsDrupalcon London: August 2011

35. Beyond deployment

36. Other tools Environment automation: Puppet Chef Vagrant Fabric Quickstart CI & test tools Jenkins/Hudson Codesniffer Selenium

37. Questions? Twitter: Blog: Slides: @manarth http://deglos.com/ http://www.slideshare.net/manarth