fluencelabs/js-libp2p
1
0
Fork 0
mirror of https://github.com/fluencelabs/js-libp2p synced 2025-04-25 02:22:14 +00:00
Code Issues Projects Releases Wiki Activity

chore: rendezvous production guide info

Browse Source
This commit is contained in:
Vasco Santos 2021-01-20 16:52:02 +01:00
parent a747e5b495
commit 64ae07435d
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/production/README.md
View File

@ -12,6 +12,7 @@ This guide aims to guide you from using the public infrastructure into setting u
* [Connecting to Nodes with connectivity limitations](#connecting-to-nodes-with-connectivity-limitations)
* [`webrtc-star` servers](#webrtc-star-servers)
* [Circuit Relay](#circuit-relay)
* [Rendezvous Servers](#rendezvous-servers)
* [Querying the network from the browser](#querying-the-network-from-the-browser)
* [Others](#others)
* [SSL](#ssl)
@ -48,6 +49,12 @@ A relay is needed in situations where nodes are behind NAT, reverse proxies, fir
You can use [libp2p/js-libp2p-relay-server](https://github.com/libp2p/js-libp2p-relay-server) to setup your own relay server. This also includes an easy to customize Docker setup for a HOP Relay.
### Rendezvous servers
During the lifetime of a libp2p node, particularly during its startup, establishing connections with other peers will be crucial to create a network topology able to fulfill the needs of the node. Node with connectivity limitations might need to find peers providing a given service or playing a given role over time, so that they can connect to them and become fully functional libp2p nodes. These services and roles can range from circuit relays to application specific routing,
You can use [libp2p/js-libp2p-rendezvous](https://github.com/libp2p/js-libp2p-rendezvous) to setup your own relay server. Bear in mind, that this should be deployed as a cluster of servers to provide a healthy service.
## Querying the network from the browser
Libp2p nodes in scenarios such as browser environment and constrained devices will not be an efficient node in the libp2p DHT overlay, as a consequence of their known limitations regarding connectivity and performance.