The multiple environments feature allows you to duplicate the service configuration and create a completely isolated separate environment.
By utilizing this feature, you can safely make configuration changes to the service in production without any impact on the production environment, ensuring secure operations.
This feature is available in the Business and Enterprise plans for multiple environments.
For details on the features available in each plan, please visit the pricing page.
First, to create an environment, open the environment menu in the management screen.
When you press the [Create New] button, a dialog for creating an environment will appear.
When creating an environment, you need to specify the environment name (any string) and the range of content and media to copy.
The copy range has the following patterns.
In the created environment, all users will have "administrator privileges." (For restrictions in the created environment, please refer to the specifications mentioned later.)
Therefore, if there is information that should not be viewed, such as draft content, included in the production environment, please narrow down the copy range when creating the environment.
After entering the above, you can create the environment by pressing the [Create] button.
Created environments can be checked in the settings screen. You can also change the environment name and delete the environment on this screen.
The source for copying environments is only the production environment. You cannot perform copies like staging environment → development environment or staging environment → production environment.
When developing a new service, it is recommended to build based on the production environment and create a separate environment when necessary after the release.
For staging confirmation purposes, there is also a method using draft saving and draftKey. There are related articles on construction methods, so please utilize them as well.
The detailed specifications of the environment are as follows.
In the Enterprise plan, some restrictions may differ.
example, created environment example-0htwv5q6lmdmk0ze4l8o).To prevent data inconsistency, it is essential to copy the media when copying content.
(Note 2) Even if the media copy range is set to [Do not copy], the settings for the "Amazon S3 Integration" feature will be copied as default settings. For more information on handling the Amazon S3 integration feature across multiple environments, please refer to the "Amazon S3 Integration" documentation.
100 items.40MB.3.10 environments (excluding the production environment).To edit the display settings for the environment, click the three-dot icon on the right side of the environment settings and select [Edit Environment].
Only members with administrator privileges can make edits.
You can edit the environment name in the editing screen.
You can edit the label color in the editing screen.
The color selected here will be reflected at the top of the screen for the configured environment.
For example, if you change the label color to "Green," it will look like the image below.
Similar to editing the display settings for the environment, you can delete it by clicking the three-dot icon and selecting [Delete Environment].
When you press [Delete Environment], a dialog like the one below will appear. Please enter the environment name in the form, review the warning items, and proceed with the deletion.
When you delete an environment, all data related to that environment (including content, media, and all API data) will be completely removed. If you delete it by mistake, it cannot be restored from a backup.
Before deletion, please ensure that there is no necessary data remaining in the target environment.
To delete an environment, you must be a member with administrator privileges or have the permission to delete the environment.