Sitecore Serialization is a powerful capability to leverage with your DevOps pipelines. There are a ton of options beyond publishing via serialization, but for the sake of this article we will walk through one method of automating serialization via Azure DevOps and Sitecore Serialization. This has the following assumptions: Our step for Sitecore Serialization (using …
When leveraging Deployment Slots for your PaaS Sitecore environment you may want differing configs per Deployment Slot. This article discusses why you would want differing configs and how to setup custom config files so they are applied per Slot. This assumes you have a single deployment source that can be deployed across differing targets such …
Sitecore XM PaaS uses Redis for its Session State and it’s a common option to use Redis in this instance for Sitecore in other scenarios (ex. XP, XM on IaaS, etc.). However, what if you have custom objects that require shared storage? This is where adding a second Redis instance for your custom objects comes …
Solr is used to power both operational and custom search indexes in Sitecore, but there are times in which you may want to access this data outside the normal Sitecore usage. A few examples are as follows: You may have other needs, but the bottom line is that there are a few methods to directly …
Having a unified login experience where users can leverage their social logins and other providers is a highly desired feature for member and customer-based portals. Incorporating each separate authentication and authorization service on their own is a large and implicitly costly endeavor, especially when factoring in keeping connections up to date to meet the requirements …
The React framework continues to improve its Server Side Rendering capabilities, and with React 19, is introducing Server Components to further launch into the SSR space. With this in mind, do React Server Components and SSR options replace Next.js for Sitecore XM Cloud/Vercel hosted applications? Why Do We Need Server Side Rendering In its simplest …
When leveraging Deployment Slots as laid out in the Multisite Application Initialization for Zero Downtime Azure Deployments post, an issue kept arising on swap when we would see unhealthy instances and 500 errors. Digging into this, it was found that it was not swapping in bad or un-warmed up instances, rather it was experiencing SNAT …
By default, Sitecore sets the deletion of log files to 30 days but does not recurse the deletion. This may leave logs in place older than 30 days. Here is the section of the default Sitecore.config file that houses the Sitecore.Tasks.CleanupAgent: Note that this line is missing the recursive=”true” parameter. A patch file to remediate …
Obtaining Zero Downtime Deployments using Azure PaaS for Sitecore is achievable, even with a Multisite configuration, but requires some steps to avoid 500 errors and other aspects that may place your Azure Application Service Sitecore instances into rotation before they are ready. This article assumes you: How a Swap is Supposed to Work When swapping …
Ever want custom 500 error pages but struggle as you have a multisite solution? Here are 3 steps for creating Sitecore multisite custom 500 error pages. Step 1: Create Custom 500 HTML Pages and Place in wwwroot Step 1 is to create the custom 500 html error pages you want and to place them, and …