when I saw the `swa` tool I thought "looks neat but it's gonna make debugging a PitA", but the debugger actually attaches to both client and server. that's awesome. and the per-PR staging environment is gonna be useful.
😂 I want to say I did that on purpose but I just chose a location near the office. I used to walk by that place every day though. I'll have to check it out next time I'm there. 🌮🌮🌮
What would be use cases where I CANNOT use Angular with Azure Static Web Apps? And would Azure App Service be the next alternative for an Angular application working with a Spring Boot backend?
Exploring into this solution I found that setting up an azure devops pipeline makes it so that it automatically deploys to your SWA from the build pipeline, without using a release. How would I have to handle rollbacks then? Just rolling back to a previous commit? Is there any way to split a devops SWA build pipeline into using a release one that can automatically handle rollbacks on failure? Also I noticed you have no deployment slots. Even though it generates a staging environment during the lifetime of a pull request, if I wanted to have a permanent staging version of my app as a beta for new features I would need another SWA for that one? I'm really trying to figure out whether I should move all my web apps currently working on App Services to SWA.
Hi there! You can find more information on how to set up a multi-stage Azure DevOps pipeline with deployment to staging environments through this blog post. msft.it/6057ezMuU
how do make sure the api can only be called by this react spa website not by tools like postman? regardless if the user is authenticated or not because my requirement is that my app requires support authenticated user and also guest user and we do not want to make the api callable other than the client side app, possible?
Hi there, thank you for your question! You can learn more by taking a look at our official documentation with details on Authentication and Authorization for Azure Static Web Apps, here: msft.it/6057bK0vc
Thanks for reaching out! Although not available just yet, our Product Team is working hard on supporting this in the near future. Keep an eye on our social channels for updates and announcements.
This video is not a good example of a static web apps for the public! Say you have a simple web site...this video is good for pushing people away from the service! Maybe you can change the title...
Love the way Scott asks the "dumb questions" that everyone else is afraid to ask ! Great demo
when I saw the `swa` tool I thought "looks neat but it's gonna make debugging a PitA", but the debugger actually attaches to both client and server. that's awesome. and the per-PR staging environment is gonna be useful.
I am in! Moving my project to Azure Static Web Apps.
This was awesome, thanks for this!
We truly live in an age of wonders.
Love it, the Long and Lat is near a Taco shop
😂 I want to say I did that on purpose but I just chose a location near the office. I used to walk by that place every day though. I'll have to check it out next time I'm there. 🌮🌮🌮
Also , definitely have that feeling of I need to stop and build something with this right now!
Thanks, much guys. Good work 👍
Why would I need to install a CLI to call the function app vs just using a fetch command?
What would be use cases where I CANNOT use Angular with Azure Static Web Apps? And would Azure App Service be the next alternative for an Angular application working with a Spring Boot backend?
thanks. this is dope
Can I connect this static webapp (front end ) to app service ( backend ) ?
You can call APIs hosted anywhere from your frontend, including APIs hosted on App Service.
If for example, a third party website wants to use your weather app but embedded. Is it possible? How will be the mutual authentication?
How do I connect this to a Windows Scheduler?
Super!
Exploring into this solution I found that setting up an azure devops pipeline makes it so that it automatically deploys to your SWA from the build pipeline, without using a release.
How would I have to handle rollbacks then? Just rolling back to a previous commit? Is there any way to split a devops SWA build pipeline into using a release one that can automatically handle rollbacks on failure?
Also I noticed you have no deployment slots. Even though it generates a staging environment during the lifetime of a pull request, if I wanted to have a permanent staging version of my app as a beta for new features I would need another SWA for that one?
I'm really trying to figure out whether I should move all my web apps currently working on App Services to SWA.
Hi there! You can find more information on how to set up a multi-stage Azure DevOps pipeline with deployment to staging environments through this blog post. msft.it/6057ezMuU
how do make sure the api can only be called by this react spa website not by tools like postman? regardless if the user is authenticated or not because my requirement is that my app requires support authenticated user and also guest user and we do not want to make the api callable other than the client side app, possible?
Hi there, thank you for your question! You can learn more by taking a look at our official documentation with details on Authentication and Authorization for Azure Static Web Apps, here: msft.it/6057bK0vc
can I use next.js server side rendering in SWA?
Thanks for reaching out! Although not available just yet, our Product Team is working hard on supporting this in the near future. Keep an eye on our social channels for updates and announcements.
Local azure sites simulator with tunneling, very nice
demo on mac 😞😞
I just don't want to learn javascript ..lol
I guess thats why they keep mentioning blazor
This video is not a good example of a static web apps for the public! Say you have a simple web site...this video is good for pushing people away from the service! Maybe you can change the title...
this is still way more complex than something like netlify where it is all done with one command