News for hackers. Stuff that matters.

A comment on GitHub Outage. Parent comment

Re:GitHub Outage by kelseydh on Wednesday January 27, 2016 @08:50PM (#10985453)
The bigger problem here is the number of build packs only relying on Github as a source of truth. We need to find an abstraction to distribute storage so that there is no single point of failure.
[ Parent | on HN ]
Re:GitHub Outage by Ellahn on Wednesday January 27, 2016 @09:12PM (#10985600)
Exactly.

So I had to install Gems from RubyGems, not that big of a deal, and I had to look them up on RubyGems since Google gives me GitHub first, but that's OK too, but then all the documentation seems to be on.... Github. Except not, it's also on RDoc. (Though RDoc kinda sucks, compared to GitHub...)

Pretty big win imho, Rails got a few more points with that. :D

Now I'm wondering how NodeJS is faring at this...

[ Parent | on HN ]
Re:GitHub Outage by TheAceOfHearts on Wednesday January 27, 2016 @11:30PM (#10986287)
We have npm as our single source of truth, although you could host your own npm, or use a tool like sinopia [0] which makes pretty reasonable tradeoffs while being usable. Instead of asking you to replicate all of npm, it just keeps local copies of your packages, and if a package isn't found it'll hit npm.

[0] https://github.com/rlidwka/sinopia

[ Parent | on HN ]