Revert "p2p --link now defaults to setting up a bi-directional link"
This reverts commit 3037feb1bf
.
On second thought, this was an overcomplication of what should be the
lowest-level primitive. Let's build bi-directional links at the pairing
level with eg magic wormhole.
This commit is contained in:
parent
5779e31cc7
commit
38f9337e16
7 changed files with 56 additions and 131 deletions
|
@ -56,12 +56,12 @@ peer1 remote:
|
|||
|
||||
git annex sync --content peer1
|
||||
|
||||
Any number of peers can be connected this way, within reason.
|
||||
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.
|
||||
|
||||
(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.)
|
||||
Any number of peers can be connected this way, within reason.
|
||||
|
||||
## starting git-annex remotedaemon
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue