Because the Sitefinity .NET Core Renderer and Sitefinity CMS are two separate applications, the recommended way to store their code is to have two separate SCM repositories and have a Continuous Integration (CI) pipeline on each one of them. This article describes the continuous delivery and integration for the .NET Core Renderer. For more information about Sitefinity CMS, see Continuous delivery.
We recommend using a SCM system, such as GitHub, to store the code of the Renderer code. We also recommend setting up a CI pipeline setup that does the following things:
RECOMMENDATION: We recommend running E2E test on your Sitefinity CMS instance.
To setup integration and E2E tests on each build, we recommend using a live CMS instance to execute these against. Using this approach, you would get the latest changes from Sitefinity CMS itself and integrate them on a regular basis.
Following is the recommended approach for deploying and propagating your changes to the Live environment:
NOTE: Alternatively, Microsoft Windows users can work with their own local version of Sitefinity CMS, if it is more convenient for them.
RECOMMENDATION: Because this is a shared environment and everyone is polluting it with test data, we recommend redeploying the database on a regular basis. For example, redeploy it each night, so that the developers can start off clean the next day.
RECOMMENDATION: We recommend redeploying the Renderer application on a regular basis – for example, every night. This way, the latest changes to your master branch are deployed to this environment.
Restore the latest database to the Test environment to see the changes to Sitefinity CMS and the Renderer with the most current database.
After completing all tests on the Test environment, promote Sitefinity CMS and the Renderer application to the Live environment and connect the Renderer to Sitefinity CMS.
The following chart demonstrates the continuous delivery process of the Renderer application:
RECOMMENDATION: We recommend using a load balancer to manage the load of Sitefinity .NET Renderer, when you host the Renderer and Sitefinity CMS on your Live environment.
Additionally, you can configure the load balancer to act as an SSL offloader and further manage the load distribution across the Renderer instances.
For more information, see SSL offloading.
Тhe Renderer acts as an SSL offloader itself and forwards all the traffic as HTTP to Sitefinity CMS. In this case, to indicate this, the Renderer sends the following additional headers to Sitefinity CMS:
You must configure the same headers on the load balancer.
Following is a sample configuration for an NGINX load balancer configured with SSL, using a self-signed certificate for testing, under a Linux based OS:
Sign up for our free beginner training. Boost your credentials through advanced courses and certification. Register for Sitefinity training and certification.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important