Show HN: Beaker – A browser for IPFS and Dat

Re:Show HN: Beaker – A browser for IPFS and Dat by zbyte64 on Thursday August 11, 2016 @05:26PM (#12271665)

How are you shipping IPFS with your electron app? I was under the impression only the GO implementation of IPFS is complete. Are you simply running IPFS Go as another process? (And where is it being included? I couldn't find it in the code base)

[ Parent | on HN ]

Re:Show HN: Beaker – A browser for IPFS and Dat by pfraze on Thursday August 11, 2016 @05:28PM (#12271683)

Have a look in https://github.com/pfrazee/beaker-plugin-ipfs. (All protocols and web apis in beaker are plugins.) The Go binary is distributed via npm, and spawned as a daemon.

[ Parent | on HN ]

Re:Show HN: Beaker – A browser for IPFS and Dat by diggan on Friday August 12, 2016 @05:15AM (#12274232)

Basically you have three different ways of using IPFS in JavaScript today.

1. Use js-ipfs which is a implementation of IPFS in javascript. This requires that you either have both frontend and backend being ipfs nodes, or at least in the backend, otherwise content added won't be seeded since you close your browser when you're done.

2. Use js-ipfs-api and go-ipfs together. Start a daemon with go-ipfs and then point js-ipfs-api to it. The daemon will essentially act like one of your backends.

3. Use js-ipfsd-ctl that kind of is the same as number 2 but starts a go-ipfs node for you, and then returns an instance of js-ipfs-api, already pointed to the daemon.

The author in this case went for 3. Probably the reasoning is that js-ipfs and go-ipfs can't really talk to each other yet, and go-ipfs has the bigger network and is more popular.

[ Parent | on HN ]