Staging to production – best practice

  • For those who are using a staging environment, do you do a WP version update on staging then push to production – or update staging, test, then update production.

    Wouldn’t updating the WP version local then pushing to ->staging->prod., break the update since only the files are pushed and not any database updates?

    (I assume a WP version update updates the database as well.)

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • Tim Nash

    (@tnash)

    Spam hunter

    If you push just the files, then WordPress will do any extra database changes, the next time someone with admin privileges logs in same way it did when you did the update on the staging site.

    Thread Starter alligatornest

    (@alligatornest)

    Thanks Tim. I am about to modify my work-flow so that I only push my theme changes with Git Hub and Deploy, but manually update WP Core and plugins on local -> staging ->production (testing each along the way of course). Lately, I’ve had issues with DeployHQ taking too long when pushing a WP core update, or throwing an error when pushing a plugin update (like a permissions error on Wordfence).

    Does anyone else have a similar set up?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    FYI, if you put your theme and/or plugin on github, you can use the Github updater plugin to treat updates like any other update.

    https://github.com/afragen/github-updater

    In your workflow, commit locally. When you want stuff to go to the live site, bump the version and push to github then wait until the next time WP checks for updates.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Staging to production – best practice’ is closed to new replies.