>> In what way is a Web App more reliable or scalable than blob storage?
Fair enough, That's actually a really interesting question. I guess I was thinking along the lines of you having more explicit control through the web apps front end on the portal. You can assign multiple instances to the web app, automatically scale it (up and down) based on usage and so on. I haven't previously considered serving a whole static site from blob storage, mainly because that's exactly what web apps are designed to do, serve a whole site, rather than individual components. Now that I think about it some more, it's not necessarily *more* reliable or scalable. Let's stick with the web app is designed to do what Greg K's after and has all of the what Greg L calls "niceness" on top of that. Cheers Andrew Coates, ME, MCPD, MCSD MCTS, Developer Evangelist, Microsoft, 1 Epping Road, NORTH RYDE NSW 2113 Ph: +61 (2) 9870 2719 • Mob +61 (416) 134 993 • Fax: +61 (2) 9870 2400 • http://blogs.msdn.com/acoat -----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Thomas Koster Sent: Thursday, 28 January 2016 10:50 AM To: ozDotNet <ozdotnet@ozdotnet.com> Subject: Re: Azure static web sites > 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 > https://na01.safelinks.protection.outlook.com/?url=www.mysite.com.au&data=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c813eee3f349a4ccaa5bc08d32774a45c%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=JbWhn5o0JG4VmyojpJN5S2N1laVyC7CAijHmO%2fpTNIQ%3d > thinks they're at my domain but in reality they're looking something like > this: > > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fmyacc > ount.blob.core.windows.net%2fweb-mysite-com-au%2findex.htm&data=01%7c0 > 1%7cACOAT%40064d.mgd.microsoft.com%7c813eee3f349a4ccaa5bc08d32774a45c% > 7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=OgSoCiMrach6928hOs2hnn2a1 > CQ7BFC75Lu%2bg3WnHww%3d > > 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
