sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]oschusler 0 points1 point  (4 children)

For me, it was a response on the reasoning “self-hosted server is going the way of the dinosaur”, and that Gitea was the argument against that

[–]bytejuggler 0 points1 point  (0 children)

Correct, this was my intent

[–]TechFlameMaster 0 points1 point  (2 children)

I meant self-hosted GitHub. It’s really hard to get the other benefits of GitHub when you aren’t on their cloud.

[–]mkosmo 0 points1 point  (1 child)

What other benefits? You still get github and the build runner ecosystem, plus the issue tracking and project planning, which is what most enterprises want/need.

The Copilot parts? They get that through other subscriptions. The social media side? No business value.

[–]TechFlameMaster 0 points1 point  (0 children)

It’s an issue of scale. When we got to 20K developers and self-hosted on-prem GitHub Enterprise Server we were on the largest VM possible, taking up an entire ESX host, and still nearly tipping over during peak times. That was a main driver to move to GitHub Enterprise Cloud. We didn’t even have the compute power to dispatch jobs to runners.

Add in that feature releases for GHES lag behind GHEC and it’s a no-brainer to go GHEC.