This is an automated archive made by the Lemmit Bot.
The original was posted on /r/azure by /u/farox on 2023-08-10 22:25:05.
Since Blazor is all the rage these days, we're looking to develop a Blazor app. It will port and existing "some java script plus mapbox" thing. But this is only the first of a handful of apps that will be ported into this yet to be build "portal".
Now I offered to also take care of the hosting and maintenance. Naturally the question is how much that would be.
So far I was still undecided on some issues, but for this I need to know how we're actually going to do this.
My problem is, that I just started learning some AWS and never did DevOps on Azure (though used it as a dev, years ago)
The idea is to have one app that faces the internet with 200 users. However these users keep the thing open during their whole work day and it can have lots of data.
Auth should be done using Active Directory (unless there is a better option).
This is public facing.
In 1 virtual private network (VNET?) I want to have a psql db (roughly 1gb, it's tiny, plus a couple for dev/test), an environment for dev where pushes to main on github will be deployed, one environment for test, (possibly one for staging,) but also some file storage for text files that need to be uploaded from one office and then downloaded to another.
All of this should be neatly tied into Visual Studio, GitHub, automatic builds, unit tests, the whole parade.
Or should I look into the app hosting services?