At the moment we've got a bunch of issues with IPFS like #130 and #109 that are likely to do with js-ipfs just not being as stable or reliable as go-ipfs.
Luckily, we can embed a go-ipfs daemon into a nodejs project pretty easily with the npm-go-ipfs module.
Here's what we'll need to do:
Add npm-go-ipfs
Have it spawn a node from within the ipfs protocol handler
Customize the prot
Use storage within Agregore's user data
Create a js-ipfs instance that just talks to the gateway
Pass this instance to js-ipfs-fetch
Make sure the daemon is torn down when Agregore exists
This should give us all the reliability of go-ipfs without needing to change much of the code.
Down the help anyone that's intersted in getting their hands a bit dirty with JS work.
At the moment we've got a bunch of issues with IPFS like #130 and #109 that are likely to do with js-ipfs just not being as stable or reliable as go-ipfs.
Luckily, we can embed a go-ipfs daemon into a nodejs project pretty easily with the npm-go-ipfs module.
Here's what we'll need to do:
This should give us all the reliability of go-ipfs without needing to change much of the code.
Down the help anyone that's intersted in getting their hands a bit dirty with JS work.