Not very well. There are issues with not only WordPress but plugins in general when moving databases on the fly, as for as I know, there is no seemless (or effortless) way to do this, it’s hacky at best, for that reason most people still use database dumps. If you just care about preserving db … Read more
There’re a couple of libraries out there. One of the more well known is from Joey Kudish and hosted on GitHub itself. Basically it does the following: utilizes the GitHub API Adds a callback to the ‘pre_set_site_transient_update_plugins’ filter Adds another callback to the ‘plugins_api’ filter finally utilizes the WP HTTP API and does a wp_remote_get() … Read more
This is more a git question than a WordPress one IMHO, but what you need to do is write a bash script and associate with a git hook that does what you want.
There’s the site_status_tests filter, to e.g. remove the asynchronous background updates tests: add_filter( ‘site_status_tests’, function ( $tests ) { unset( $tests[‘async’][‘background_updates’] ); return $tests; } ); But one could argue that this is just hiding information from the user. Ticket #46733 suggests instead e.g. “…ignored tests section, hidden away like the Passed tests“, so the … Read more
Adding this filter in a must-use plugin or functions.php will allow automatic updates even if the site is under version control: add_filter( ‘automatic_updates_is_vcs_checkout’, ‘__return_false’, 1 ); From https://developer.wordpress.org/reference/hooks/automatic_updates_is_vcs_checkout/
I would use WP DB Migrate to export the DB in the production environment. It allows you to rewrite URLs. Then you import that in your local DB.
Why not use a completely separate repo for each child-theme site once its established? Clone the master repo when spinning up the environment, remove the Git directory, init a new Git repo, and push it up to wherever? Now each child theme can be developed independently of each other. Alternatively, if you’re using the same … Read more
Overview That’s the one main caveat of WordPress development, that even a seasoned WordPress developer still wonders what’s the perfect automation for syncing database content from local environment to live server. You can’t just upload your database dump from your local development environment to the server and be happy with the results. WordPress actually stores … Read more
I would formulate your requirements like this: repository should capture complete and precise state of site updates should be tested locally and pushed to production database update events should run in production reliably Sticking with Git alone that would indeed mean that you need to install updates locally and commit them into repository. As for … Read more
Assuming your wp-config.php is already in place and in order: Step 1. Mysqldump your development database Step 2. Replace all instances of development.domain.com to production.domain.com^^ Step 3. Login to MySQL, run a SOURCE command to import data e.g. source /path/to/file ^^ How to replace all instances of old domain with new: (1) Copy the script … Read more