I'm opening this PR to track progress in implementing ipfs-api support.
Once implemented, ChluIPFS will be able to use any IPFS node that is exposing the HTTP API (go-ipfs included) and we will fix #3.
Unfortunately, I started working on this without realising that ipfs-pubsub-room does not work with ipfs-api: we use that library directly and it's also used by OrbitDB.
We can't use ipfs-api, so we can't use go-ipfs until this gets solved somehow. This PR comes with a test that should pass if ipfs-pubsub-room solves the issue.
Note: not ready to be merged!
I'm opening this PR to track progress in implementing ipfs-api support.
Once implemented, ChluIPFS will be able to use any IPFS node that is exposing the HTTP API (go-ipfs included) and we will fix #3.
Unfortunately, I started working on this without realising that ipfs-pubsub-room does not work with ipfs-api: we use that library directly and it's also used by OrbitDB.
Relevant ipfs-pubsub-room issue: https://github.com/ipfs-shipyard/ipfs-pubsub-room/issues/28
Relevant OrbitDB issue: https://github.com/orbitdb/orbit-db/issues/273
We can't use ipfs-api, so we can't use go-ipfs until this gets solved somehow. This PR comes with a test that should pass if ipfs-pubsub-room solves the issue.