GitHub Down with a 503
41–50 of 89 posts
Re: GitHub Down with a 503
#42Earlier quoted context omitted.
Do you and I have a different definition of "production?" GitHub going down impacts your deploys?
If you're using a cloud running test service like Travis CI pushing to GitHub can trigger your whole deployment process starting with running the unit and integration tests.
Third-party services being in the critical path for applying code to systems is a recipe for outages and other trauma. If it impacts you enough to come to HN and leave the comment I replied to, you're doing it wrong -- there had absolutely better be a failsafe that does not involve GitHub and Travis in your architecture.
Re: GitHub Down with a 503
#43Reminds me of the classic bumbling quote: "Why don't they just host GitHub where they host the status page?"
Re: GitHub Down with a 503
#44I was wondering why my `bower install` was failing... :/
Doesn't bower install from a local cache if network request fails? npm on the other hand... per docs at https://github.com/bower/bower oh....
As for the docs, it is somewhat crazy to think how much documentation is hosted by GitHub these days...
Re: GitHub Down with a 503
#45Re: GitHub Down with a 503
#46Re: GitHub Down with a 503
#47Haha, I wonder how many of us came here because we couldn't push or pull commits, so just taking a HN reading break... and boom the top post is about Github!
When Github appears down, I come to HN to find out if it's affecting everyone :p
Re: GitHub Down with a 503
#48Re: GitHub Down with a 503
#49Re: GitHub Down with a 503
#50I still have the tab opened now, saying "All systems operational"...