function-proxies-on-static-web-apps
static-web-apps
| function-proxies-on-static-web-apps | static-web-apps | |
|---|---|---|
| 1 | 7 | |
| 2 | 317 | |
| - | 0.6% | |
| 0.0 | 3.0 | |
| about 2 years ago | 5 months ago | |
| HTML | ||
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
function-proxies-on-static-web-apps
-
Using function proxies with Azure Static Web Apps
Catalog Service
static-web-apps
-
Unable to deploy Azure Static Web Apps, support refuse to acknowledge outage
Latest issue: https://github.com/Azure/static-web-apps/issues/1404
-
Any Feedback on how i can improve this project?
FYI for 6. it usually means you have to set the fallback page to index.html on your host. Here's an azure static web apps issue referring to that problem https://github.com/Azure/static-web-apps/issues/702.
-
Deep linking with Azure Static Web Apps and Easy Auth
If you're using Azure Static Web Apps, you're likely to have this problem. Azure Static Web Apps doesn't support deep linking with authentication. When you get redirected you'll find you are (at best) missing the query parameters. If you take a look at the link here you'll see a suggested workaround. We're going to develop that idea in this post.
-
Azure AD Claims with Static Web Apps and Azure Functions
There is a limitation that affects authorization when you have a linked backend paired with an Azure Static Web App. Let's take the case of having an Azure Function App as the linked backend. Essentially the Azure Function app does not receive the claims that the Static Web App receives. There's an issue tracking this on GitHub, and it seems that this is a general problem with Static Web Apps, Azure AD and linked backends.
- Azure Static Web Apps will soon support server-side rendering for Next.js applicationsAzure Static Web Apps will soon support server-side rendering for Next.js applications
-
Static Web Apps from Azure DevOps Releases
More information can be found in this GitHub issue. The workaround is based on this comment in a related pull request.
-
Using function proxies with Azure Static Web Apps
NOTE: Currently, you can't add configuration settings on a SWA that doesn't have any functions in it, so I also included a dummy HTTP function to allow configuration in production. I believe that it should be a valid scenario to only have proxies on your backend function app, so I created an issue on the Static Web App's GitHub repository. I'll update this post with any info they provide me.
What are some alternatives?
blazor-desktop-crossplatform-sample - Example of an actual cross platform web and desktop hybrid Blazor app using the .NET 6 Blazor Desktop implementation
tye - Tye is a tool that makes developing, testing, and deploying microservices and distributed applications easier. Project Tye includes a local orchestrator to make developing microservices easier and the ability to deploy microservices to Kubernetes with minimal configuration.
aswa-example02 - Azure Static Web App .NET example
azure-cli-extensions - Public Repository for Extensions of Azure CLI.
fire-desktop - This project aims to help everyone who wants to achieve financial independence get to this goal earlier. We use mathematical calculations with personal and business questions to help advise you on how to take financial decisions.
blazor-starter - A starter template in C# APIs and Blazor for Azure Static Web Apps
easyauth-deeplink - Enable deep linking with Easy Auth
json-to-c-sharp - Convert a JSON String to C# String.
AzureStaticWebApp-CSharp-SimpleDemo - Simple Azure Static Web App demo done In C# for the videos series: aka.ms/StaticWebAppsTips
blazor-dragdrop - Easy-to-use Drag and Drop Library for Blazor