Best Practices to promote a WordPress Site from Dev to Test to Prod

  • kabalibalasubramanian

    (@kabalibalasubramanian)


    4 years, 9 months ago

    Hi All,

    We are developing WordPress Site lampstack running in Pivotal Cloud Foundry Container, Apache, PHP runtime, MySQL DB (configurations) and AWS S3 bucket (remote storage to store media files). This container do not have any command line access.

    We have 3 different environments in separate cloud container (Dev, Test and Prod). Development is being used to develop the themes, plugins etc (non-content). We are using Elementor page builder to build our site. And we are trying to promote same changes from Dev to higher environments (test and Prod).

    The plugin, theme changes (PHP, HTML, JavaScript code) are stored in Git repository, configurations are getting stored in MySQL DB and media files are stored in AWS S3 bucket.

    We are able to move the changes committed in Git Repository into Test environment. Whereas unable to identify the configurations stored in MySQL DB for newly developed elementor pages.

    We would like to know the possibility of identifying the MySQL DB configuration changes that are being made by elementor and migrate the configurations into Test environment. Also, we want to know how to merge the DB configurations from Test to Production without overwriting the existing live content changes.

    Any help would be highly appreciated. Thanks!

    [ Signature deleted ]

Viewing 1 replies (of 1 total)

  • If you find a good reliable solution, let us know because there’s currently nothing that can do that!

    What you are finding is the single biggest problem with every CMS out there. There’s just nothing available that can do any form of source control in database entries and keep things “as they should be” on all versions (dev, staging, live) of a site.

    The only thing that’s come close, for WordPress at least, is VersionPress. BUT… be aware that it says right on the home page “Please note that VersionPress is a developer preview.” so it’s no fully ready for real-world use. As a note it’s said that for years now, so I don’t think it’s going to bet much better.

Viewing 1 replies (of 1 total)
  • The topic ‘Best Practices to promote a WordPress Site from Dev to Test to Prod’ is closed to new replies.

Tags