Gx: A package management tool built around IPFS

Re:Gx: A package management tool built around IPFS by tlrobinson on Thursday March 24, 2016 @04:11AM (#11351287)

Great work on this stuff.

Question about package managers built on ipfs, and ipfs in general: how do you ensure the packages/files you depend on will always be available? Is the idea that there would be at least one entity pledging to host every package for eternity, or if you depend on obscure packages would it be wise to run your own mirror of the packages you use? Or something else?

[ Parent | on HN ]

Re:Gx: A package management tool built around IPFS by _prometheus on Thursday March 24, 2016 @05:07AM (#11351444)

Thanks! Many answers:

- storing is super cheap. seeding not v expensive. i think the entire npm reg is <1TB?

- (soon can ship entire registries in USB keys!)

- many individuals and orgs should keep/replicate what they depend on

- tools like ipfs-cluster will help organize nodes like a RAID array

- can pay services to back things up (on service infra in vogue)

- can pay _the network_ to back things up -- see http://filecoin.io

[ Parent | on HN ]

Re:Gx: A package management tool built around IPFS by kefka on Thursday March 24, 2016 @06:22AM (#11351711)

When I want files available on IPFS, I just pin them to the appropriate machines.

    Ipfs pin add [key]

And my material now has another seed machine. It works, and is clean and efficient. One thing: I share everything in a directory, so the root directory name gets clobbered with the multi hash, and all the files in it retain their pretty names.

[ Parent | on HN ]