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 ClickMarcus DeglosPrincipal Engineer - Capgemini@manarth

2. Can you make a build with ONE step?

3. Starting from square oneContract ✔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 repositoryDownload latest Drupal to your checkoutStart coding?Downloading contrib modulesClick + configureCustom modules and themes?

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

6. Two phasesCold start: installing from scratchUpdating a live site

7. Cold start considerationsScript everything.Tools include:drushdrush makeinstall profilesdistributions (which typically use a complex install profile)

8. Start simpleDBWeb serverVarnish

9. Deployment – what’s in a name?At its simplest, it’s:Move code from repo to serverBut there’s more…Switching symlinksLinking up file paths?Clearing cachesRunning update.phpPost-deploy tasks:DB changes?Drush commands?Notify external systems?

10. Pushing codeIt’s all been done beforeFTPManual deployment – SSH/rsyncBash scriptRube goldberg machineCapistrano/WebistranoAnt/PhingJenkinsAegirDrushGit commandsRPM packages

11. Simple tools for simple problemsWith 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 deployversion=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/$timestampsvntag=$svn/$versionsvn co $svntag $destination# Switch symlink.rm -f $docrootln -s $destination $docroot# Clear caches with Drush.drush -l $docroot cc allSlides will be on slideshare.

13. Enterprise sites: simpleHA ProxyHA ProxyVarnishVarnishWebWebDB (master)DB (slave)

14. Enterprise sites: complex+HA ProxyHA ProxyVarnishVarnishWebWebMemcacheSOLRDB (master)DB (slave)NAS/SAN

15. Enterprise sites: complex++HA ProxyHA ProxyZeusZeusVarnishVarnishWebWebMemcacheLDAPSOLRESBDB (master)DB (slave)NAS/SAN

16. Why is this complex to deploy?Multiple hostsMultiple rolesDifferent actions for different roles

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

18. Deployment conceptsRolesWebserver

19. Reverse proxy

20. Network management

21. Data cache

22. Database

23. Authentication hostHosts192.168.20.4

24. web1.example.comTasksClear data cache

25. Checkout codeActionsDeploy to stage

26. Close site for maintenanceEnvironments, hosts, rolesDemo172.16.25.10 = web, cache, db, proxyLive192.168.20.30 = web, cache192.168.20.31 = web, cache192.168.20.32 = web, cache192.168.20.40 = db192.168.20.50 = proxy Environ-mentsHostsRoles

27. Tasks, actions, targetsRecipeDeploy code

28. Restart memcacheTasks / RecipesActionsRoles

29. Pushing codeIt’s all been done beforeFTPManual deployment – SSH/rsyncBash scriptRube goldberg machineCapistrano/WebistranoAnt/PhingJenkinsAegirDrushGit commandsRPM packages