Our system has 2 environments: development and production. Should we create 2 different workspaces for each environment?
Solved
Whats the best way to handle test environments and production environments
Best answer by Felix
Hey Rushil,
both options have pros and cons.
The main con for having two workspaces (prod & dev) is that you can’t simple “roll out” the dev environment. You will have to set up the prod one the same way (may take a lot of time). You can only copy paste campaign flows from one workspace to another.
The main con for having one workspace is that test data will flout around in the prod environment and mess up with metrics. Also you have to be very careful to not send real people test campaigns.
I personally tend to one workspace, but that depends on your setup as well.
Hope that helps,
Felix
Hey Rushil,
both options have pros and cons.
The main con for having two workspaces (prod & dev) is that you can’t simple “roll out” the dev environment. You will have to set up the prod one the same way (may take a lot of time). You can only copy paste campaign flows from one workspace to another.
The main con for having one workspace is that test data will flout around in the prod environment and mess up with metrics. Also you have to be very careful to not send real people test campaigns.
I personally tend to one workspace, but that depends on your setup as well.
Hope that helps,
Felix
Thanks
1 person likes this
FYI Having one single environment means that any developer on the team needs access to your production Customer IO data (read & write). This is very unsafe.
It’s fairly easy to copy transactional emails from one environment to the other, so I would highly recommend you do it.
1 person likes this
Reply
Most helpful members this week
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.