Assume the hotfix contains both files and items. If the hotfix is installed via the Sitecore shell, it works as expected until the next build where some or all of the dlls are replaced with the the original files. In order to get the hotfix dlls to stick, it seems that the hotfix must be added to the image itself. What is the best practice method of doing this? This sitecore doc says...

There is a dedicated layer for you to make hotfixes or future customizations in.

But no elaboration on how that is performed. Currently using SC9.3


If the hotfix contains both files and items, I think it should be installed as if it were a module, following the documented approach in the Add Sitecore Modules section of the Sitecore official documentation.

This approach requires a module to be distributed as asset image. For a normal Sitecore package, you will need to convert it to a web deploy package (WDP) first and then create an asset image for it. The steps to convert a .update Sitecore package to a WDP package are described here. A good tutorial to create an asset image starting from a WDP package is described in this blog post here instead.

Additional Production Considerations

To promote the hotfix to a containerized Kubernetes Sitecore application in production, you will need to implement an additional mssql-init data initialization container to use with a Kubernetes job to deploy the items of the hotfix in the production SQL databases. I recently described the concept and this approach in a blog post here.

  • Hi, thank you for the detailed response. Does this process apply for both 9.3 and 10.1 ? Mar 23 at 11:34
  • 1
    Hi @PaulGeorge, this process applies to both in general, but the available tool powershell scripts in the images between these SC versions are different. The SC 9.3 community images don't have the same scripts available in the official SC 10.x images. For example, the community SQL image contains a script called Install-Databases.ps1 to publish a dacpac file to a SQL server, while a similar script is called DeployDatabases.ps1 in the SC 10 MSSQL image. Mar 23 at 11:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.