Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
#DCMuc16 @drubb
Closing	the	Drupal	Hosting	Gap
A	Review	of	Wodby
DrupalCamp	Munich,	3.12.2016
#DCMuc16 @drubb
About	me
Boris	Böhne
aka	drubb	on	d.o,	DrupalCenter,	Twitter,	Slideshare,	...
Freelance	Drupal	Developer
S...
#DCMuc16 @drubb
1.	Some	typical	Hosting	Solutions	for	Drupal
#DCMuc16 @drubb
1.1	Back	in	the	Old	Days:	Shared	Hosting
 cheapest	solution
 wide	availability
 no	ssh,	git,	drush,	......
#DCMuc16 @drubb
1.2	Roll	your	Own:	Self-managed	Server
 inexpensive
 great	flexibility
 needs	much	knowledge	(Linux,	pr...
#DCMuc16 @drubb
How	to	Manage	a	Server...
#DCMuc16 @drubb
1.3	Top	Notch:	Drupal	Business	Hosting
(looking	at	you,	pantheon.io	/	amazee.io	/	acquia	cloud	/	platform....
#DCMuc16 @drubb
2.	Closing	the	Gap:	The	Wodby	Approach
Your	servers,	your	repos,	your	workflow
Infrastructure	as	a	service...
#DCMuc16 @drubb
2.1	Basic	Wodby	Concepts
Application
Your	Drupal	site,	with	all	environments	(instances)
Bundle
Optimized	...
#DCMuc16 @drubb
2.2	Managing	Servers	and	Git	Repositories
One	or	multiple	servers
One	or	multiple	providers
Native	or	cust...
#DCMuc16 @drubb
#DCMuc16 @drubb
#DCMuc16 @drubb
#DCMuc16 @drubb
2.3	Working	with	Applications
Application	=	Your	site
Customized	bundle	/	stack	per	application
Optimized	...
#DCMuc16 @drubb
#DCMuc16 @drubb
#DCMuc16 @drubb
#DCMuc16 @drubb
2.4	Managing	Environments
Unlimited	instances	per	application
Assigned	to	git	branches	/	servers
Three	ins...
#DCMuc16 @drubb
#DCMuc16 @drubb
#DCMuc16 @drubb
#DCMuc16 @drubb
2.5	Domain	Management
 Internal	default	domain	per	environment
 One	or	more	custom	domains	per	environme...
#DCMuc16 @drubb
#DCMuc16 @drubb
2.6	Daily	Workflow
 Git-based	workflows
 Manual	/	automated	deployments
 Post-deployment	scripts	using	...
#DCMuc16 @drubb
#DCMuc16 @drubb
Post	deployment
example	script:
wodby.yml
																			pipeline:
																			-	name:	update	d...
#DCMuc16 @drubb
#DCMuc16 @drubb
Example:	Basic	deployment	using	Drush	/	Git
Dev	instance Prod	instance
(Just	one	master	branch,	no	local	d...
#DCMuc16 @drubb
2.7	Security
 Isolated	environments
 Drupal	security	best	practices
 Files	outside	web	root
 Limitatio...
#DCMuc16 @drubb
#DCMuc16 @drubb
#DCMuc16 @drubb
3.	What	else?
Fine	grained	access	control	per	organization	/	application
Clustered	solutions	(HA)
Wodby	AP...
#DCMuc16 @drubb
Wodby	Team	Management
Assign	user	roles	/	access	rights
General	(per	organization)
Per	application
#DCMuc16 @drubb
#DCMuc16 @drubb
Read	on
docs.wodby.com
docs.wodbyapi.apiary.io
docker4drupal.org
slideshare.net/drubb
#DCMuc16 @drubb
Thank	you!
Questions?
Upcoming SlideShare
Loading in …5
×

Closing the Drupal Hosting Gap - A Review of Wodby

1,005 views

Published on

Presentation from DrupalCamp Munich 2016 about Drupal hosting options, reviewing Wodby (https://wodby.com)

Published in: Internet
  • When it’s come to select a Drupal hosting option there is one main thing that almost everyone looks for is reliability in affordable prices. One such reliable Drupal cloud hosting provider is Cloudways, they offer very awesome services, there uptime is almost 100%, they guarantee 1-click setup, user friendly easy to use console, unlimited storage, managed security with backups, 24/7 customer support and lot more in unbeatable lowest prices. More info on: https://www.cloudways.com/en/drupal-cloud-hosting.php
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Closing the Drupal Hosting Gap - A Review of Wodby

  1. 1. #DCMuc16 @drubb Closing the Drupal Hosting Gap A Review of Wodby DrupalCamp Munich, 3.12.2016
  2. 2. #DCMuc16 @drubb About me Boris Böhne aka drubb on d.o, DrupalCenter, Twitter, Slideshare, ... Freelance Drupal Developer Sindelfingen, Germany Drupal since 2006 (Drupal 4.7)
  3. 3. #DCMuc16 @drubb 1. Some typical Hosting Solutions for Drupal
  4. 4. #DCMuc16 @drubb 1.1 Back in the Old Days: Shared Hosting  cheapest solution  wide availability  no ssh, git, drush, ...  no additional services, like Varnish or Solr  no flexible configuration, e.g. php memory  not optimized for Drupal  multiple security flaws
  5. 5. #DCMuc16 @drubb 1.2 Roll your Own: Self-managed Server  inexpensive  great flexibility  needs much knowledge (Linux, provisioning, security, ...  time-consuming maintenance
  6. 6. #DCMuc16 @drubb How to Manage a Server...
  7. 7. #DCMuc16 @drubb 1.3 Top Notch: Drupal Business Hosting (looking at you, pantheon.io / amazee.io / acquia cloud / platform.sh / freistilbox)  Optimized stacks  Top performance  Scalability  Top security  Latency issues (e.g. server location)  Privacy concerns (EU data privacy laws)  Not affordable for some customer types  No support for Drupal 6 (e.g. PHP version)
  8. 8. #DCMuc16 @drubb 2. Closing the Gap: The Wodby Approach Your servers, your repos, your workflow Infrastructure as a service Base tools: Docker, Kubernetes https://wodby.com
  9. 9. #DCMuc16 @drubb 2.1 Basic Wodby Concepts Application Your Drupal site, with all environments (instances) Bundle Optimized stack of services for an application type, e.g. web server, database server, Varnish, Solr, ... Instance Single environment, like dev/stage/prod Container Docker container holding one service Server Hosting platform, e.g. VPS, cloud or dedicated server
  10. 10. #DCMuc16 @drubb 2.2 Managing Servers and Git Repositories One or multiple servers One or multiple providers Native or custom integrations
  11. 11. #DCMuc16 @drubb
  12. 12. #DCMuc16 @drubb
  13. 13. #DCMuc16 @drubb
  14. 14. #DCMuc16 @drubb 2.3 Working with Applications Application = Your site Customized bundle / stack per application Optimized stacks e.g. for D6 / D7 / D8, Wordpress, ... One or more environments / instances per application
  15. 15. #DCMuc16 @drubb
  16. 16. #DCMuc16 @drubb
  17. 17. #DCMuc16 @drubb
  18. 18. #DCMuc16 @drubb 2.4 Managing Environments Unlimited instances per application Assigned to git branches / servers Three instance types: Dev, Stage, Prod Import database / files, e.g. from other environments
  19. 19. #DCMuc16 @drubb
  20. 20. #DCMuc16 @drubb
  21. 21. #DCMuc16 @drubb
  22. 22. #DCMuc16 @drubb 2.5 Domain Management  Internal default domain per environment  One or more custom domains per environment  Let's Encrypt certificates for custom domains  Support for Basic Authorization
  23. 23. #DCMuc16 @drubb
  24. 24. #DCMuc16 @drubb 2.6 Daily Workflow  Git-based workflows  Manual / automated deployments  Post-deployment scripts using yaml files  Remote debugging with Xdebug  Deploy via UI  Deploy via CLI (Drush, Git, Composer)
  25. 25. #DCMuc16 @drubb
  26. 26. #DCMuc16 @drubb Post deployment example script: wodby.yml pipeline: - name: update db type: command command: drush updb -y directory: $WODBY_APP_DOCROOT - name: clear cache type: command command: drush cc all directory: $WODBY_APP_DOCROOT
  27. 27. #DCMuc16 @drubb
  28. 28. #DCMuc16 @drubb Example: Basic deployment using Drush / Git Dev instance Prod instance (Just one master branch, no local development environment) drush @wodby.drubb.chips.dev ssh drush up ctools -y drush cc all ... do some checks ... git commit -am 'Updated CTools module' git push exit drush @wodby.drubb.chips.prod ssh git pull drush cc all exit
  29. 29. #DCMuc16 @drubb 2.7 Security  Isolated environments  Drupal security best practices  Files outside web root  Limitation of executable scripts  Regulary backups  Local  Remote
  30. 30. #DCMuc16 @drubb
  31. 31. #DCMuc16 @drubb
  32. 32. #DCMuc16 @drubb 3. What else? Fine grained access control per organization / application Clustered solutions (HA) Wodby API Open Source: Docker4Drupal
  33. 33. #DCMuc16 @drubb Wodby Team Management Assign user roles / access rights General (per organization) Per application
  34. 34. #DCMuc16 @drubb
  35. 35. #DCMuc16 @drubb Read on docs.wodby.com docs.wodbyapi.apiary.io docker4drupal.org slideshare.net/drubb
  36. 36. #DCMuc16 @drubb Thank you! Questions?

×