Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

WordPress Modern WordPress Workflow The Production Server Migrating to Production

Nicholas Olsen
seal-mask
.a{fill-rule:evenodd;}techdegree
Nicholas Olsen
Front End Web Development Techdegree Student 19,342 Points

Deploying to production using Wordmove: pull --db -e=production, push --all -e=production?

I'm going over the course on Modern WordPress Workflow - beginning the final section on migrating to production. In this video, he says if the database on production has been updated since the last time a local copy of the database was made, then "you have a sticky situation."

His advice is to push everything to production, then update the database as fast as possible.

My question is, why not pull the database from production to local first, then push everything to production? Is there a problem with that I am not seeing?

Eduardo Rubio
Eduardo Rubio
11,420 Points

I was confused by this as well. I've been doing this with a live site I'm working on using the Migrate DB plugin. Any time I need to make changes, I pull the database from the production/live site into my local environment, make the changes I need to make, and push everything back to the live site. As far as I can see, things have worked out well. I really hope I'm not messing something up.