Within the Chain.io platform, we provide you with up to three different environments for running and testing your integrations. This article explains the environments and their intended uses.
All customers will have a production environment. QA & Dev are optional and can be configured upon request.
Description: This is your main account for production traffic and should not be used for testing. The name will be your company name.
Chain.io Environment: This runs in the production chain.io environment fronted by https://portal.chain.io and is your main account.
Description: This is an optional account where you can test your integrations and configurations against Chain.io production code.
Chain.io Environment: This runs in the production Chain.io environment fronted by https://portal.chain.io under a secondary account. If your main account is named "Joe Forwarder", we will create a second account in the portal called "Joe Forwarder (QA)" for this environment. These two accounts are fully isolated from each other so you can test configurations in QA without impacting production.
Description: This is an optional account where you can test integrations with us against the bleeding edge Chain.io code. It should only be used when both you and the Chain.io development team are actively co-developing a new integration type.
Chain.io Environment: These accounts are setup in an isolated portal. If needed, you'll be provided with the correct url by the development team. This environment is reset to our "master" codebase each night US time, so you'll need to make sure you are communicating your testing plans with your project manager so we can be sure you're testing against the correct code base. Our goal is to move code as quickly from this environment to your QA environment so you can do user acceptance testing against a stable code base.
Article is closed for comments.