Manage Configured Commerce sandbox websites
Note
This process is self-service and is not supported by the Optimizely support team. You need access to Mission Control to manage sandbox websites. For information on gaining access, see Mission Control accessMission Control access.
Production website management is not available within Mission Control and requires an Optimizely support ticket. For more information, see Add additional websites to a cloud projectAdd additional websites to a cloud project.
Mission Control lets you add websites, archive existing websites, and update Spire blueprints for Configured Commerce sandbox instances.
To manage websites and view existing configuration, go to the Websites tab on the Instance Details page for the target sandbox. This page shows all websites for the instance, both active and archived.
Important
After completing any of the actions within this article, you must redeploy your base code for the changes to take effect.
Add a website
To add a website to a Configured Commerce sandbox instance:
- On the Websites tab of the Instance Details page, click Add Website.
- Enter the following details for the new website:
- Website Name (Key) – The unique identifier for the website. The name must meet the following requirements:
- Maximum of 54 characters
- Lowercase alphanumeric characters and hyphens only
- Must begin and end with an alphanumeric character
- CMS Type – The content management system for the website. Available options are Spire, Classic, and Headless. Optimizely strongly recommends Spire or Headless unless Classic is required for your use case.
- Theme – The Spire blueprint for the website. Required for Spire CMS type only. The theme must be built in the associated repository before it can be selected here. For more information, see Change a blueprint.
- Primary Website – Indicates whether the website is the primary website for the instance. Set to true for the main website. Every Configured Commerce instance requires exactly one primary website.
Note
Changing the primary website can disrupt the application as it will change the Website URL from: {instanceIdentifier}.insite... to: {websiteKey}-{instanceIndentifier}.insite...
- Click Save.
- Redeploy your base code for the changes to take effect. The new website will be added to the instance as part of the next deployment.
Note
Each additional website on an instance increases deployment time. The more websites configured for an instance, the longer deployments take.
Archive a website
Archiving a website removes it from deployment without permanently deleting it. The website remains visible in the Websites tab and can be restored at any time.
Note
Websites cannot be permanently deleted. Archiving is the only way to remove a website from deployment.
- On the Websites tab of the Instance Details page, locate the website to archive.
- Click Archive.
- Type the Website Name and click Archive to confirm the action.
- Redeploy your base code for the changes to take effect. The website status changes to archived and is excluded from future deployments.
Enable a website
Once a website has been archived, you can restore it using the following steps:
- On the Websites tab of the Instance Details page, locate the website to archive.
- Click Enable.
- Type the Website Name and click Enable to confirm the action.
- Redeploy your base code for the changes to take effect. The website status changes to enabled and is included in future deployments.
Change a blueprint
A blueprint determines the Spire storefront design for a website. Blueprints only apply to websites that use the Spire CMS type.
Before changing the blueprint for a website, build the new blueprint in the associated repository.
- On the Websites tab of the Instance Details page, locate the website to update.
- Click the Website Name to edit the website.
- In the Theme drop-down list, select the new blueprint.
- Click Save.
- Redeploy your base code for the changes to take effect.