4

So what we are usually doing (and I have recently seen that others are doing this as well) is keeping a separate Infrastructure Solution. This is usually done when you have an Ops team in place and is responsible for keeping the Ops stuff of the solution (for example ARM Templates, Terraform files etc.). When you create such solution this becomes your main ...


4

There are automatic cleanup tasks in place to deal with that. Basically if you look under <scheduling> in a default Sitecore.config, you will find these. <agent type="Sitecore.Tasks.UrlAgent" method="Run" interval="00:15:00"> <param desc="url">/sitecore/service/keepalive.aspx</param> <LogActivity>true</LogActivity> &...


2

So something worth looking into with Azure deployments if you're using Web Deploy (for clean deployments) is to ensure that you handle the App_Data folder with care. For your Deploy Azure App Service Step, have a look at ticking the "ignore App_Data folder" option which will be in the settings for that task. Azure actually dumps a huge amount of small log ...


1

I would recommend that you exclude the Sitecore binaries from your deployment. This would prevent them from overwriting any existing Sitecore binaries, any Sitecore patch/hotfix binaries and also it stops errors happening when you might reference the wrong Nuget version of Sitecore and deploy... that is always fun. msbuild Ways to do this, depend a bit on ...


Only top voted, non community-wiki answers of a minimum length are eligible