Screencast: Pushing Local Development Data to a Staging Environment with WP Migrate DB Pro

Transcript:

So, I have two different environments here. I’ve got my development environment in this tab, and a staging environment in this tab.

Usually a staging environment is where… somewhere out on the web, where your clients can go take a look at their website. Whereas your development copy is something local, it’s probably not viewable by the public.

So, I want to update the staging environment with the data that I’ve been working on in my development environment.

And as you can see here, there is quite a difference between the two. There’s new posts, I’ve got some plugins enabled on my local copy. There’s Varnish here, there’s SES stats here. And these are not available, currently not activated, in the staging environment.

So, let’s do a push.

So if we go to the development environment and go to Tools, Migrate DB Pro. And then we want to do a push, so we select push.

And now we need connection info, so let’s go to staging environment and go to Tools, Migrate DB Pro. And go to Settings and copy.

And then let’s go back to our development environment and paste. And so there, we’re connected. And we’ve already been pre-populated, so we can go ahead and push.

And it looks like everything’s finishing up here, and there we go. Migration has been pushed to staging.

So if we switch of to staging and we check our dashboard. And we see that numbers have changed. Varnish is now showing up, SES Stats is showing up, and we’re all refreshed.

About the Author

Brad Touesnard

As founder of Delicious Brains Inc., Brad wears many hats; from coding and design, to marketing and partnerships. Before starting Delicious Brains, Brad was a busy freelance web developer, specializing in front-end development.

  • lkraav

    How you doin. How about a video on how the Migration Profiles work?

    • Sure thing boss, we’ll look to have a video for that in the future!

  • I’ve been trying to emulate this setup but seems like there’s a bug or js conflict in PagodaBox environment (my staging/testing env.)

    Tried googling seems like not many has a Setup of PB + WMDP.

    http://quick.as/ellbikbe

    Tried it on Chrome Version 31.0.1650.63, FF 25.0.1, Safari Version 6.1 (7537.71) on Mac OSX 10.7.5