Last updated: Feb 04 2019
This topic explains the environments in Episerver Digital Experience Cloud Service, and their usage. The environments are used for publishing and testing of code, content and databases, to prepare for final deployment to a production site.
Depending on your DXC Service setup and products included, you will have two or more environments between which deployment is done. You can deploy to Integration, Preproduction, and Production yourself. See Deploying and DXC Service self-deployment guide.
Typical usage scenarios for the different environments are described below. The number of environments is based on the specific cloud package in your solution, see the Digital Experience Cloud Service Description for details.
- Integration. Partners and customers deploy the full solution, as daily builds or continuous releases. Here you can validate initial integrations with external systems, perform functional testing, and add initial content in the case of a first-time deployment. The integration environment has fixed configuration and no automatic scaling.
- Preproduction. This environment is used to test production deployment, and verify performance and operational functionality. Customers may also use it for UAT, load testing, or approved penetration testing. Preproduction scales automatically. Any content added in this environment will be overwritten during an upgrade.
- Production. This is the live environment. In Production, website users will perform authoring of content, using for example the Episerver content publishing flow or projects, and website visitors can access public content. The Production environment scales automatically.
Episerver Find is included by default in Episerver DXC Service. Each of the environments described above can be a multisite setup, and each of them will have their own Find index. In a multisite scenario the sites share the same index, but each individual site will have their own partition of the index, as well as a shared partition for shared content.
When deploying to a production environment, always ensure that the correct configurations are applied. See Environment configurations how to set up environment-specific configurations.
Note: Make sure you never use credentials, tokens or endpoints from a Preproduction environment, in a Production environment.