Sitefinity Cloud provides customers with Continuous Delivery (CD) setup consisting of two isolated environments - Production and Staging. This way code changes are first deployed to the Staging environment, where stakeholders verify the project and new functionality is working as expected and will not affect the production website. Once verified, the new functionality can be promoted to the Production environment. Promoting code to Production is made possible while maintaining the public website availability.

Production environment

In the Production environment, content editors are able to author content in an efficient and secure fashion, utilizing the Sitefinity content editing capabilities and content approval workflow. Website visitors can access the public content via the website public URL. The Production environment scales automatically to ensure optimal performance and high availability.

Deploying new functionality to Production is done via preconfigured deployment pipelines available in the Management Portal.

The following diagram visualizes the production environment workflow:


Staging environment

This environment is used by website stakeholders from the customer and partner teams, including business users and technical team like development and QAs. The environment is separated from Production and is designated for user acceptance testing (UAT). Unlike Production, which scales automatically, Staging consists of a static number of instances.

Deploying new functionality to Staging and then to Production is done via preconfigured deployment pipelines available in the Sitefinity Cloud Management Portal.StgEnv

Was this article helpful?