My repos were coming up as 404s. I was wondering if I had been canned...
We are investigating reports of degraded performance
21–30 of 152 posts
Re: We are investigating reports of degraded performance
#22Who decided to deploy something risky on a Friday /s
Why don't they have lower environments like QA to test it in before going to production /s
Re: We are investigating reports of degraded performance
#23Re: We are investigating reports of degraded performance
#24Github is becoming too important. A routine backup system is needed, something like archive.org, that backs up important Github projects.
Re: We are investigating reports of degraded performance
#25Github is becoming too important. A routine backup system is needed, something like archive.org, that backs up important Github projects.
Hobby projects and today's work? Sure. Point straight at GitHub and hack away. And when it goes down, get yourself a coffee.
But everything that's anywhere near production should have already pointed those github requests to a mirror or other tool in your own controlled ecosystem. The status of GitHub should have nothing to do with whether you're customers are getting what they're paying you for. Same goes for Docker containers and every other kind of remotely distributed dependency.
Re: We are investigating reports of degraded performance
#26Re: We are investigating reports of degraded performance
#27I like how "Every request returns a 404" == "degraded performance"
Re: We are investigating reports of degraded performance
#28Re: We are investigating reports of degraded performance
#29Github is becoming too important. A routine backup system is needed, something like archive.org, that backs up important Github projects.
If only there was a decentralized system to allow version management of code.
I've been meaning to give radicle a try.