#production mode but without https
1 messages Β· Page 1 of 1 (latest)
It's not possible, Production mode is our recommendation and it is not designed for K8S hosting (or other kinds of reverse proxy hosting where you can't run on https).
Hmm, what's wrong K8S hosting Umbraco?
Is it only the Production that would have issues?
Right now we have now issues at all running Umbraco in out K8S setup. It runs perfect and fast.
Maybe tou can disable the runtime check for https. You can write your own checks and add them with a composition, so it would be a good bet that you could also remove runtime checks.
umbracoBuilder.RuntimeModeValidators().Remove<UseHttpsValidator>(); would seem likely?
Thanks, I will give it a try
Hmm, what's wrong K8S hosting Umbraco?
Sorry, absolutely nothing wrong with that! We don't "support" it directly, as in we have no documentation and expertise in it. I just meant: the feature Production Mode was not designed for K8S hosting. π
Thanks Mike, it works as expected.
I understand your recommendations. Was just wondering if you have any specific problems with Umbraco + K8S.
Our setup is maybe not the common use of K8S.
Each (200+) Umbraco application is running with 0 or 1 pod. So no real loadbalancing of Umbraco traffic and scaling. And it is only the backoffice that is in use, not the frontend.
I have absolutely no experience running Umbraco in a setup like that, I think you might be the first pioneer.. so.. no idea! π
no real loadbalancing
just remember that if 2 or more instances of an Umbraco backoffice connect to the same database then you are by definition load balancing
I think you should see the production mode as a way to force best practices. It's mostly a collection of checks at startup which cause Umbraco to fail to start if one of the checks fail. Like I said, you can also write checks yourself. So in your case, I guess the best practice isn't applicable, but it's not like Umbraco doesn't like your situation π Maybe it should have been easier to disable certain checks, maybe there needs to be a flag that says: I'm running behind a firewall, skip some checks. But you have the tools to remove checks if required. And tbh, in 98% of the cases it's probably better to have the 'usehttps' setting enabled and for the other few cases you can disbled them π
you can see it in the umbracoServer table if more than one are active (I believe)
you're right, it's "just" checks that we enforce because we thing it's best practice π no magic
Ahh. So "Mode": "Production" has no effect on how Umbraco runs?
It's all the other settings like for example "ModelsMode", "UseInMemoryCache". That is important.
There will only be 1 instance π
Not entirely sure, I believe there are SOME optimalisations, but for the most parts it's just checks that force certain settings
Production mode itself is just checks that make sure that you deploy with the correct settings. Those settings indeed change how Umbraco works, Production mode just checks that they're all set to best practice and does nothing else.
I thought production mode pre-compiles razor files where-as BackofficeDevelopment does not (because they need to be editorable in the backoffice in that case). That's not a setting, right?
Think it just tells you to enable the setting for precompiling razor files, but I might be wrong
To be fair, it's the only thing I'm not sure about if it's just checking a setting or actively doing something by itself.
You might be right! https://github.com/umbraco/Umbraco-CMS/pulls?q=is%3Apr+production+mode+is%3Aclosed+author%3Aronaldbarendse
PR #12697 looks like it does that.
I can confirm that when in Production mode. It is not possible to change templates.
There is no error message or notification when trying to save a template.
The changes just disappear from the Umbraco Template editor.
Maybe the editor should be in read-only mode and/or the [Save] button should be disabled
That's weird. In Umbraco 13 it would actively disabled the editor (except in Umbraco forms for some reason :P)
Well, looks like a bug report has to be created later today π
Now back to work!