Live data from Hacker News

GitHub incident 2022-03-23

githubstatus.com

41–50 of 206 posts

Re: GitHub incident 2022-03-23

#41
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?

Re: GitHub incident 2022-03-23

#42
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 collaboration.

Re: GitHub incident 2022-03-23

#43

I hope they figure out what’s going on every morning. Heard from inside they don’t know why the db dies everyday but restarting it fixes it.

What's "the db"? It sounds like something of small to medium scale if you can just restart it like that.

In any case, why not just relocate some vendor engineers on site for a bit? Or, better, why does the vendor not have a small presence in the corner?

Sounds like whatever "the db" is it's probably some (objectively) small but very scary thing that's currently on fire and people are trying to figure out how to put it out without crashing the plane and also making too many waves internally, which is probably even harder. So asking about making vendor noises is (as useful as it may be) probably going down the wrong path - in much the same way this is probably not related to the outages (it may well be, but from the outside it's all coincidence anyway).

Re: GitHub incident 2022-03-23

#44

Earlier quoted context omitted.

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.…

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.

Re: GitHub incident 2022-03-23

#45
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.

The company I work for has a bunch of non-programmers using and working in gitlab (or "the git"), I can't really see it happening with GitHub regardless of where it was hosted.

Gitlab just seems better for actually running a software project.

Re: GitHub incident 2022-03-23

#46

Earlier quoted context omitted.

If you are a closed org, that is. Running your own gitea or gitlab with registration enabled and having to deal with spam is a real hurdle.

Is it not possible to restrict access to the git server from a VPN server only? Just off the top of my head, that's one thing you can do.

Yah, that's a "closed org". When you need to deal with the public at large, you need to deal with user registration issues and spam.

Re: GitHub incident 2022-03-23

#47

Earlier quoted context omitted.

If you are a closed org, that is. Running your own gitea or gitlab with registration enabled and having to deal with spam is a real hurdle.

Is it not possible to restrict access to the git server from a VPN server only? Just off the top of my head, that's one thing you can do.

So now every person who wants to contribute to your open source project has to setup a VPN client?

The parent comment was explicitly about non-closed (e.g. private) orgs.

Re: GitHub incident 2022-03-23

#48
post #27

Earlier quoted context omitted.

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.…

Maybe you are in a different time zone because our organization certainly noticed and was disrupted by this.

I’m on PST time, some of our other devs are on the east coast and one is in India. I think we’re spread out enough it should be an issue but maybe we prioritize different things.

Re: GitHub incident 2022-03-23

#49
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?

Yes

Re: GitHub incident 2022-03-23

#50
post #42
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…

It seems there's a tracking issue here, but it seems stalled: https://github.com/go-gitea/gitea/issues/1612
Post reply on HN