Is it possible to have a multisite Umbraco 8 where each site is set up as an individual IIS site? We want each site run in a different application pool rather than having a unique pool with multiple domains, to subdivide resources consumption and achieve better scalability. We want to create an IIS website for each domain and then point all the sites to the same Umbraco installation, the same server folder.
We already have a similar setup for an application running more than 50 sites with Umbraco 7 and we want to replicate this architecture with Umbraco 8.
I’m writing this post because we are experiencing some problems with Examine/Lucene indexes. We are actually running Umbraco 8 in a setup with three root nodes with different domains and we found this issue.
This comment warned us about the feasibility of this architecture.
You can't have more than one IIS site pointing at the same folder.
But if you can live with having a folder for each site (and a virtual directory for media, so it's shared across sites), then you can get close. It's basically like loadbalancing.
Make sure the backoffice can only be accessed from one site though.
The configuration suggested by Claudio seems to work correctly. Each virtual directory for App_Data/TEMP contains a separate version of the ExamineIndexes directory. The indexes are now created separately and there are no more errors related to concurrent accesses.
Are there any other problems with this setup that we are not considering?
wouldn't be possible to have different IIS websites pointing at same folder but configuring (for each site) a virtual directory "app_data/temp" that separates the Lucene files between sites? Couldn't it work to avoid file locks or similar issues?
Umbraco 8 multisite setup
Is it possible to have a multisite Umbraco 8 where each site is set up as an individual IIS site? We want each site run in a different application pool rather than having a unique pool with multiple domains, to subdivide resources consumption and achieve better scalability. We want to create an IIS website for each domain and then point all the sites to the same Umbraco installation, the same server folder.
We already have a similar setup for an application running more than 50 sites with Umbraco 7 and we want to replicate this architecture with Umbraco 8.
I’m writing this post because we are experiencing some problems with Examine/Lucene indexes. We are actually running Umbraco 8 in a setup with three root nodes with different domains and we found this issue. This comment warned us about the feasibility of this architecture.
You can't have more than one IIS site pointing at the same folder.
But if you can live with having a folder for each site (and a virtual directory for media, so it's shared across sites), then you can get close. It's basically like loadbalancing.
Make sure the backoffice can only be accessed from one site though.
https://our.umbraco.com/Documentation/Fundamentals/Setup/Server-Setup/Load-Balancing/
The configuration suggested by Claudio seems to work correctly. Each virtual directory for
App_Data/TEMPcontains a separate version of theExamineIndexesdirectory. The indexes are now created separately and there are no more errors related to concurrent accesses.Are there any other problems with this setup that we are not considering?
wouldn't be possible to have different IIS websites pointing at same folder but configuring (for each site) a virtual directory "app_data/temp" that separates the Lucene files between sites? Couldn't it work to avoid file locks or similar issues?
is working on a reply...