> From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] > On Behalf Of Greg Keogh > Sent: Thursday, 28 January 2016 9:17 AM > To: ozDotNet <ozdotnet@ozdotnet.com> > Subject: Azure static web sites > > Folks, I was thinking of moving some of my old static web sites to Azure, > and I've noticed via links from others in here that they must doing this > already. It looks you don't actually "deploy" a static web site to Azure > (like an application), you just make a Blob container, upload the files and > make the container access public. A quick test confirms this works okay, but > there are some differences ... what's the equivalent of the old IIS log > files to track usage? And because it's not your own IIS, what's replaces > host headers so that someone going to www.mysite.com.au thinks they're at my > domain but in reality they're looking something like this: > > https://myaccount.blob.core.windows.net/web-mysite-com-au/index.htm > > You want to make visitors feel like they're at your domain, not some weird > Azure blob url.
On 28 January 2016 at 09:46, Andrew Coates (DX AUSTRALIA) <andrew.coa...@microsoft.com> wrote: > Is there a reason you’d want to do it this way rather than using a Web App? > Web apps will give you all of that (host headers, logging etc) as well as > reliability and scaling if need be. In what way is a Web App more reliable or scalable than blob storage? -- Thomas Koster
