From c3bf7a0810475ea0d6c260eceb43eaf4fe3541e5 Mon Sep 17 00:00:00 2001 From: Jette <110890857+Jette94@users.noreply.github.com> Date: Thu, 24 Oct 2024 14:40:57 +0200 Subject: [PATCH 1/2] Update multisite-setup.md --- 14/umbraco-cms/tutorials/multisite-setup.md | 1 + 1 file changed, 1 insertion(+) diff --git a/14/umbraco-cms/tutorials/multisite-setup.md b/14/umbraco-cms/tutorials/multisite-setup.md index b68e34ed446..749f562164c 100644 --- a/14/umbraco-cms/tutorials/multisite-setup.md +++ b/14/umbraco-cms/tutorials/multisite-setup.md @@ -56,5 +56,6 @@ While such a setup might be handy, it also comes with drawbacks. It is important * Might increase resource usage. * Could interfere with editors' workflows, especially if there are multiple people working on both websites at once. That is because the solution will still use one database for both websites. * Limit your options in regards to developing new features and making schema changes. +* It should be noted, that if the project has any issues, this will effect all websites at once. On Umbraco Cloud-hosted sites we recommend using the [Baseline](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines) functionality - which comes with added benefits, and offers increased stability compared to the multisite solution in a single project. From 9943c57715c6c38bad04bb6111fb46acb54ed16a Mon Sep 17 00:00:00 2001 From: Jette <110890857+Jette94@users.noreply.github.com> Date: Thu, 24 Oct 2024 14:56:20 +0200 Subject: [PATCH 2/2] Update 14/umbraco-cms/tutorials/multisite-setup.md Co-authored-by: sofietoft --- 14/umbraco-cms/tutorials/multisite-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-cms/tutorials/multisite-setup.md b/14/umbraco-cms/tutorials/multisite-setup.md index 749f562164c..d29e8438b69 100644 --- a/14/umbraco-cms/tutorials/multisite-setup.md +++ b/14/umbraco-cms/tutorials/multisite-setup.md @@ -56,6 +56,6 @@ While such a setup might be handy, it also comes with drawbacks. It is important * Might increase resource usage. * Could interfere with editors' workflows, especially if there are multiple people working on both websites at once. That is because the solution will still use one database for both websites. * Limit your options in regards to developing new features and making schema changes. -* It should be noted, that if the project has any issues, this will effect all websites at once. +* If the project has any issues, this will affect all websites. On Umbraco Cloud-hosted sites we recommend using the [Baseline](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines) functionality - which comes with added benefits, and offers increased stability compared to the multisite solution in a single project.