RE: Azure static web sites

[David Smith]

Hi Greg,

As an aside, these “Website” projects are really a simple compile on demand 
project type.
You optionally have web.config, a bin folder to drop pre-compiled assemblies 
into, an App_Code folder for code.

We use this project type for our non mvc web projects because for us, it allows 
us to work faster, no having to run, find bug, stop, edit, compile and re-run, 
it simply becomes run, find bug, edit, refresh

David

From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On 
Behalf Of Andrew Coates (DX AUSTRALIA)
Sent: Thursday, 28 January 2016 8:14 p.m.
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: RE: Azure static web sites

https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/

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

From: ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com> 
[mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh
Sent: Thursday, 28 January 2016 2:13 PM
To: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>
Subject: Re: Azure static web sites

I could do a quick walkthrough later today if that’d help. There aren’t many 
options that need to be chosen.

That'd be great if you have a break. Only the skeleton of the steps should get 
me going. Once I get the files in the right sort of project and deploy with 
suitable settings I should be able to extrapolate and find all the 
configuration stuff about host headers and DNS and the like. I'll make a blog 
post after I get it all working -- Greg K

RE: Azure static web sites

[Andrew Coates (DX AUSTRALIA)]

BTW, there are lots of ways to deploy your static site (it doesn’t have to be 
VS)

https://azure.microsoft.com/en-us/documentation/articles/web-sites-deploy/

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

From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On 
Behalf Of Greg Keogh
Sent: Friday, 29 January 2016 10:52 AM
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: Re: Azure static web sites

Andrew, Greg L et al, now my broadband has returned to full speed I followed 
the instructions and have a static site up on Azure okay. It's clear now why my 
initial attempt yesterday morning went haywire ... I tried to create a solution 
and project to contain the static site. It turns out you "Open Web Site", which 
I never tried because it was counterintuitive to normal VS2015 usage. Then I 
wasn't sure what sort of Azure "publish target" to use, as the choice of "App 
Service" sounds inappropriate, but it's not!

I'm not sure how to use plans. Do I group similar sites and apps within the 
same plan? I haven't worked out a convention for their use yet.

Every deploy I've tried produces the "Can't find existing loaded project" 
error, so the hint about opening the View > Other Windows > Web Publish 
Activity window and clicking the tiny button to continue was vitally important. 
I reckon it would have taken an hour to jump that hurdle that without help.

So overall, it works easily (once you know the tricks) and I can see the static 
site nicely at 
http://myname.azurewebsites.net<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fazurewebsites.net=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c900d79c2c3c540ae923208d3283e126f%7c72f988bf86f141af91ab2d7cd011db47%7c1=rjx35Jd%2b9a8QU%2buKTuukez259aWgikA3ttgqFX6xg%2bc%3d>.
 All I have to figure out now it how to fiddle DNS and the like so that the 
world sees my com.au domain name pointing to this Azure web.

Greg K

On 28 January 2016 at 18:13, Andrew Coates (DX AUSTRALIA) 
<andrew.coa...@microsoft.com<mailto:andrew.coa...@microsoft.com>> wrote:
https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fblogs.msdn.microsoft.com%2facoat%2f2016%2f01%2f28%2fpublish-a-static-web-site-using-azure-web-apps%2f=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c900d79c2c3c540ae923208d3283e126f%7c72f988bf86f141af91ab2d7cd011db47%7c1=0YsIAEAgJ1tnShFaZAD65toxmtMlUVrvqVynQnHxYBQ%3d>

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<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fblogs.msdn.com%2facoat=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c900d79c2c3c540ae923208d3283e126f%7c72f988bf86f141af91ab2d7cd011db47%7c1=EIBjruipFG5x5pM3FNY%2fKkZ9u%2fxcPhmYl4r1xkDn2zU%3d>

From: ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com> 
[mailto:ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com>] On 
Behalf Of Greg Keogh
Sent: Thursday, 28 January 2016 2:13 PM
To: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>
Subject: Re: Azure static web sites

I could do a quick walkthrough later today if that’d help. There aren’t many 
options that need to be chosen.

That'd be great if you have a break. Only the skeleton of the steps should get 
me going. Once I get the files in the right sort of project and deploy with 
suitable settings I should be able to extrapolate and find all the 
configuration stuff about host headers and DNS and the like. I'll make a blog 
post after I get it all working -- Greg K

RE: Azure static web sites

[Andrew Coates (DX AUSTRALIA)]

App Service Plan details

https://azure.microsoft.com/en-us/documentation/articles/azure-web-sites-web-hosting-plans-in-depth-overview/

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

From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On 
Behalf Of Greg Keogh
Sent: Friday, 29 January 2016 10:52 AM
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: Re: Azure static web sites

Andrew, Greg L et al, now my broadband has returned to full speed I followed 
the instructions and have a static site up on Azure okay. It's clear now why my 
initial attempt yesterday morning went haywire ... I tried to create a solution 
and project to contain the static site. It turns out you "Open Web Site", which 
I never tried because it was counterintuitive to normal VS2015 usage. Then I 
wasn't sure what sort of Azure "publish target" to use, as the choice of "App 
Service" sounds inappropriate, but it's not!

I'm not sure how to use plans. Do I group similar sites and apps within the 
same plan? I haven't worked out a convention for their use yet.

Every deploy I've tried produces the "Can't find existing loaded project" 
error, so the hint about opening the View > Other Windows > Web Publish 
Activity window and clicking the tiny button to continue was vitally important. 
I reckon it would have taken an hour to jump that hurdle that without help.

So overall, it works easily (once you know the tricks) and I can see the static 
site nicely at 
http://myname.azurewebsites.net<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fazurewebsites.net=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c900d79c2c3c540ae923208d3283e126f%7c72f988bf86f141af91ab2d7cd011db47%7c1=rjx35Jd%2b9a8QU%2buKTuukez259aWgikA3ttgqFX6xg%2bc%3d>.
 All I have to figure out now it how to fiddle DNS and the like so that the 
world sees my com.au domain name pointing to this Azure web.

Greg K

On 28 January 2016 at 18:13, Andrew Coates (DX AUSTRALIA) 
<andrew.coa...@microsoft.com<mailto:andrew.coa...@microsoft.com>> wrote:
https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fblogs.msdn.microsoft.com%2facoat%2f2016%2f01%2f28%2fpublish-a-static-web-site-using-azure-web-apps%2f=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c900d79c2c3c540ae923208d3283e126f%7c72f988bf86f141af91ab2d7cd011db47%7c1=0YsIAEAgJ1tnShFaZAD65toxmtMlUVrvqVynQnHxYBQ%3d>

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<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fblogs.msdn.com%2facoat=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c900d79c2c3c540ae923208d3283e126f%7c72f988bf86f141af91ab2d7cd011db47%7c1=EIBjruipFG5x5pM3FNY%2fKkZ9u%2fxcPhmYl4r1xkDn2zU%3d>

From: ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com> 
[mailto:ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com>] On 
Behalf Of Greg Keogh
Sent: Thursday, 28 January 2016 2:13 PM
To: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>
Subject: Re: Azure static web sites

I could do a quick walkthrough later today if that’d help. There aren’t many 
options that need to be chosen.

That'd be great if you have a break. Only the skeleton of the steps should get 
me going. Once I get the files in the right sort of project and deploy with 
suitable settings I should be able to extrapolate and find all the 
configuration stuff about host headers and DNS and the like. I'll make a blog 
post after I get it all working -- Greg K

RE: Azure static web sites

[Andrew Coates (DX AUSTRALIA)]

Instructions for adding your custom domain here:

https://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/

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

From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On 
Behalf Of Greg Keogh
Sent: Friday, 29 January 2016 10:52 AM
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: Re: Azure static web sites

Andrew, Greg L et al, now my broadband has returned to full speed I followed 
the instructions and have a static site up on Azure okay. It's clear now why my 
initial attempt yesterday morning went haywire ... I tried to create a solution 
and project to contain the static site. It turns out you "Open Web Site", which 
I never tried because it was counterintuitive to normal VS2015 usage. Then I 
wasn't sure what sort of Azure "publish target" to use, as the choice of "App 
Service" sounds inappropriate, but it's not!

I'm not sure how to use plans. Do I group similar sites and apps within the 
same plan? I haven't worked out a convention for their use yet.

Every deploy I've tried produces the "Can't find existing loaded project" 
error, so the hint about opening the View > Other Windows > Web Publish 
Activity window and clicking the tiny button to continue was vitally important. 
I reckon it would have taken an hour to jump that hurdle that without help.

So overall, it works easily (once you know the tricks) and I can see the static 
site nicely at 
http://myname.azurewebsites.net<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fazurewebsites.net=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c900d79c2c3c540ae923208d3283e126f%7c72f988bf86f141af91ab2d7cd011db47%7c1=rjx35Jd%2b9a8QU%2buKTuukez259aWgikA3ttgqFX6xg%2bc%3d>.
 All I have to figure out now it how to fiddle DNS and the like so that the 
world sees my com.au domain name pointing to this Azure web.

Greg K

On 28 January 2016 at 18:13, Andrew Coates (DX AUSTRALIA) 
<andrew.coa...@microsoft.com<mailto:andrew.coa...@microsoft.com>> wrote:
https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fblogs.msdn.microsoft.com%2facoat%2f2016%2f01%2f28%2fpublish-a-static-web-site-using-azure-web-apps%2f=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c900d79c2c3c540ae923208d3283e126f%7c72f988bf86f141af91ab2d7cd011db47%7c1=0YsIAEAgJ1tnShFaZAD65toxmtMlUVrvqVynQnHxYBQ%3d>

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<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fblogs.msdn.com%2facoat=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c900d79c2c3c540ae923208d3283e126f%7c72f988bf86f141af91ab2d7cd011db47%7c1=EIBjruipFG5x5pM3FNY%2fKkZ9u%2fxcPhmYl4r1xkDn2zU%3d>

From: ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com> 
[mailto:ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com>] On 
Behalf Of Greg Keogh
Sent: Thursday, 28 January 2016 2:13 PM
To: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>
Subject: Re: Azure static web sites

I could do a quick walkthrough later today if that’d help. There aren’t many 
options that need to be chosen.

That'd be great if you have a break. Only the skeleton of the steps should get 
me going. Once I get the files in the right sort of project and deploy with 
suitable settings I should be able to extrapolate and find all the 
configuration stuff about host headers and DNS and the like. I'll make a blog 
post after I get it all working -- Greg K

Re: Azure static web sites

[Greg Keogh]

>
> BTW, there are lots of ways to deploy your static site (it doesn’t have to
> be VS)
>

Yes, I just created a Web App manually in the portal, then used FTP from
Expression Web 4, which might be preferable for my workflow -- *GK*

Re: Azure static web sites

[Greg Keogh]

Andrew, Greg L et al, now my broadband has returned to full speed I
followed the instructions and have a static site up on Azure okay. It's
clear now why my initial attempt yesterday morning went haywire ... I tried
to create a solution and project to contain the static site. It turns out
you "Open Web Site", which I never tried because it was counterintuitive to
normal VS2015 usage. Then I wasn't sure what sort of Azure "publish target"
to use, as the choice of "App *Service*" sounds inappropriate, but it's not!

I'm not sure how to use *plans*. Do I group similar sites and apps within
the same *plan*? I haven't worked out a convention for their use yet.

Every deploy I've tried produces the "Can't find existing loaded project"
error, so the hint about opening the View > Other Windows > Web Publish
Activity window and clicking the tiny button to continue was vitally
important. I reckon it would have taken an hour to jump that hurdle that
without help.

So overall, it works easily (once you know the tricks) and I can see the
static site nicely at http://*myname*.azurewebsites.net. All I have to
figure out now it how to fiddle DNS and the like so that the world sees my
com.au domain name pointing to this Azure web.

*Greg K*

On 28 January 2016 at 18:13, Andrew Coates (DX AUSTRALIA) <
andrew.coa...@microsoft.com> wrote:

>
> https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/
>
>
>
> 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
>
>
>
> *From:* ozdotnet-boun...@ozdotnet.com [mailto:
> ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Greg Keogh
> *Sent:* Thursday, 28 January 2016 2:13 PM
> *To:* ozDotNet <ozdotnet@ozdotnet.com>
> *Subject:* Re: Azure static web sites
>
>
>
> I could do a quick walkthrough later today if that’d help. There aren’t
> many options that need to be chosen.
>
>
>
> That'd be great if you have a break. Only the skeleton of the steps should
> get me going. Once I get the files in the right sort of project and deploy
> with suitable settings I should be able to extrapolate and find all the
> configuration stuff about host headers and DNS and the like. I'll make a
> blog post after I get it all working -- *Greg K*
>

Re: Azure static web sites

[罗格雷格博士]

Saved me a job thanks Andrew !

Regards

Greg

Dr Greg Low
SQL Down Under
+61 419201410
1300SQLSQL (1300775775)

On 28 Jan 2016, at 6:22 PM, Greg Keogh 
> wrote:

https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/

Oooh! I'll run through that later tonight. I think some of my screens were 
different when I tried similar initial steps, but I'll find out ... Ta, Greg

Re: Azure static web sites

[Greg Keogh]

I'm trying to publish a static site now using Andrew's notes, but Telstra
throttled back our speed because we passed our monthly quota, then we
applied for our first free "top up" for the remaining week, but that seems
to have made it even slower. It's slower now than when I first used a modem
back in 1993. In fact, it might be slower than two tin cans connected with
a string. I'll have another bash in the morning, but I can see immediately
that the first step was where I went wrong ... I never thought of going
File > Open > Web Site and opening a plain folder of static files. So my
attempts went downhill from there. Having a dummy solution with files and
no project runs contrary to traditional usage of the tools for me, but the
steps from there on look sensible and will probably work -- *Greg K*

On 28 January 2016 at 21:38, David Connors  wrote:

> [image: pasted1]
> On Thu, 28 Jan 2016 at 19:11 Greg Low (罗格雷格博士)  wrote:
>
>> Saved me a job thanks Andrew !
>>
>> Regards
>>
>> Greg
>>
>> Dr Greg Low
>> SQL Down Under
>> +61 419201410
>> 1300SQLSQL (1300775775)
>>
>> On 28 Jan 2016, at 6:22 PM, Greg Keogh  wrote:
>>
>>
>>> https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/
>>>
>>
>> Oooh! I'll run through that later tonight. I think some of my screens
>> were different when I tried similar initial steps, but I'll find out ... *Ta,
>> Greg*
>>
>> --
> David Connors
> da...@connors.com | @davidconnors | LinkedIn | +61 417 189 363
>

Re: Azure static web sites

[David Connors]

[image: pasted1]
On Thu, 28 Jan 2016 at 19:11 Greg Low (罗格雷格博士)  wrote:

> Saved me a job thanks Andrew !
>
> Regards
>
> Greg
>
> Dr Greg Low
> SQL Down Under
> +61 419201410
> 1300SQLSQL (1300775775)
>
> On 28 Jan 2016, at 6:22 PM, Greg Keogh  wrote:
>
>
>> https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/
>>
>
> Oooh! I'll run through that later tonight. I think some of my screens were
> different when I tried similar initial steps, but I'll find out ... *Ta,
> Greg*
>
> --
David Connors
da...@connors.com | @davidconnors | LinkedIn | +61 417 189 363

RE: Azure static web sites

[Andrew Coates (DX AUSTRALIA)]

>> 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=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c813eee3f349a4ccaa5bc08d32774a45c%7c72f988bf86f141af91ab2d7cd011db47%7c1=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=01%7c0
> 1%7cACOAT%40064d.mgd.microsoft.com%7c813eee3f349a4ccaa5bc08d32774a45c%
> 7c72f988bf86f141af91ab2d7cd011db47%7c1=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

RE: Azure static web sites

[罗格雷格博士]

I was thinking the same. I’d just create a web app and deploy it, even if it 
had a whole bunch of static content. By doing that, you pick up all the 
niceness.

Regards,

Greg

Dr Greg Low

1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax
SQL Down Under | Web: www.sqldownunder.com<http://www.sqldownunder.com/>

From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On 
Behalf Of Andrew Coates (DX AUSTRALIA)
Sent: Thursday, 28 January 2016 9:47 AM
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: RE: Azure static web sites

Hi Greg,

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.

Cheers,

Coatsy

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

From: ozdotnet-boun...@ozdotnet.com<mailto: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<mailto: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<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.mysite.com.au=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c4f9e6d4075b1475e87b508d327679ac3%7c72f988bf86f141af91ab2d7cd011db47%7c1=mYNnU%2bcr0DVJGvpjxBQ8iSYmKByEjz9Omrihpxs6rB4%3d>
 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<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fmyaccount.blob.core.windows.net%2fweb-mysite-com-au%2findex.htm=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c4f9e6d4075b1475e87b508d327679ac3%7c72f988bf86f141af91ab2d7cd011db47%7c1=5HYukAO3huVyWpSDNDz3wk3bu1mnRQ8O3JoTFAQ6mj8%3d>

You want to make visitors feel like they're at your domain, not some weird 
Azure blob url.

Greg K

RE: Azure static web sites

[罗格雷格博士]

:-)

Yep niceness includes all the config stuff that it makes really easy.

And it's a whole world of easier to do and portable.

* Shared site with host headers - check
* Free option for really little sites - check
* Custom domain - check
* Automated help with DNS configuration - check
* Makes it trivial to do SSL, etc. - check

And so on and so on.

Regards,

Greg

Dr Greg Low

1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax 
SQL Down Under | Web: www.sqldownunder.com

-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On 
Behalf Of Andrew Coates (DX AUSTRALIA)
Sent: Thursday, 28 January 2016 11:48 AM
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: RE: Azure static web sites

>> 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=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c813eee3f349a4ccaa5bc08d32774a45c%7c72f988bf86f141af91ab2d7cd011db47%7c1=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=01%7c0
> 1%7cACOAT%40064d.mgd.microsoft.com%7c813eee3f349a4ccaa5bc08d32774a45c%
> 7c72f988bf86f141af91ab2d7cd011db47%7c1=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

Re: Azure static web sites

[Greg Keogh]

I had a quick experiment with the web app idea for static content. I can't
figure out what sort of app to create or what do with the vast baggage of
references and support files that come with most default VS2015 projects.
I'm not even sure if I should use VS2015 for this, but it does have deploy
wizards. It's like mixing oil and water with an app and static content.
Then while trying to deploy I created entries in my Azure resource list
that I can't figure out how to delete, or even exactly what they are. So
the quick experiment is an utter failure. If anyone has done this and knows
what tools and settings to use to make it a smooth process, then I'm keen
to hear about it -- *Greg*

On 28 January 2016 at 10:09, Greg Low (罗格雷格博士)  wrote:

> I was thinking the same. I’d just create a web app and deploy it, even if
> it had a whole bunch of static content. By doing that, you pick up all the
> niceness.
>
>
>
> 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.
>

Re: Azure static web sites

[David Connors]

On Thu, 28 Jan 2016 at 10:59 Greg Keogh  wrote:

> I had a quick experiment with the web app idea for static content. I can't
> figure out what sort of app to create or what do with the vast baggage of
> references and support files that come with most default VS2015 projects.
> I'm not even sure if I should use VS2015 for this, but it does have deploy
> wizards. It's like mixing oil and water with an app and static content.
> Then while trying to deploy I created entries in my Azure resource list
> that I can't figure out how to delete, or even exactly what they are. So
> the quick experiment is an utter failure. If anyone has done this and knows
> what tools and settings to use to make it a smooth process, then I'm keen
> to hear about it -- *Greg*
>

If it is just static content you can deploy via FTP.

David.

-- 
David Connors
da...@connors.com | @davidconnors | LinkedIn | +61 417 189 363

RE: Azure static web sites

[罗格雷格博士]

I could do a quick walkthrough later today if that’d help. There aren’t many 
options that need to be chosen.

Regards,

Greg

Dr Greg Low

1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax
SQL Down Under | Web: www.sqldownunder.com<http://www.sqldownunder.com/>

From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On 
Behalf Of David Connors
Sent: Thursday, 28 January 2016 1:19 PM
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: Re: Azure static web sites

On Thu, 28 Jan 2016 at 10:59 Greg Keogh 
<gfke...@gmail.com<mailto:gfke...@gmail.com>> wrote:
I had a quick experiment with the web app idea for static content. I can't 
figure out what sort of app to create or what do with the vast baggage of 
references and support files that come with most default VS2015 projects. I'm 
not even sure if I should use VS2015 for this, but it does have deploy wizards. 
It's like mixing oil and water with an app and static content. Then while 
trying to deploy I created entries in my Azure resource list that I can't 
figure out how to delete, or even exactly what they are. So the quick 
experiment is an utter failure. If anyone has done this and knows what tools 
and settings to use to make it a smooth process, then I'm keen to hear about it 
-- Greg

If it is just static content you can deploy via FTP.

David.

--
David Connors
da...@connors.com<mailto:da...@connors.com> | @davidconnors | LinkedIn | +61 
417 189 363

Re: Azure static web sites

[Greg Keogh]

>
> I could do a quick walkthrough later today if that’d help. There aren’t
> many options that need to be chosen.
>

That'd be great if you have a break. Only the skeleton of the steps should
get me going. Once I get the files in the right sort of project and deploy
with suitable settings I should be able to extrapolate and find all the
configuration stuff about host headers and DNS and the like. I'll make a
blog post after I get it all working -- *Greg K*

RE: Azure static web sites

[Andrew Coates (DX AUSTRALIA)]

You’ll want to check you’ve got the latest Azure SDK and tools installed using 
the Web Platform Installer.

Looks like we’re up to 2.8.2 (I’ve got 2.8.1 installed)

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

From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On 
Behalf Of Greg Keogh
Sent: Thursday, 28 January 2016 6:22 PM
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: Re: Azure static web sites

https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fblogs.msdn.microsoft.com%2facoat%2f2016%2f01%2f28%2fpublish-a-static-web-site-using-azure-web-apps%2f=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7cd9c5f7b252db4ce20b8808d327b3cb96%7c72f988bf86f141af91ab2d7cd011db47%7c1=qPBwuCRVkxNbOv3t9SYiR2JnR%2f%2bko6d6aHC2ZSLjh1w%3d>

Oooh! I'll run through that later tonight. I think some of my screens were 
different when I tried similar initial steps, but I'll find out ... Ta, Greg

RE: Azure static web sites

[Andrew Coates (DX AUSTRALIA)]

https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/

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

From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On 
Behalf Of Greg Keogh
Sent: Thursday, 28 January 2016 2:13 PM
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: Re: Azure static web sites

I could do a quick walkthrough later today if that’d help. There aren’t many 
options that need to be chosen.

That'd be great if you have a break. Only the skeleton of the steps should get 
me going. Once I get the files in the right sort of project and deploy with 
suitable settings I should be able to extrapolate and find all the 
configuration stuff about host headers and DNS and the like. I'll make a blog 
post after I get it all working -- Greg K

Re: Azure static web sites

[Greg Keogh]

>
>
> https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/
>

Oooh! I'll run through that later tonight. I think some of my screens were
different when I tried similar initial steps, but I'll find out ... *Ta,
Greg*