Skip to main content

Preview Status Configuration

Overview​

Preview Status is an important feature in the cloud development environment, providing developers with an independent preview environment and preview data capabilities. By enabling Preview Status, developers can safely develop, test, and iterate without affecting the production environment, effectively reducing development risks and improving development efficiency.

Features​

After enabling Preview Status, the CloudBase environment will exhibit the following characteristics:

  • Environment Isolation: The preview environment is completely isolated from the production environment, ensuring that development and testing do not affect online services.
  • Data Independence: Preview data is completely separate from production data, enabling safe data model adjustments and testing.
  • Version Management: Supports independent release and management of preview versions and production versions.
  • One-Click Release: After passing testing and verification, the preview version can be released to the production environment with one click.

Application Scenarios​

The distinction between preview and production is primarily used in the following scenarios:

  1. Separation of Development Testing and Production Usage: Develop and test features in Preview Status, then publish to the production environment after verification.
  2. Data Model Iteration: Safely adjust data model fields in Preview Status, then synchronize to the production environment after validation.
  3. Functional Preview Experience: Allow a subset of users to experience preview versions, collecting feedback before deciding on official release.
  4. A/B Testing: Run preview and production versions simultaneously to compare the performance of different versions.

Supported Resource Types​

Data Model​

  • Dual-Environment Data: The data model distinguishes between preview and production data, enabling separate querying or editing of preview and production data content.
  • Field Modification: Data model fields can be safely adjusted in Preview Status without impacting the production environment.
  • One-Click Synchronization: After passing field modification testing, the data model structure in Preview Status can be published to Production Status with one click.

Application Editor​

  • Environment Selection: The Application Editor supports selecting preview data or production data for integration during development.
  • Version Release: During application deployment, you can choose to release either a preview version or a production version.
  • Independent Access: Preview versions and production versions have separate access links.

Configuration Steps​

  1. Go to the Cloud Development Console and select the environment to be configured
  2. In the left navigation bar, select [Environment Configuration] - [Environment Settings] - [Preview Status Configuration]
  3. Click the switch to enable Preview Status
  4. After saving the settings, the system will automatically enable Preview Status for you.

Best Practices​

Development Workflow Recommendations​

  1. Requirements Analysis: Define functional requirements and development objectives
  2. Preview Status Development: Conduct feature development and data model adjustments in the preview environment
  3. Internal Testing: Conduct functional testing within the team in the preview environment
  4. Experience Feedback: Invite a subset of users to experience the preview version and collect feedback
  5. Optimization Iteration: Perform optimizations in the preview environment based on feedback
  6. Official Release: After passing testing and verification, release the preview version to the production environment

Notes​

  • Resource quotas for the preview environment and production environment are shared. Please plan resource usage appropriately.
  • Preview data is completely separate from production data and requires manual synchronization or migration.
  • It is recommended to regularly clean up unused preview data to avoid occupying excessive storage space.
  • For sensitive operations (e.g., data deletion, structural changes, etc.), it is recommended to first verify them in the preview environment before executing in the production environment.