This article provides an overview of the weekly synchronization process between the production, staging, and development environments, including the sync rules applied during this process.
Synchronization ensures that the staging environment closely mirrors production, aiding the testing of new features before deployment. It also allows flexibility in syncing the development environment based on project requirements.
Sync schedule
The production environment is synchronized with the staging environment every Saturday morning at approximately 3 am AEST.
Sync rules
- All product and order data on staging will be overwritten by anonymized production data.
- User credentials will be copied from production to staging. Users should use their production credentials to access the staging environment.
- API Keys will be copied from production to staging.
- Webhooks on staging will be wiped clean. However, webhooks from production will not be transferred to staging to prevent any inadvertent data transmission.
- MConnect integration setup on staging will be cleared and must be manually set up again.
Sync rules for anonymization
In anonymizing a Marketplacer database, synchronization rules dictate the transformations applied to its tables and columns. These rules guarantee the replacement or removal of personally identifiable information or sensitive data, preserving privacy while upholding data integrity.
Related articles