Listen "Local, Remote, Dev, Staging, Live: Our WordPress environments"
Episode Synopsis
How do you make sure every developer on a website project sees the same content across environments? How do we maintain stable development environments for very old websites? And on which environments do we present code changes to our clients? In this episode Dominik and Steffen give insights how they set up the deployment and cloning process and architecture at Bleech. Highlights00:00 Intro00:31 Why care about the development server setup?01:44 How we deployed back in the days05:24 How we synch database and assets across development environments07:05 Local environments on a remote server10:33 The challenge with maintaining build processes15:07 How we set up environments, cloning and deployments21:21 When we split development and staging22:41 More environments increase complexity24:34 Dominik's favourite stack and process31:10 Beware of data privacy!32:47 A typical workflow for new projects37:26 The future of dev environmentsLinksStackBlitz: https://stackblitz.com/CodeSandbox: https://codesandbox.io/InstaWP: https://instawp.com/More from BleechBlog Posts (WordPress Development)Flynt (WordPress Starter Theme)VRTs (Visual Tests for WordPress)Siegfried, deploy! (YouTube Channel)
More episodes of the podcast Siegfried, deploy!
Rapid WordPress dev setups with wp-now
07/11/2023
Why Passkeys are the future
24/10/2023
What's New in Flynt v2.0
14/09/2023
HTMX is awesome and here's why
07/09/2023
Debugging Open Graph Images on Social Media
17/08/2023
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.