Live data from Hacker News

GitHub was down

githubstatus.com

81–90 of 133 posts

Re: GitHub was down

#81
post #17

I know Github is down because I'm trying to update a kops cluster, but Github breaks it > kops update cluster error reading channel "https://raw.githubusercontent.com/kubernetes/kops/master/channels/stable": unexpected response code "500 Internal Server Error" for "https://raw.githubusercontent.com/kubernetes/kops/master/channels/stable": 500: Internal Server Error

Some major tools like python's `poetry` has official recommended installation as:

    curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | python
Guess why our python docker images stopped building today?

Re: GitHub was down

#83
post #75
post #61

Hopefully it's just them reverting their latest UI changes

What's wrong with them? Maybe it's because I do not use project management features much, but I like new UI more.

the repo top bar is wider than the rest of the content. It feels unbalanced. Personally I'm not a fan of that part. No complaints about any other change.

Re: GitHub was down

#84
ITT: Lots of Github hate.

Dont forget that change in software is inherently risky and will result in bugs, etc. Id rather have a platform that is always looking to make things better and risking a bit of downtime, than a stale platform that we all know we depend on.

Re: GitHub was down

#85
post #11

People are advocating hosting their own Git repos, but wouldn't those go down, too, and wreck the day even more? Or, are you guys all devops geniuses better than those who work at GitHub?

Not sure why you're being downvoted; I absolutely agree. For a smallish project, especially made up of volunteers, free time spent toward maintaining infra is time not spent on working on your project.

For larger projects where you have the resources to have dedicated infra people, I guess it depends.

Re: GitHub was down

#86
post #11

People are advocating hosting their own Git repos, but wouldn't those go down, too, and wreck the day even more? Or, are you guys all devops geniuses better than those who work at GitHub?

I used to self-host everything and while I never had hiccups or problems, I got tired of the additional work of maintaining a git server and moved my personal projects to github just so I don't have to deal with it. I suppose the comments are fueled by frustration and the fact that when you have something in-house, you can directly go and push the devops teams to fix it whereas github you just sit and wait. I never understood why people think that poking someone with a stick will magically speed up the fixing process but there we go...

Re: GitHub was down

#87
post #11

People are advocating hosting their own Git repos, but wouldn't those go down, too, and wreck the day even more? Or, are you guys all devops geniuses better than those who work at GitHub?

> Or, are you guys all devops geniuses better than those who work at GitHub?

Do you call IBM to maintain your pi-hole?

Re: GitHub was down

#88
post #25

Earlier quoted context omitted.

Umm, so if you are hosting your own Git Repos, and not fiddling with the configurations much once you have found the perfect fit. Isn't the only reason it will go down be because of network issues or power failure? What other possible cause could be for system failure? I have been running HA, Pi-Hole, Maria-DB and my own API instances on my Raspberry Pi and in the 22 days of uptime till now, there have been 0 failure…

Many reasons, including your hosting provider going down. At that point you'd have to create and manage a cluster. You have to update servers, etc. etc. and if you count the hours is many times more than working locally and wait a couple of hours until technicians at GitHub fix the problem for you.

Self-hosting means something different.

Also, most people don't need to provide access to hundred of thousands of users so they won't ever need a cluster of Git servers.[1] (Some bloated UI like GitLab may need more computing to host even for a moderate amount of users, though).

Self-hosting Git is easy. Besides power failures there is not much reason this could go down if you don't help with that actively. But if you don't touch it besides OS updates it can run 24h a day for many years without any effort. (Biggest issue is backup actually, but you have to think about that point anyway if you run something on your own).

[1] https://news.ycombinator.com/item?id=23804373

Re: GitHub was down

#89
post #31

This is a nice reminder that you can have multiple remote repos and push/pull to all of them at the same time. For my side projects I usually use both github and google cloud source (I use gcp). If one is down the other is still available and then just resync when service is recovered.

Nice, good tip, I will set that up for my local projects. Not using Github for those, but it nevers hurts to have redundant Git servers.
Post reply on HN