Add the ability to clone/sync an environment #28
Replies: 3 comments 1 reply
-
Please add this! A typical approach I take is to add prod then duplicate prod and make a dev. So cloning should clone all s3 assets, database, env settings, and env variables. then I could go in and manually tweak from there--since we'd change the environment from production to dev and change the site url. But you won't know if someone is going from dev to prod or prod to dev, so I suppose you could add a radio dropdown like this: Change Env settings? that'll solve the minor thing I do at the end. with the env variables. You could change the settings and apply dev or prod etc based on what we selec tint he radio. But regardless, having a clone option do all the rest is gold. Especially because from time to time it is nice to nuke dev and then clone prod so dev looks more like prod. It would be lovely to do this easily |
Beta Was this translation helpful? Give feedback.
-
Related #26 |
Beta Was this translation helpful? Give feedback.
-
This would be a big boon. We have some content heavy websites and a big part of staging is just testing that new features and tweaks don't break existing content, including assets. Being able to say "Staging, take the current assets and DB from production but with this branch" would be a game-changer in productivity. Alternatively/additionally it might be nice if the "Local Configuration" asset access |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What should be included?
Beta Was this translation helpful? Give feedback.
All reactions