-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Clone ipfs daemon
in node
#921
Comments
Thanks for reporting this issue @milesalex. You are trying to create a daemon out of the IPFS instance (core). The daemon needs to instantiated differently. See https://github.com/ipfs/js-ipfs#usage |
Were you able to get it to work? |
This was my attempt. |
If you are looking for a If you look to have a |
I have my client side run like:
And then trying to expose the core api daemon on port 5001 from the backend:
I am getting that error from console when i try and connect from the front end: |
Both frontend and backend are running from the same machine! My Goal is to connect to ipfs, without having to run. |
@426F746368 you are still trying to run an You expose a daemon, you need to do this steps https://github.com/ipfs/js-ipfs/blob/master/src/http-api/index.js |
Another great example is https://github.com/ipfs/js-ipfs/blob/master/test/utils/ipfs-factory-daemon/index.js |
@diasdavid, appreciated. Will def look at them. You reckon it is better to run a daemon on a local machine, yielding better results than on a nodejs server? |
The daemon is a Node.js server :) Hope this answers your question |
License: MIT Signed-off-by: Alan Shaw <alan.shaw@protocol.ai>
if you want to connect remote server |
I'm trying to recreated the command
ipfs daemon
in node.But in the browser I''m getting fetch errors
The text was updated successfully, but these errors were encountered: