I got a bit confused as explained below with steps:
I created a new umbraco solution locally
I published app to Azure (Using Web.config transformation for the Connection String)
I installed Umbraco locally w/ clean installation no Starter Kits
I installed Umbraco on Azure w/ clean installation no Starter Kits
I created a new Deployment Slot (selected copy settings from the production one)
I created a new Database to use for staging
I published files to Azure Staging (I have created a specific Web.config transformation for the Connection String)
Now, when I browse the staging website, Umbraco is already installed! How come? Did VS also publish the database when I published to Staging? Or did the deployment slot copy the database? Or what?
I noticed that this feature in VS to Publish SQL is disabled already.
However, I discovered that when I was creating a new staging DB on Azure, I chose to create a new DB out of Backup :). At that time I selected the production database! My bad.
So if I'm understanding correctly, the staging slot should have it's own DB and the production slot have its own DB? I currently have those two slots, but sharing a DB. I'm suspecting that that's why the examine indexes lock?
Hosting umbraco on Azure Production / Staging
Hi, I followed this post on how to install Umbraco locally, Azure production and Azure staging. https://sunithamk.wordpress.com/2015/08/05/using-umbraco-cms-with-multiple-environments-on-azure-app-service/
I got a bit confused as explained below with steps:
Now, when I browse the staging website, Umbraco is already installed! How come? Did VS also publish the database when I published to Staging? Or did the deployment slot copy the database? Or what?
Many thanks,
/Bilal
Hi Bilal,
Yes, you are right. VS publishes db, you can disable this functionality during the publishing.
Thanks,
Alex
Hi Alex.
I noticed that this feature in VS to Publish SQL is disabled already.
However, I discovered that when I was creating a new staging DB on Azure, I chose to create a new DB out of Backup :). At that time I selected the production database! My bad.
Thanks for support.
/Bilal
Glad to help you!
Have a nice day!
Thanks
So if I'm understanding correctly, the staging slot should have it's own DB and the production slot have its own DB? I currently have those two slots, but sharing a DB. I'm suspecting that that's why the examine indexes lock?
is working on a reply...