search

libp2p / docs

Documentation site for the libp2p project.
https://docs.libp2p.io/
Other
60 stars 87 forks source link

Update go.md #352

Closed PanK0 closed 9 months ago

PanK0 commented 9 months ago

Added the indication to write and compile the second node with another address

marten-seemann commented 9 months ago

This is wrong. There's no need to hardcode the port, or to write any new code to start the second node.

PanK0 commented 9 months ago

Why? When I follow the tutorial I obtain an error in the end, due to the fact that the node address is written in the code. When running the second node adding as argument the address to the first node, the program stops because basically there is a node trying to connect to itself.

I solved this problem by running the second node with a different address, so I obtained a similar outcome to the one presented in the tutorial. That's why I tried to modify the page. :)

But if you say that this is wrong, can you please explain me why? I am clearly not getting it at this point.

Thanks for your patience.

Il Lun 25 Set 2023, 18:13 Marten Seemann @.***> ha scritto:

Closed #352 https://github.com/libp2p/docs/pull/352.

— Reply to this email directly, view it on GitHub https://github.com/libp2p/docs/pull/352#event-10464886955, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF2OKA4TUYVLYHJML7B3RW3X4GUSRANCNFSM6AAAAAA5GI73TQ . You are receiving this because you authored the thread.Message ID: @.***>

marten-seemann commented 9 months ago

Listening on :0 picks a random different port. This is standard UNIX behavior.

PanK0 commented 9 months ago

I will check it. Thanks. I am sorry for this, I am just trying to learn something new.

Il Lun 25 Set 2023, 18:30 Marten Seemann @.***> ha scritto:

Listening on :0 picks a random different port. This is standard UNIX behavior.

— Reply to this email directly, view it on GitHub https://github.com/libp2p/docs/pull/352#issuecomment-1734092985, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF2OKA2QK7GYQIHHNPKTT53X4GWTZANCNFSM6AAAAAA5GI73TQ . You are receiving this because you authored the thread.Message ID: @.***>