Managing and Syncing Environments (Dev, Test, and Live) in Sharetribe
Overview
Sharetribe's platform includes three main environments: Development (Dev), Test, and Live. Each environment serves specific purposes, and understanding their synchronization rules and capabilities is vital for effective configuration management.
Environment Synchronization and Copying Rules
No-Code Changes Between Environments: - No-code changes can only be copied from Test to Dev or Live. Copying in the reverse direction is not available within self-service functionality. - For one-time needs, Sharetribe can manually override a Test environment with the current Dev or Live setup. However, ensure you copy all the settings that you want on your Dev or Live before initiating this process, as it replaces all Test no-code settings with those from Dev or Live environments.
Custom Code in Test Environment: - Sharetribe-hosted Test environments only support no-code functionality and do not support deploying custom code. To test custom code changes, deploy a self-hosted instance configured to run in the Test mode instead. This approach aligns Dev, Test, and Live and incorporates code into standard deployment workflows.
Legacy Features: - Older "copy changes" features allow copying from Dev to Live. However, activating this feature prevents copying from Test, making it primarily useful when transitioning between Dev and Live with code. This feature highlights historical contrasts with the no-code-first workflow.
Data and Listings: - Each environment maintains separate datasets, including users, listings, transactions, and reviews. Copying listings or data between environments, such as from Test to Live, is not supported. Instead, users are encouraged to manage and validate configurations in Test before implementing them in Live.
Using the Test Environment for No-Code Validation
The correct no-code Test setup: If you are working without code, then your test environment and live environment settings would behave the same way. Make sure you keep these environments in sync so that when you want to test new changes or features you can do it safely in Test and not affect your Live environment.
The correct custom-code Test setup: when working with a developer and using custom code, the correct Test setup will vary depending on the way you are developing your platform. By default, Test is the place were you should configure the no-code settings. Having a copy of your custom-coded application connected to your Test environment would be mandatory for this to happen in a precise way.
Best Practices for Transitioning Configurations
Leverage the Test environment to replicate potential scenarios without affecting Live configurations.
Always have the Test data up to date before making changes to Live or Dev environments. Try to keep all the no-code settings of all of the environments you are working with in sync.
By understanding these environment rules and capabilities, you can effectively manage and synchronize your Sharetribe platform for optimal operation.