3 ms·
Again? Last time an incident like that happened was Packages which was less than 24 hours ago. [0] Before that weeks ago [1] At this point, it is clear that Git
by rvz 4y ago
Again? Last time an incident like that happened was Packages which was less than 24 hours ago. [0] Before that weeks ago [1] At this point, it is clear that GitHub is essentially falling apart and is becoming extremely unreliable.
It's not too late to join the serious projects like Blender, ReactOS, RedoxOS, etc who are happily self hosting and are not going all in on GitHub.
I posit that they even have better uptime by just self hosting for one year vs GitHub's uptime record since they got acquired by Microsoft. Looks like 'centralising everything' to GitHub did not age well at all, as I have warned years ago. [2]
[0] https://news.ycombinator.com/item?id=34982456 https://news.ycombinator.com/item?id=34982456
[1] https://news.ycombinator.com/item?id=34843847 https://news.ycombinator.com/item?id=34843847
[2] https://news.ycombinator.com/item?id=22867803 https://news.ycombinator.com/item?id=22867803
- echelon 4y ago> happily self hosting That can also be a nightmare. Do you want git hosting, CI/CD, etc. to be among your core competencies? Because that's what this entails. You need a full team to staff it and be on call. I guarantee you that those who self host will have just as many breakdowns. Five nines is hard, especially when it's not your main job.
- kneebonian 4y agoIt isn't that hard to have a build server and run a shell script on a timer.
- vore 4y agoYeah, and don't forget to run the shell script in screen as well so you can detach it /s
- throwusawayus 4y agowhy always repeatedly write the same comment about not going “all in on github” in these threads? what is goal of writing this hundred+ times? https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=“all%20in%20on%20github”%20rvz&sort=byPopularity&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu... i dislike github quite alot but this does not achieve anything. no one else is saying to go all in on github so what is this even reply to?
- rvz 4y ago> why always repeatedly write the same comment about not going “all in on github” in these threads? what is goal of writing this hundred+ times? Because I can. How many more times does a service need to go down in less than a month to deem it unacceptable for any use? Unless you think paying for downtime is acceptable? > i dislike github quite alot but this does not achieve anything. That is not my problem since I saw the problem years ago and chose to self-host instead. Rather than others complain to GitHub, they might as well self-host instead for reliability. If you can setup a simple SaaS website, you can easily self-host a Gitlab / Gitea instance for 1 to 5 people. It's not that hard. > no one else is saying to go all in on github so what is this even reply to? So you didn't read this then? >> We're all in on Github actions these days but there was a time when we used to maintain our own Jenkins instance. [0] >> At this point, our self-hosted CI and code review tooling has had significantly better uptime for the past year. [1] The schadenfreude for GitHub's unreliability and some of its fans celebrating monthly down time only makes it hilarious to watch. [0] https://news.ycombinator.com/item?id=26302907 https://news.ycombinator.com/item?id=26302907 [1] https://news.ycombinator.com/item?id=26301740 https://news.ycombinator.com/item?id=26301740
- throwusawayus 4y agoso, because two people said they go all in on github on an hn thread TWO YEARS AGO , you feel the need to post public i-told-you-so hundreds of times ???!??? i am amazed @dang is ok with that, it seem completely deranged man, borderline harassment
- rvz 4y agoI already gave the solution years ago [0] and each time GitHub goes down, hundreds of comments continue to complain when the solution is right in front of their eyes. > i am amazed @dang is ok with that, it seem completely deranged man, borderline harassment What harassment exactly? That whatever helpful advice I said in [0] and not 'centralizing everything to GitHub' seems to have aged well? There is nothing 'deranged' about explaining preventative solutions like 'self-hosting' to those still using an unreliable service. In fact, it is more 'deranged' to believe that GitHub has gotten any more reliable after Microsoft acquired it. You can continue to use GitHub's services, but don't complain when something from GitHub goes down again in less than a months time when the solution has been in front of you for years. [0] https://news.ycombinator.com/item?id=22867803 https://news.ycombinator.com/item?id=22867803