Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub incident 2022-03-23

githubstatus.com

Post reply on HN
Print view View original

51–60 of 206 posts

Re: GitHub incident 2022-03-23

#51

Post by edgyquant »

xondono wrote: post #44
gjulianm wrote: post #32

Earlier quoted context omitted.

At my organization it's always been true. Setting up GitLab is fairly easy, in my company we do it and it's cheap (on-prem hosting is basically zero, and we had the IPs/domains already) and it hasn't given us too many headaches. I think last time I had to do something was maybe a few months ago when I restarted it so that it picked up the updated SSL certificate.

I’d say it depends, I run my own on prem server and gitlab was a PITA. Too many moving parts, updating took too much of my time, and I never felt “safe”. Moving to gitea solved all of those issues for me (thus far), now I’m looking into adding other stuff like CI through Drone.

It definitely depends. We’re pretty early stage and I’m the senior engineer+infrastructure guy so running our own gitea instance or whatever is just more time that I’m almost out of.

Re: GitHub incident 2022-03-23

#52

Post by jon-wood »

jrowley wrote: post #29
stuff4ben wrote: post #23

Earlier quoted context omitted.

Github Enterprise hasn't been faring too well at my work either this week. When you work on both open and closed source products and GH and GHE are both down, it leads to a very unproductive week.

Does GitHub enterprise result in dedicated instance or any better availability?

It Depends.

GitHub Enterprise is confusingly both a "call us for pricing" tier of GitHub the website, and also an on-premise version of GitHub that you can run as an appliance in your own data centre. The first of those is ultimately just GitHub and so has the same outages, the second is running on your own hardware so (shouldn't be) tied to the website's availability.

Re: GitHub incident 2022-03-23

#53

Post by tokumei »

dbrgn wrote: post #42
nimbius wrote: post #16

https://www.githubstatus.com/history 21 incident outages in just 3 months. At this rate the benefits of running your own gitea or gitlab are starting to become competitive.

Does Gitea support some kind of federation / cross-instance PRs? That's the main thing I'd miss from a self-hosted instance, the ease of getting contributions. After all, you don't even need Gitea for pure Git hosting. If you have a server with SSH access, just init a bare repo in a directory, push to that, and you're ready to go. No web UI needed. The reason I'm still using GitHub is not code hosting. It's collabora…

> If you have a server with SSH access, just init a bare repo in a directory, push to that, and you're ready to go. No web UI needed.

Used to do that years ago for my personal projects. Honestly does the trick.

Re: GitHub incident 2022-03-23

#54

Post by bewuethr »

jrowley wrote: post #29
stuff4ben wrote: post #23

Earlier quoted context omitted.

Github Enterprise hasn't been faring too well at my work either this week. When you work on both open and closed source products and GH and GHE are both down, it leads to a very unproductive week.

Does GitHub enterprise result in dedicated instance or any better availability?

There are multiple products: self-hosted (Enterprise Server) and hosted by GitHub (Enterprise Cloud). I don't know about uptime guarantees, but you can buy Premium or Premium Plus support with 30-minute SLA or a dedicated account manager.

Re: GitHub incident 2022-03-23

#55

Post by mrkurt »

nimbius wrote: post #16

https://www.githubstatus.com/history 21 incident outages in just 3 months. At this rate the benefits of running your own gitea or gitlab are starting to become competitive.

If you want companies to be honest on their status pages (I do!), you can't just count incidents like that. Status pages can be an amazing place to communicate all kinds of problems.

Most issues have a relatively narrow impact, but the impacted people _still_ benefit from seeing them listed.

Re: GitHub incident 2022-03-23

#56

Post by brimble »

dbrgn wrote: post #42
nimbius wrote: post #16

https://www.githubstatus.com/history 21 incident outages in just 3 months. At this rate the benefits of running your own gitea or gitlab are starting to become competitive.

Does Gitea support some kind of federation / cross-instance PRs? That's the main thing I'd miss from a self-hosted instance, the ease of getting contributions. After all, you don't even need Gitea for pure Git hosting. If you have a server with SSH access, just init a bare repo in a directory, push to that, and you're ready to go. No web UI needed. The reason I'm still using GitHub is not code hosting. It's collabora…

Gitea gets you: a nice GitHub-like web GUI, including for stuff like managing users; 2FA; some integrations; web hooks without having to add git-hooks to all your repos; and extremely-useful-to-some-projects features like git-lfs support.

If you don't want or need those things, bare git repos are fine and certainly easier to support (not that Gitea's that hard, though a few issues/PRs I've noticed have caused me more than a little concern about the overall quality of the project).

Re: GitHub incident 2022-03-23

#58

Post by queuebert »

adamsmith143 wrote: post #41
nimbius wrote: post #16

https://www.githubstatus.com/history 21 incident outages in just 3 months. At this rate the benefits of running your own gitea or gitlab are starting to become competitive.

Is it really though? Are engineers committing so frequently that they can't make it through a few hours without Github?

Maybe they measure performance in git commits.

Re: GitHub incident 2022-03-23

#59

Post by Inversechi »

xondono wrote: post #44
gjulianm wrote: post #32

Earlier quoted context omitted.

At my organization it's always been true. Setting up GitLab is fairly easy, in my company we do it and it's cheap (on-prem hosting is basically zero, and we had the IPs/domains already) and it hasn't given us too many headaches. I think last time I had to do something was maybe a few months ago when I restarted it so that it picked up the updated SSL certificate.

I’d say it depends, I run my own on prem server and gitlab was a PITA. Too many moving parts, updating took too much of my time, and I never felt “safe”. Moving to gitea solved all of those issues for me (thus far), now I’m looking into adding other stuff like CI through Drone.

Did you consider woodpecker instead of drone? It's basically an evolved fork of the OSS version.

https://woodpecker-ci.org/

Re: GitHub incident 2022-03-23

#60

Post by thaeli »

edgyquant wrote: post #22
nimbius wrote: post #16

https://www.githubstatus.com/history 21 incident outages in just 3 months. At this rate the benefits of running your own gitea or gitlab are starting to become competitive.

I’m not sure at what organization that is true. My company lives out of GitHub and Jira and I’ve hardly noticed the three month surge. GitHub would have to do a lot worse to get many companies to want to host their own services. This is the argument people have said about the cloud from day one. People want to know it isn’t their problem, that makes cloud computing (and things like GitHub) worth their weight in gold.…

Also, looking at this it seems like GitHub isn't doing the common SaaS thing of just lying on their status page. Many providers, both internal and external, would look a lot worse if they had honest status pages.
Post reply on HN