• Hi! I deployed my WordPress installation using Docker and Rancher. I track all my files using GIT.

    I configured shared directory “wp-content” as described here https://thedockerexperts.com/blog/scale-php-application-across-multiple-nginx-docker-nodes/ . This configuration works pretty good, but I have several questions on optimization of the CI\CD process.

    1. How can I handle new plugin installation on Dev machine and transfer it to the production?
    2. What is the best way to handle DB migrations?
    3. Is it enough to replace WP core files and wp-content in my GIT to update WP core as described here https://codex.ww.wp.xz.cn/Upgrading_WordPress#Manual_Update ?
    4. How to revert changes if my update failed for plugins or WP core? Should I have a backup restored?

    Thanks for the ideas and helpful info!

    • This topic was modified 7 years, 11 months ago by drxelak.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hello @drxelak !

    1. You can list plugin names and versions with WP-CLI, its output can be customized. This output can be parsed on the production server and installed by also WP-CLI.

    2.a. Do you mean the classic migration thus altering DB structure? Try integrating https://phinx.org/
    2.b. If you mean copying the DB from one environment to another then WP-CLI is the choice.

    3. You need to run wp core update-db but I suggest you to get WP core as a composer package

    4. It is very tricky. Reverting core&plugins: composer or WP-CLI, anything other: git, db: I have to figure out

    @szepeviktor Do Wp-cli migrate db from one environment to another (stage to Prod) without a down time.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘CI CD process recommendations for WordPress’ is closed to new replies.