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

[WIP] IPFS local config #117

Closed
wants to merge 1 commit into from
Closed

[WIP] IPFS local config #117

wants to merge 1 commit into from

Conversation

AquiGorka
Copy link
Contributor

@AquiGorka AquiGorka commented Nov 21, 2017

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:

  • Setup and execute js-ipfs node.
    • Double check if we can assign an id to the node and use that for the IPFS config files in the browser.
  • Setup and execute signaling server
  • Setup different IPFS configurations fro dev and prod environments

This 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 future test layer.

By limiting the number of nodes we can also avoid unnecessary connections that can potentially crash the browser.

Configuration reference

'/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',
Copy link
Contributor

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?

Copy link
Contributor Author

@AquiGorka AquiGorka Nov 22, 2017

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.

Copy link
Contributor

@chadoh chadoh left a 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?

@AquiGorka
Copy link
Contributor Author

AquiGorka commented Nov 22, 2017

Do we need a way to configure these Bootstrap and Swarm addresses for different environments?

Yes.

  1. One for local sandboxed development
  2. One for production
  3. Maybe another one for local development that connects to the IPFS network.

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?

Hmmm. I don't think I can answer this question. I mean, those nodes are probably long lived IPFS nodes but not sure if they will change/update them.

I think we can go back to the defaults for scenarios 2 & 3 from above.

@AquiGorka AquiGorka closed this Apr 12, 2018
@AquiGorka AquiGorka deleted the dev/local-ipfs-setup branch April 12, 2018 09:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants