This release introduces a new Peering feature. The peering subsystem configures go-ipfs to connect to, remain connected to, and reconnect to a set of nodes. Nodes should use this subsystem to create “sticky” links between frequently useful peers to improve reliability. You can read more about it and how to configure peers in the go-ipfs config readme.
> Peering
> This release introduces a new Peering feature. The peering subsystem configures go-ipfs to connect to, remain connected to, and reconnect to a set of nodes. Nodes should use this subsystem to create “sticky” links between frequently useful peers to improve reliability. You can read more about it and how to configure peers in the go-ipfs config readme.
https://github.com/ipfs/go-ipfs/blob/v0.6.0/docs/config.md#peering
raucao
added a new dependency 2020-07-19 12:50:57 +00:00
The implementation effort for automating this with Chef wasn't worth the benefit here in my opinion.
We needed to document the peering config for people wanting to peer with us anyway, so I added the information to the wiki, where you can now also find an easy copypasta command for configuring your own nodes as well as new IPFS VMs:
I then used the command from the wiki to configure my local node as well ipfs-1 and verified that it does what it's supposed to do.
The implementation effort for automating this with Chef wasn't worth the benefit here in my opinion.
We needed to document the peering config for people wanting to peer with us anyway, so I added the information to the wiki, where you can now also find an easy copypasta command for configuring your own nodes as well as new IPFS VMs:
https://wiki.kosmos.org/Kredits:IPFS#Peering_with_Kosmos_IPFS_nodes
I then used the command from the wiki to configure my local node as well `ipfs-1` and verified that it does what it's supposed to do.
raucao
removed a dependency 2020-10-26 08:03:26 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
https://github.com/ipfs/go-ipfs/blob/v0.6.0/docs/config.md#peering
The implementation effort for automating this with Chef wasn't worth the benefit here in my opinion.
We needed to document the peering config for people wanting to peer with us anyway, so I added the information to the wiki, where you can now also find an easy copypasta command for configuring your own nodes as well as new IPFS VMs:
https://wiki.kosmos.org/Kredits:IPFS#Peering_with_Kosmos_IPFS_nodes
I then used the command from the wiki to configure my local node as well
ipfs-1and verified that it does what it's supposed to do.