Learn how to create and use a production workspace.
Production workspaces are ready to handle live traffic. This guide provides step-by-step instructions on creating and managing a Production workspace.
Production workspaces serve multiple purposes, including quality assurance, testing, running A/B tests, and validating VTEX IO apps. It's important to note that for making changes or developing a new VTEX IO app, you must use a Development workspace.
Creating a production workspace
- Log in to your VTEX account.
- Create a production workspace by running the following command:
_10vtex use {workspaceName} --production
Replace
{workspaceName}according to your scenario.
Next steps
After testing your app and configurations, you can promote a Production workspace to Master to make your code changes available to the end-user.
Creating a Production workspace is one of the steps to making your code's new version public. Refer to the Making your new app version publicly available guide for detailed information on subsequent steps.
Deleting a workspace
You can manually delete workspaces that are no longer in use by running the following command:
_10vtex workspace delete {workspaceName}
Deleting a workspace is irreversible, and its content cannot be restored.
Production workspace behavior
In Production workspaces, certain actions are permitted while others are restricted to maintain stability and reliability. Here is a summary of allowed and restricted actions:
| Action | Allowed |
|---|---|
| Install apps. | ✅ |
| Run A/B tests. | ✅ |
| Handle traffic. | ✅ |
| Promote to master. | ✅ |
| App development. | ❌ |
| Link an app. | ❌ |
| Publish an app. | ❌ |
Key considerations
- Code modifications: Production workspaces strictly prohibit code changes in VTEX IO apps. To implement code modifications, it is necessary to switch to a dedicated Development workspace.
- Workspace inheritance: Production workspaces are initiated independently and do not inherit code changes from a Development workspace. Therefore, any modifications made in a Development workspace must be manually replicated to the new Production workspace.
- Data persistency: Workspace settings persist unless conflicts arise with the Master workspace. In such cases, Master settings take precedence over settings in other workspaces, including the Development ones.
- Expiration: Once created, Production workspaces have no expiration date.
- Deletion: Unused workspaces are not automatically deleted. It is recommended to perform manual deletion to optimize platform resources and maintain an efficient operational state.
- Organization: Maintain a concise list of workspaces for organizational and resource efficiency reasons.