Plugin configuration workflow between dev/staging and production

Trying to figure what would be the better way to configure the plugin once and have it replicate to staging/production when ready. For example, I could have configured yoast seo plugin on staging, how do I replicate it to production easily?

Another scenario would be some plugin that is not working for development mode, example jetpack, hence I cannot test it on dev machine, unless it is the first test on staging and repeat back to production.

Currently, I am configuring the plugin settings at each env individually, it is error-prone and time-consuming. Wondering is there better practice or workflow that could improve this.

This is kind of outside the scope of the Roots tools. You could probably write some actions and filters to set and re-set the options associated with Yoast, but that’s probably the best you can do outside of merging databases and content.


This topic was automatically closed after 42 days. New replies are no longer allowed.