aboutsummaryrefslogtreecommitdiff
path: root/doc/tips/peer_to_peer_network_with_tor.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/tips/peer_to_peer_network_with_tor.mdwn')
-rw-r--r--doc/tips/peer_to_peer_network_with_tor.mdwn10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/tips/peer_to_peer_network_with_tor.mdwn b/doc/tips/peer_to_peer_network_with_tor.mdwn
index 9c97735e4..13a7f0cc7 100644
--- a/doc/tips/peer_to_peer_network_with_tor.mdwn
+++ b/doc/tips/peer_to_peer_network_with_tor.mdwn
@@ -56,13 +56,13 @@ peer1 remote:
git annex sync --content peer1
-You can also generate an address for this new peer, by running `git annex
-p2p --gen-addresses`, and link other peers to that address using `git annex
-p2p --link`. It's often useful to link peers up in both directions,
-so peer1 is a remote of peer2 and peer2 is a remote of peer1.
-
Any number of peers can be connected this way, within reason.
+(When the second peer links to it, the first peer also
+gets a new remote added to it, which points to the second peer.
+So, on the first peer, you can also sync with the second peer.
+The name of the that remote will be "peer1", or "peer2", etc.)
+
## starting git-annex remotedaemon
Notice the `git annex remotedaemon` being run in the above examples.