Are there side effects to pointing multiple Umbraco instances (of the same version) to the same database?
The reason I ask is we'd like to use a staging instance in an Azure deployment slot - usually we clone the existing database and make the live instance read only until the staging slot is verified and swapped into live.
On this occasion there are only internal code / view changes, no database changes so wanted to know if we can avoid the read only step, verify staging and then swap it into live without anything more than a log out being required for our editors.
There is no problem with that at all (we do it frequently). You need to ensure that Umbraco is never accessed from multiple locations (e.g. a deployment slot and live) at the same time.
Multiple front-ends pointing at same database
Hi everyone
Are there side effects to pointing multiple Umbraco instances (of the same version) to the same database?
The reason I ask is we'd like to use a staging instance in an Azure deployment slot - usually we clone the existing database and make the live instance read only until the staging slot is verified and swapped into live.
On this occasion there are only internal code / view changes, no database changes so wanted to know if we can avoid the read only step, verify staging and then swap it into live without anything more than a log out being required for our editors.
We're using Umbraco 7.6.4 if it's significant
Hi Dan,
There is no problem with that at all (we do it frequently). You need to ensure that Umbraco is never accessed from multiple locations (e.g. a deployment slot and live) at the same time.
Jeavon
is working on a reply...