Hello - while building out our community before launch, we did all the work in Production since there were no members that it would affect.
Now that we have members on it, we’d like to perform changes in the Staging site, but it looks nothing like our Production site.
The work it would take to get the Staging site up to date is a lot, so it would be helpful for Community Managers to have a way to copy our production site into the staging site.
+1 we absolutely need the ability to synchronise these environments. It’s really hard to test changes without seeing how they impact user generated content, and duplicating the work I’ve done on production into staging is really time consuming.
We need the capacity to refresh our sandbox site (“almostinsided”) to mirror the content of our production site so that we can test changes safely before scheduling them for production. The mirrored site should have security exceptions such as a unique set of access privileges.
The absence of a sandbox that mirrors the production site discourages site improvements because they can put the business at risk.
Hi all! Thank you@dannygarcia for submitting the idea.
We completely understand the need for this. However, we currently don’t have any concrete plans yet to implement this. There’s also a lot of caveats to consider with this, including (but not limited to) the fact that, as far as I know, we’re not allowed to move user data between data processing regions. This quickly becomes an issue for our US customers, because our staging environments are EU only. So any feature like this would probably have to be limited to non-user generated content, like configuration, styling, etc.
I’ll leave this idea open to gather some more momentum, and will update you of course in case we have any news on it
+1 to this! Just encountered this today and I’m like… omg I cannot take the time to make our Sandbox like our Production environment.
So any feature like this would probably have to be limited to non-user generated content, like configuration, styling, etc.
I would really love this. If we're considering changing this up, this would help a bunch.
Would love to see this possible!
+1 - would be really helpful. Also segmenting different areas, for example: Update only the knowledge-base changes, etc.
+1 - we require the ability to move at least the config (data as well, however config more important than data) between sandbox and production. Even if we are able to manually export pieces of config in (XML or binary blobs or any other format) and then import into the other platform it will help.
Hello,
@dannygarcia What is the status of this idea?
Thank you