deploy wordpress database settings and not content

What is the best way to deploy wordpress database settings to production without having to migrate the entire database? I am using git and https://github.com/wp-cli/wp-cli. If I have a development branch checkout out need to merge this back in to master, there must be a way to deploy database settings without having to migrate the full database including content. In Drupal there is a module called ‘Features’ which handles this process. Any suggestions regarding wordpress deployment processes across multiple development environments would be fantastic.

Related posts

Leave a Reply

1 comment

  1. You can’t define “module”, WordPress term is plugin, in wp-config.php The plugin settings are stored in the table _options table, but some plugins use multiple rows, others create entire new tables.

    If the plugin doesn’t have the option to export/import the settings, you can almost forget about it. You would have to dig in the code to figure out the names of the rows in the DB and if the the plugin creates new tables.