-
Notifications
You must be signed in to change notification settings - Fork 5
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
[WIP] IPFS local config #117
Conversation
'/dns4/nyc-2.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLV4Bbm51jM9C4gDYZQ9Cy3U6aXMJDAbzgu2fzaDs64', | ||
'/dns4/wss0.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmZMxNdpMkewiVZLMRxaNxUeZpDUb34pWjZ1kZvsd16Zic', | ||
'/dns4/wss1.bootstrap.libp2p.io/tcp/443/wss/ipfs/Qmbut9Ywz9YEDrz8ySBSgWyJk41Uvm2QJPhwDJzJyGFsD6', | ||
'/ip4/127.0.0.1/tcp/4003/ws/ipfs/QmPFcnw8WYBGchAT7kJv2s8XiCkEAYUnkx5Zcw25RXwbip', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where does this hash come from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the hash from my terminal js-ipfs
node, one of the things to get done is figure out a way to give the node a custom id or find out which id it has so that we can setup the browser nodes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need a way to configure these Bootstrap
and Swarm
addresses for different environments?
I know we added these Bootstrap
settings in #39 for a particular reason, but does hard-coding them introduce problems? Can these addresses become stale?
Yes.
Hmmm. I don't think I can answer this question. I mean, those nodes are probably long lived I think we can go back to the defaults for scenarios 2 & 3 from above. |
This changes will give us a better understanding of the layers and their interactions in the
IPFS
network.With this changes we will be able to have a working setup that does not connect to the IPFS network but simulates a local network able to distribute content in their same fashion.
There are some tasks still needed:
js-ipfs
node.id
to the node and use that for theIPFS
config files in the browser.signaling server
dev
andprod
environmentsThis setup allows the devs to run a local network. Meaning, we can access
thicket-webapp
from different browsers (or same browser in regular and incognito modes) and the content created between them will be distributed and available to each other.We will be able to see how
thicket-webapp
behaves to different users. This will also provide a base to a futuretest layer
.By limiting the number of nodes we can also avoid unnecessary connections that can potentially crash the browser.
Configuration reference