In this topic
You can deploy solutions from your development environment to the Integration environment, as daily builds or continuous releases. When you are ready to go live, you can deploy to Preproduction and Production through the DXC Service Management Portal. This involves creating a backup of the existing environment, and moving the code to Preproduction, where you can verify that everything works.
Episerver takes care of the the following as part of the service:
The following image illustrates a first-time deployment from a local development environment to Production. In this scenario the production environment is "empty" at the beginning. You first create code and content in your local development environment, and then push this to your Integration environment. You then deploy to Preproduction and validate that everything works as expected. When ready, you can deploy to Production.
The following image illustrates the scenario after a first-time deployment of code and content to production. After the first deployment, website users edit content in the Production environment. As part of the upgrade process, content can be moved by Episerver from Production back to the Preproduction and Integration environments, where new solution updates are added by developers. See Deploying code changes.
You can deploy either using deployment tools for a version-controlled team development environment, or through Visual Studio using the Episerver extensions and publish profiles. In both cases you need to contact Episerver before you deploy for the first time, to get the needed deployment integration settings information.
Note: Read through and follow the recommendations below, to make deployment as smooth as possible!
Note: If your changes are additive and do not break the sites when the old and the new code runs in parallel during deployment, you can deploy without using maintenance page.
Last updated: Feb 04, 2019