Consider deployment story for static web apps/spa

dotnet / aspire

Tools, templates, and packages to accelerate building observable, production-ready apps

https://learn.microsoft.com/dotnet/aspire

MIT License

3.94k stars 483 forks source link

Consider deployment story for static web apps/spa #2711

Open timheuer opened 8 months ago

timheuer commented 8 months ago

As some front-end apps get added for AppHost orchestration and thus also deployment, currently Dockerfile is the recommended (only?) approach. This will translate into a container resource for deployment manifest.

We should consider how to model specifically SPA-type front-ends in the AppHost that also would translate to new deployment endpoints more tailored to static web apps like storage, Azure SWA, etc.

kjbetz commented 3 months ago

I agree. I'm working on a current project that I would like to deploy an Angular SPA to an Azure Static Web App. The API deploying as a Container App and the DB provisioned as Postgres Flexible Server should be good. Would love to see this picked up.

Or/And also another scenario maybe... being able to build frontend and put into public folder of web app before it gets built and deployed as Azure Container App.