Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Nicholas Olsen
Front End Web Development Techdegree Student 19,342 PointsDeploying 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
11,420 PointsEduardo Rubio
11,420 PointsI 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.