Recommended Sync settings for multiple environments

  • Resolved Django

    (@mediaformat)


    1 year, 3 months ago

    We recently discovered that a client’s MailChimp account was not only syncing to Production, but to the Staging and Development Environments as well.

    Avoid data sync issues

    Keep your staging website synchronized with your live site. Otherwise, you can suffer data loss when you try to make changes. You can use a plugin to keep the synchronization with your WordPress staging site, but you can also do it manually.

    https://mailchimp.com/resources/staging-site/

    I could not find any related documentation, for what is essentially a pretty common setup.

    I also looked into some of the available Constants in the codebase and saw none related to managing this aspect of deployment.

    It would very useful to be able to set some environment variables, so as keep production and dev/test data separate.

    Please advise

    Regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author ryanhungate

    (@ryanhungate)

    1 year, 3 months ago

    @mediaformat yes that does make sense. Out of curiosity, how exactly do you see this being built out? Would you just simply want to “turn off all syncing”? Is it that when you migrate to staging, it is pushing new test items into your Mailchimp account? Any explanation would be beneficial as we come up with a solution.

    Plugin Support KJ

    (@kjvextras)

    1 year, 2 months ago

    @mediaformat Hi! Checking in – Did you have any ideas you would like to drop? We would love to consider them in the next release. Please let us know

    Thread Starter Django

    (@mediaformat)

    1 year, 2 months ago

    Hi @ryanhungate and @kjvextras,

    I appreciate the follow-up!

    The primary concern is avoiding any sync from non-production environments. But in practice there are a few considerations.

    1. Occasionally we will sync our Staging database from Production.
    2. Being able to run tests for new features on Staging.

    To solve for 1. the ideal would be code-based, for example a Constant we could define in .env or even a hook we could add to mu-plugins, which would prevent sync from mailchimp to staging.

    For no. 2, perhaps this could be a tag or other flag type in mailchimp that indicates the data is unrelated to production.

    These are just suggestions, I’m glad to hear your thoughts on the matter.

    Plugin Support KJ

    (@kjvextras)

    1 year, 2 months ago

    These are great suggestions! Thank you! We will do some discovery and will get back to you.

    Plugin Support KJ

    (@kjvextras)

    1 year, 1 month ago

    Letting you know we logged these requests – Stay tuned and visit our github page to stay up to date!

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Recommended Sync settings for multiple environments’ is closed to new replies.

Tags