# Plugin configuration workflow between dev/staging and production

**URL:** https://discourse.roots.io/t/plugin-configuration-workflow-between-dev-staging-and-production/14670
**Category:** trellis
**Tags:** plugins
**Created:** 2019-01-24T14:17:49Z
**Posts:** 3

## Post 1 by @tonyhans — 2019-01-24T14:17:49Z

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.

---

## Post 2 by @MWDelaney — 2019-01-24T18:49:45Z

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](https://codex.wordpress.org/Function_Reference/update_option) associated with Yoast, but that’s probably the best you can do outside of merging databases and content.

---

## Post 3 by @system — 2019-03-07T14:17:52Z

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