You can at least schedule the updates.
replyIt's still a pretty annoying process, though.
Until GHES can do zero-downtime upgrades nothing will get better. Not on their roadmap because as far as I’m aware the GHES team doesn’t actually exist or is entirely focused on KLTO. It’s a dead product that they wish didn’t exist.
replyPretty sure GitHub Enterprise Cloud is just Github hosting their enterprise server for you on Azure so you don't have to do the patching yourself.
replyIt sure isn’t! GitHub Enterprise Cloud is simply an enterprise plan on the regular multitenant github.com. Your repositories are on disk right next to everyone else that uses github.com. There is no segregated storage or compute.
replyI wish they had a plan to literally host GHES for you because then more people in the company would be forced to reckon with how terrible GHES is from an operational perspective. It is stuck ca. 15-20 years ago conceptually.
[flagged]
replyGithub enterprise cloud is on github.com and with more features:
http://github.com/account/enterprises/new
replyThey don't host github enterprise server for you (though gitlab has something called gitlab dedicated which they host gitlab ee for you).
> X-Stat header that controls whether the server operates in enterprise mode.
replyPerhaps this header mentioned in the article is related, maybe that's the toggle for the enterprise mode? Seems there is at least traces of "enterprise mode" on the normal github servers.
There is no “the toggle”. Read the article. A GHES appliance (and github.com) is dozens of services working together, some of which act differently in ES mode, so there are toggles galore. But probably not a lot that can be toggled by user input :(
replyWhy is there an eu github status then ?
https://eu.githubstatus.com/uptime
replyData residency is a thing.
replyAnd how would that explain the way higher SLA ?
reply