Blip, its back up. Nah, too much effort to host my own and I do need a coffee break from time to time.
Ignore this if you are on a big team of course.
GitHub was down
61–70 of 197 posts
Re: GitHub was down
#62Gone now!
18:41 CDT Everything operating normally.
Re: GitHub was down
#63Earlier quoted context omitted.
Exactly this. It's painful to realize that Git was invented to solve this very problem, but so many use GitHub as their source control server just like CVS and all the other old source control systems.
Then what's the alternative? Push and pull directly from other users who have access to the repository? What if that user is currently offline? There are huge benefits to having a main centralized repo. If you need redundancy for some reason, it's fairly trivial to mirror the repository somewhere else.
Push and pull to your own server running Gitea/Gogs or Gitlab, and mirror to Github if you feel the urge? Or, if you insist on having your workflow around Github, do it the other way around: have your local server mirror your Github repositories. That way, if Github goes belly-up you can just switch to your local server for the time being.
Re: GitHub was down
#64Earlier quoted context omitted.
Your question seems to indicate that you have a runtime dependency on github. If true, this is a problem no matter where your git repo resides. You need to architect a solution wherein you do not have a runtime dependency, especially if it is a single point of failure, or accept that your reliability will never be better than the sum of your services' reli abilities (there was an article on the "calculus of availabil…
Thing is, runtime dependencies on Github is something that Github is promoting and selling now ( https://github.com/marketplace/ ). Maybe this incident puts that value proposition in a more visceral context.
Just because they sell it doesn't mean people shouldn't know better.
Re: GitHub was down
#65Re: GitHub was down
#66What do people do to get around this? Run my own git server like the good 'ol days? Github has become a central source of failure for us now...
Your question seems to indicate that you have a runtime dependency on github. If true, this is a problem no matter where your git repo resides. You need to architect a solution wherein you do not have a runtime dependency, especially if it is a single point of failure, or accept that your reliability will never be better than the sum of your services' reli abilities (there was an article on the "calculus of availabil…
Is it still considered a runtime dependency if all you do is merge code and deploy while relying on GitHub? I assume most apps will not go down if GitHub goes down, but their ability to move code to production gets stalled.
Re: GitHub was down
#67What do people do to get around this? Run my own git server like the good 'ol days? Github has become a central source of failure for us now...
Others will say "work locally," but the problem is more in deployment. There's still a lot of app and CI servers out there where the workflow is "push to Github, then some automated script will tell the cluster to pull from Github" rather than "push the changes directly to the cluster." Containerization, especially projects like Kubernetes, make the latter much more viable; your cluster handles its own orchestration…
I agree.
Github is an off-site backup, and a nice interface for pull requests and code browsing.
There's just no reason to make github a critical part of your infrastructure.
Re: GitHub was down
#68What do people do to get around this? Run my own git server like the good 'ol days? Github has become a central source of failure for us now...
AWS CodeCommit has worked pretty well for me. I generally trust AWS/GCP/Azure over others regarding availability.
Re: GitHub was down
#69This is the 3rd major outage in a week, wow.
Poor gals and guys. Godspeed to them.
Re: GitHub was down
#70Earlier quoted context omitted.
Your question seems to indicate that you have a runtime dependency on github. If true, this is a problem no matter where your git repo resides. You need to architect a solution wherein you do not have a runtime dependency, especially if it is a single point of failure, or accept that your reliability will never be better than the sum of your services' reli abilities (there was an article on the "calculus of availabil…
Is it still considered a runtime dependency if all you do is merge code and deploy while relying on GitHub? I assume most apps will not go down if GitHub goes down, but their ability to move code to production gets stalled.
Git is inherently distributed. There's really no reason that Github has to stand between development and production.