Don’t Break Live: Using a Staging Site Can Make Your Life a Lot Easier
summary
Shows how a staging copy prevents the “white screen” by replicating live files and the MySQL database, handling serialized URLs, and testing updates before deploy; demos and tools include one-click staging on hosts like WP Engine and Pantheon, migration plugins such as Duplicator and WP Migrate DB, and local tools like Local by Flywheel and DesktopServer. Covers disabling emails/caching on staging, merging limits for databases, Git/CI deployment options, and recommends scheduled monthly staging updates.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:27Why staging sites matter
- 3:33What is a staging site
- 7:51Requirements for staging
- 8:35Auditing your site
- 11:47Hosting one-click staging
- 13:53Staging plugins
- 14:56Manual staging setup
- 16:01Duplicating your site
- 18:50Pushing changes live
- 20:17Overwriting vs merging
- 22:03Staging plugins overview
- 24:56Local development environments
- 27:48Update schedule importance
- 28:52Evaluating your options
- 31:02Developer workflow basics
- 33:50Provisioning staging sites
- 36:22Sharing environment keys
- 37:30Configuration challenges
- 38:56Content gaps in staging
- 41:06Deployment tools
- 43:18Q&A
