Artwork

Content provided by Bleech. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Bleech or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Local, Remote, Dev, Staging, Live: Our WordPress environments

40:46
 
Share
 

Manage episode 351050114 series 3419630
Content provided by Bleech. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Bleech or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

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.
Highlights
00:00 Intro
00:31 Why care about the development server setup?
01:44 How we deployed back in the days
05:24 How we synch database and assets across development environments
07:05 Local environments on a remote server
10:33 The challenge with maintaining build processes
15:07 How we set up environments, cloning and deployments
21:21 When we split development and staging
22:41 More environments increase complexity
24:34 Dominik's favourite stack and process
31:10 Beware of data privacy!
32:47 A typical workflow for new projects
37:26 The future of dev environments
Links
StackBlitz: https://stackblitz.com/
CodeSandbox: https://codesandbox.io/
InstaWP: https://instawp.com/

More from Bleech
Blog Posts (WordPress Development)
Flynt (WordPress Starter Theme)
VRTs (Visual Tests for WordPress)
Siegfried, deploy! (YouTube Channel)

  continue reading

47 episodes

Artwork
iconShare
 
Manage episode 351050114 series 3419630
Content provided by Bleech. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Bleech or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

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.
Highlights
00:00 Intro
00:31 Why care about the development server setup?
01:44 How we deployed back in the days
05:24 How we synch database and assets across development environments
07:05 Local environments on a remote server
10:33 The challenge with maintaining build processes
15:07 How we set up environments, cloning and deployments
21:21 When we split development and staging
22:41 More environments increase complexity
24:34 Dominik's favourite stack and process
31:10 Beware of data privacy!
32:47 A typical workflow for new projects
37:26 The future of dev environments
Links
StackBlitz: https://stackblitz.com/
CodeSandbox: https://codesandbox.io/
InstaWP: https://instawp.com/

More from Bleech
Blog Posts (WordPress Development)
Flynt (WordPress Starter Theme)
VRTs (Visual Tests for WordPress)
Siegfried, deploy! (YouTube Channel)

  continue reading

47 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide

Listen to this show while you explore
Play