You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In electron we want to be able to use an internal go-ipfs node to leverage the advatages it has over js-ipfs. If we can't do that, we want to at least be able to run js-ipfs in the node process of Electron so that it can use more transports than it would in the renderer process.
Unfortunately at the moment js-ipfs only works in the renderer process so it would be the same as running from the browser.
The other way is connecting to go-ipfs using ipfs-api, we have an issue for that: #9
Relevant ipfs issue: ipfs/js-ipfs#843
In electron we want to be able to use an internal go-ipfs node to leverage the advatages it has over js-ipfs. If we can't do that, we want to at least be able to run js-ipfs in the node process of Electron so that it can use more transports than it would in the renderer process.
Unfortunately at the moment js-ipfs only works in the renderer process so it would be the same as running from the browser.
The other way is connecting to go-ipfs using ipfs-api, we have an issue for that: #9
For running a go-ipfs inside node/electron, that's easy: it's being done in this app: https://github.com/ipfs-shipyard/station using this library: https://github.com/ipfs/js-ipfsd-ctl. I'm actually already using this in #9
So the roadblock we are hitting is that we need #9 to comfortably use ChluIPFS from electron, otherwise it's like using the browser.
The text was updated successfully, but these errors were encountered: