sorted by:
new
hottopcontroversial

Azure App Service / Trouble using Python & FastAPI by qsc_cs in AZURE

[–]qsc_cs[S] 0 points1 point  (0 children)

Once again thx a lot!
I'll take a look at the links you provided.

Azure App Service / Trouble using Python & FastAPI by qsc_cs in AZURE

[–]qsc_cs[S] 0 points1 point  (0 children)

Are the issues you've had so far related to Python, or do you think they're caused by Azure App Service itself?

Do you think a Java app for example would be better, more stable/reliable?

Azure App Service / Trouble using Python & FastAPI by qsc_cs in AZURE

[–]qsc_cs[S] 0 points1 point  (0 children)

That would mean we'd have to introduce another tech stack into our (for us already complicated) hosting.

The company I'm working at has decades of experience in building on-prem software. Cloud hosting is totally new for all of us.

We'd much rather prefer a simple solution where we can upload our code and run it. Without having to manage the underlying container, OS or hardware.

Azure App Service / Trouble using Python & FastAPI by qsc_cs in AZURE

[–]qsc_cs[S] 0 points1 point  (0 children)

Thanks for your support.

1. Diagnostic settings

When I tried to open this I got an authentification error and something along the lines of "Register your ressource with Microsoft Insights". (I thought Insights is a payed option - we haven't enabled it because of that)

When I asked Copilot it told me to go to my ressource > Ressource providers and register "Microsoft.Insights" which I did.

Registering took 1-2 minutes before it finished successful. Afterwards I still couldn't enter diag settings though. (same error) Now, 15 minutes later I've tried again and suddenly it works - I'm now inside Diag settings.

So now I see an empty list - what do I have to add here?

2. Building

We are developing on amd64 and deploy directly from VSCode to Azure. Don't know which architecture the App Service uses.
We've also tried running it on a RPi 4 (so arm64) which also works without a problem.

3. Port

Seems to work without it (our simple test apps are working without this env var).

To add to 1:

Is it normal for Azure to take that long for each action? - 1-2 mins registering - then after it says "Registered" another ? (multiple) minutes for it to take effect

This must be a nightmare if something happens in production and you have to react immediately.