Skip to content

Umbraco is unstable on Azure Web Apps OoTB #15742

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JasonElkin opened this issue Feb 21, 2024 · 2 comments
Open

Umbraco is unstable on Azure Web Apps OoTB #15742

JasonElkin opened this issue Feb 21, 2024 · 2 comments
Labels

Comments

@JasonElkin
Copy link
Contributor

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

Every version, ever...

Bug summary

I'm testing a PR that seeks to improve stability on Azure, but requires yet another environment specific appsetting to be enabled.

This will make 4 separate appsettings required to make Umbraco stable on an Azure web app. This is too many.

Discord, Our, and GitHub issues regularly attract queries about stability issues on Azure and a lot of the time it's simply because the site's not using the necessary app settings. It can be frustrating trying to help too as any conversation has to start with a review of appsettings.

One might be inclined to cry "RTFM" and be done with it, but I think we should be doing more to make the development experience easier here - especially as we're talking about deploying an ASP.NET based site to Microsoft's own platform for hosting ASP.NET sites.

Proposed solution:

An ASP.NET site can know if it's running on Azure Web Apps by looking for specific environment variables.

At start up, Umbraco could detect if it's running on Azure and, in the absence of any overriding appsettings, automatically use the appropriate appsettings for Azure Web Apps

Specifics

No response

Steps to reproduce

Deploy an Umbraco site to Azure App Service, without the necessary appsettings, and cry in despair at the poor performance and file locking.

Expected result / actual result

Umbraco "Just Works".

Copy link

Hi there @JasonElkin!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@CarlSargunar
Copy link
Contributor

Stumbled on this and I'm curious - is this a commonly seen problem? Working with slots in Azure? I'm just deploying a site which someone else has set up, and if I am expecting to see issues then it might be good to know :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants