Platform-as-a-service (PaaS) solutions have recently sprung up for Drupal, with Pantheon and Acquia Dev Cloud leading the race. The advantages are plentiful: zero set-up costs, instant upscaling, the use of powerful services such as Apache Solr, Varnish, Redis/Memcached, automated Drupal core updates, site profiling tools, etc. In this session, I’ll make Drupal developers familiar with PaaS, and show the concepts of “Cloud-driven development” to speed up development and deployment processes. I will show how to use your local, development, test and production environments to organize your Drupal development, and push changes back and forth using Git, Features and Drush, eliminating the need to share the database and pushing changes exclusively via code. Finally, Drush will make your deployment a breeze. With the free developer subscription of Pantheon and a series of Drush commands and scripts, you will be able to start developing and deploying your own Drupal projects in the cloud, and never again worry about your server. After all, you are a Drupal Developer, not a System Administrator!

1. Cloud Driven
Development
a better workflow, less worries, and more power
Peter Vanhee
20th October 2012 - DrupalCamp Spain

2. Who am I?
‣ Consumer and contributor to Drupal for over 6 years
@pvhee
‣ Co-founder Marzee Labs @marzeelabs, a web shop
from Barcelona
‣ http://marzeelabs.org

3. The Cloud
“The cloud has given has us the ability to provide
nearly limitless, on-demand resources to speed up
our web development and deployment processes”

4. For me?
Photo from Flickr by Abode of Chaos

5. The Cloud

6. Is that enough?

7. Enter PaaS
‣ “Platform-as-a-service”
‣ Yet another service built on top of the cloud
‣ Provides a computing platform and a solution
stack
Source: Wikipedia

8. Know any?

9. Paas for Drupal

10. In general, Drupal PaaS offer
‣ Different environments. Typically a development,
staging and production environment
‣ Code repository, e.g. git
‣ On-demand resources
‣ Specialty services for search, caching, performance
optimization, etc.
‣ A lot of automation of the tools you typically use (or
want to) when building Drupal sites

11. More good stuff
‣ one-click installs of Drupal distributions
‣ they teach you awesome developer processes

12. Disadvantages?
‣ Difficult to break away from the standard setup
‣ Not always shell access - and shell in generally
very limited
‣ Cannot install just anything

13. Cuts most of the deals

14. Enter Cloud Driven
Development
“Cloud Driven Development puts the fun back into
your Drupal development and deployment”

15. Cloud Driven Development Model
adev b test c live
u local

16. Cloud Driven Development Model
for your Team
a dev
u local
u local

17. Cloud Driven Development Model
with the Client
b test c live
Revise new features Work on content

18. Cloud Driven Development Model
for Everyone Else
c live

19. Cloud Driven Development Model
t t
a dev
gn
b test
gn
c live
t
gn
u local
t code moves from left to right
g files and n database move from right to left

20. The Ingredients
for Cloud DD
Drush
+
“exportables”

21. Demo using Pantheon
Free developer tier at http://getpantheon.com

22. Spinning up a new site

24. Go u local
> git clone git@* drupalcamp_spain

25. At Marzee Labs we maintain our own
Drupal distribution
‣ contains modules and sandboxes we always use
‣ has some features we always need
‣ has smart settings preconfigured
mz/mz.make
mz/mz.profile
mz/mz.install
mz/mz.info

26. Make our site
> drush make --no-core
profiles/mz/mz.make .

27. From u local to adev
> git add -A .
> git commit -m "Built site from MZ"
> git push origin master

28. Install your site on adev

29. Install your site (2)

30. Pantheon Dashboard
From http://getpantheon.com

31. A typical development flow
‣ pull the database from the dev/test/live environment *
‣ drush dl awesome_module
‣ configure and export
‣ enable the module, in our site feature
* if you follow a real database-free development flow, you should do this only once at the beginning

32. First: get your drush aliases
from ulocal to
> drush @pantheon.dcspain.dev a dev
> drush @pantheon.dcspain.test
b test
> drush @pantheon.dcspain.live
c live

33. Deploy on adev
> git push origin master
> drush @pantheon.dcspain.dev updatedb
> drush @pantheon.dcspain.dev fra
> drush @pantheon.dcspain.dev cc all

34. Deploy on btest

35. Hello Pandarus
‣ A drupal sandbox* by wodenx
‣ For command-line freaks
‣ Deploy via command-line
‣ Syncronize databases and files
* http://drupal.org/sandbox/wodenx/1512788 soon to be a full d.o. project

36. Deploy faster with Pandarus
> drush pan-deploy test

37. Syncing database and files
never was easier
> drush rsync
@pantheon.dcspain.dev:%files
@self:%files
> drush pan-sql-sync
@pantheon.dcspain.dev @self

38. Pre-launch dev cycle
t
a dev
gn
b test
t gn
u local

39. Going Live
t
btest gn c live

40. Searching like a pro

41. Caching like a boss
‣ varnish / nginx - for anonymous users
‣ redis - for authenticated users

42. Scale!
From http://getpantheon.com

43. Site Profiling

44. Ou Yeah.. there is more
‣ Drupal core updates
‣ On-server development - hot fixes directly on the
server

45. Things to look out for
‣ Drupal 8 and the CMI: will make exportables much better
(think: bye-bye Features)
‣ More command-line magic
‣ More automation
‣ Cloud Driven Development: the future for Drupal?

46. Thanks!
http://marzeelabs.org @marzeelabs