DrupalCon26: From Firefighting to Sleeping at Night

Bad deployments kill agency reputations. This session walks through how modern hosting infrastructure can power smarter dev workflows—staging environments, Git integration, automated deployments—so your team ships faster with fewer disasters and happier clients.

Transcript

1. Your tech. Sovereign hosting. d l a w t t i m @ H C I M L E H MARTIN G N I T H G I F E R I F FROM T H G I N T A G N I P E E L TO S & G N I G A T S F O O R P T E L L U B A G N I D L I W U O B L F K R O W T N E M Y O L P E D - CC 0 SpaceX
2. YOUR STUFF ? DEPLOYMENT INFRASTRUCTURE
3. N I T R A M H C I M L HE mittwald Chief Technology Evangelist Head of Developer Relations TYPO3 Association Board Member PHWT Lecturer, Software Engineering & Cloud Computing
4. 16 YEAR OLD MARTIN HIS SHITTY FIRST TYPO3 SITE - https://web.archive.org/web/20040829084706/http://www.espelkamper-nachrichten.de/
6. martin@local $ rsync -a . your-server.example:/path/to/prod sending incremental file list uploading file 1 of 8756234...
8. WE HAVE VERSION CONTROL, DON’T WE? I'M GOING TO DEPLOY MY SOFTWARE WE HAVE VERSION CONTROL, DON’T WE?
9. martin@local $ ssh your-server.example martin@server $ cd /path/to/prod martin@server path/to/prod $ git pull martin@server path/to/prod $ PROFIT!!!
10. R U O Y E S O O CH S L O O T
12. R E N I A C O NT IMAGE YOUR F F U T S D E R I U REQ T N E M N O R I V EN YOUR STUFF YOUR PROBLEM ! INFRASTRUCTURE NOT YOUR PROBLEM
13. Image Source
15. IT DEPENDS – every consultant, ever
16. “I JUST NEED TO GET MY CODE UP ON THE SERVER” “JUST DO A GIT PULL” E S A B A T A SMOKE D TESTS S E T A UPD LANGUAGE FILES FRONTEND BUILDS T N CO S U O U IN RY CACHE FLUSHING
17. DEPLOYMENT REQUIREMENTS REPEATABLE and (potentially) AUTOMATABLE Complex processes consisting of multiple build steps should be easily repeatable without margin for human error. Typically, specialized deployment tools are used for this.
18. DEPLOYMENT REQUIREMENTS REPEATABLE and (potentially) AUTOMATABLE ZERO DOWN TIME Deployments should not cause a down time; the software delivered to users should always be consistent, and releases should be switched instantly (“atomic”)
19. DEPLOYMENT REQUIREMENTS REPEATABLE and (potentially) AUTOMATABLE ZERO DOWN TIME REVERSIBLE A deployment should be easily reversible in case of an unexpected error.
20. s e t i s d e t a ? d s p s u e n y i l t s n n u o i e b t u a e q r z i e o r c f m n o y i t c r s n o u / e c d g l n a a a n m i d o n e i s d v i u m a l / c o l t o o r p f n o , u , h n m P S o a i T t e F _ t a S l z l i , a d s r e m a t s d a , n t d a e p t g u S d o u _ t b u s A , p s o n l l o a i t m u l S o s _ d e g a n a M HERE BE  DRAGON S E V N O C E C N E I N L O R T ON dated Cfrequently up tions u l / o x s e l m p o t m s ? o s u c c / M , O d m e B a v S i e l t ? s g e t n g n r o e s a L l e m , t e n e r i o n i r u t e q a b e z i r u m K e o , c t s n s r a i u e l c n p i f a m t o o n _ e o C e r C g e d  h g i _ H _ _
21. WE O T E M O C L C I M O T T N E A M Y O L P E D R E Y O L P E D h rg o . r e y o epl d / / : s ttp
23. SEE https://github.com/mittwald/deployer-recipes
24. SEE https://github.com/mittwald/deployer-recipes
25. DEPLOYMENT REQUIREMENTS REPEATABLE and (potentially) AUTOMATABLE ZERO DOWN TIME REVERSIBLE CHOOSE YOUR TOOLS
26. MARTIN HELMICH m.helmich@mittwald.de martin.helmich@typo3.org linkedin.com/in/martinhelmich Your tech. Sovereign hosting. mittwald.de