IPFS cluster mid-term solution #26

New Issue

raucao · 2019-04-04T08:13:52Z

raucao commented

2019-04-04 08:13:52 +00:00

Eventually, we're shutting down dev.kosmos.org, which would leave us with only one of the currently two cluster nodes.

Perhaps helpful for this, I just stumbled upon this detailed guide for setting up a cross-region cluster on the cheap:

https://gateway.ipfs.io/ipfs/QmTqD45V5EFF9DvCpr39vyJDE5m1PJYdhWSjqNdYLAgA37/

Eventually, we're shutting down `dev.kosmos.org`, which would leave us with only one of the currently two cluster nodes. Perhaps helpful for this, I just stumbled upon this detailed guide for setting up a cross-region cluster on the cheap: https://gateway.ipfs.io/ipfs/QmTqD45V5EFF9DvCpr39vyJDE5m1PJYdhWSjqNdYLAgA37/

raucao commented

2019-05-28 12:24:27 +00:00

Thinking about this again, and I can't help but wonder why we should use a private pin orchestration mechanism, when our IPFS hashes are all published on the public Ethereum ledger to begin with.

That means any node listening to the blockchain for new hashes could just pin them from those events. With the kredits-contracts JS wrapper, that would probably be solved in less than 10 lines of code.

/cc @bumi

Thinking about this again, and I can't help but wonder why we should use a private pin orchestration mechanism, when our IPFS hashes are all published on the public Ethereum ledger to begin with. That means any node listening to the blockchain for new hashes could just pin them from those events. With the `kredits-contracts` JS wrapper, that would probably be solved in less than 10 lines of code. /cc @bumi

raucao commented

2019-06-12 10:53:37 +00:00

https://github.com/67P/kredits-contracts/pull/136