Setting up Kentico+ Staging environment

If you use our SaaS solution Kentico+, you might be interested in configuring a Staging site for testing purposes before migrating your changes live.
Our recommended approach is to perform all the tests locally but if that is not an option for you, you can create another Kentico+ subscription with a new project which would serve as a staging environment – this can be done by following instructions in Kentico+ documentation – Creating subscriptions and projects.

After you have a new project created and initialized, you can export your production  site and import it to your staging instance. You may also want to configure content staging to enable synchronization of content changes between your staging and production site (Developer’s Guide – Staging configuration). If your K+ site is a managed project and still runs on version 7, you will need to take one extra step – that is synchronizing Microsoft.Web.Services3.dll to your designated blob storage and its ~/bin folder. You can simply create a new folder named "bin" in a cmscustomcode/managed container, copy the renamed DLL to this folder and synchronize the changes (Adding custom code files to managed projects). After getting through this step, you are good to go and the remaining configuration is not any different from standard Kentico projects hosted on-premise.
Share this article on   LinkedIn

Filip Ligač

Hi, I work as a Cloud Support Specialist here at Kentico. I write about Microsoft Azure and and am trying to extend knowledge about the best practices for deployment.