- 06 Sep 2024
- 2 Minutes to read
- Print
- PDF
Publish to Staging
- Updated on 06 Sep 2024
- 2 Minutes to read
- Print
- PDF
This is currently a limited availability feature.
Overview
Publish to Staging provides a way to validate an updated site configuration before publishing it to production.
After publishing to Staging, you can direct requests to the staging network by editing the host file on your local machine. Learn how.
When you're satisfied with the site configuration on staging, you can then publish it to production.
Publishing to staging does not affect traffic in production.
Limitations:
- Routing: Traditional routing to the staging environment is not available. To direct traffic to this site, in your host file, map the site hostname to the staging environment IP address. Learn how.
- Performance: The staging network is designed specifically for testing site configurations. It is not optimized for performance. Performance is not guaranteed on the staging environment.
- Observability: Requests to the staging network are not captured in the media delivery logs, or Qwilt reports and dashboards.
Publish a Site to Staging
To publish a site version to staging:
- Make sure the site you want to publish is saved. See Save a Site Configuration.
- Select the version from the Versions List. See Version Control.
- Select Publish and then Staging.
- See Publish a Site for further instruction.
Alternatively, use the Sites API to publish a specified configuration version to staging. Simply set the target attribute to staging.
Direct Traffic to the Site
To direct requests to the site on staging, edit the host file on your local machine to map the site hostname to this static IP: 35.234.109.253.
For example, if the site hostname is www.example.com, add the following line to the host file on your local computer:
35.234.109.253 www.example.com
In this example, an API request from the local machine to www.example.com would be directed to the staging server at 35.234.109.253 rather than to the production server.
Markers in the Site Configuration UI
Purple markers in the Site Confuration UI identify versions that are published to staging:
In the Publish History, each item specifies the target of the publishing operation, production or staging.
Linked Certificates
When a site is published, the linked certificate is published along with it, regardless of the publishing target.
To check the status of a linked certificate, open the Certificates tab. A linked certificate displays a Published for production or Published for staging label, or two dots if it's published for both. An unpublished certificate does not display a label.
Published for production:
Published for both: