0

Problem

There is lots of documentation on how to create an MVC Sitecore site with Docker and containers. But how would you recommend creating a multisite Sitecore site for a multitenant 8+ site topology?

Details

Currently we have 8+ tenancy sites that when compiled/deployed indivdually deploy to tenant virtual directories hosted with one IIS sitecore site. Included is a shared code library. It's close to the architecture outlined here: MVC Area + separate solution for each site copying only their site to their respective tenant folders.

This way if we need to make a change to just one site, only one site needs to be compiled / deployed because only that site has changed.

We're currently looking at migrating to containers, but because containers are immutable, we would not be able to do this from what I've seen. For every site deploy, we'd have to add every other site to the container, compiling each. This would drastically increase our build/deployment time.

Questions

  1. Are there any options out there for this?
  2. Does anyone have any references to multi tenant Sitecore container setups? I have not been able to much on this topic.
5
  • 1
    This link you are sharing is very old, modern Sitecore implementations using Helix principle - helix.sitecore.com , for reference you can see this example - github.com/Sitecore/Habitat . You don't need a separate solution for each module, just need separate web projects. Aug 13 at 4:12
  • Thanks! I had seen that. I know it's old, but that's what our company is using atm. But regardless of the sln setup, for a multisite sitecore site, what is the recommended way to containerize each site? @MahendraShekhawat
    – w00ngy
    Aug 13 at 15:46
  • 1
    Two things come to mind for me. The disconnected solutions could all be brought together into a single solution that has a single output. Another option may be to checkout and compile each solution independently, but take the outputs and layer them together as a single artifact. This artifact could then possibly be used to build up the container image. Aug 13 at 18:15
  • @DylanMcCurry I had similar thoughts. Might be able to build separate images for each site and cache them. Then each solution build could check to see if the tenancy images have changed and if not just use those images to build off of to create the final image.
    – w00ngy
    Aug 13 at 19:01
  • Use SXA for sitecore multi tenant implementations doc.sitecore.com/en/developers/sxa/17/… Nov 7 at 11:12

Your Answer

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

Browse other questions tagged or ask your own question.