Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Electron support #11

Open
fazo96 opened this issue Dec 19, 2017 · 1 comment
Open

Electron support #11

fazo96 opened this issue Dec 19, 2017 · 1 comment

Comments

@fazo96
Copy link
Collaborator

fazo96 commented Dec 19, 2017

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.

@kulpreet
Copy link
Contributor

kulpreet commented Jan 8, 2018

@fazo96 Don't worry about using js-ipfs inside the electron based architecture.

We will use electron only if we want to use go-ipfs, otherwise we provide a chrome extension or a chrome app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants