mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix up some commands

Browse source
This commit is contained in:
Joey Hess 2016-12-07 12:00:27 -04:00
parent 60f4b1cf36
commit 528c7bee24
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/tips/peer_to_peer_network_with_tor.mdwn
View file

@ -12,9 +12,9 @@ First, you need to get Tor installed and running. See
To make git-annex use Tor, run these commands in your git-annex repository:
sudo git annex enable-tor
sudo git annex enable-tor $(id -u)
git annex remotedaemon
git annex p2p --gen-address
git annex p2p --gen-addresses
The p2p command will output a long address, such as:
@ -39,7 +39,7 @@ with a new empty repository:
And make git-annex use Tor, by running these commands in the git-annex
repository:
sudo git annex enable-tor
sudo git annex enable-tor $(id -u)
git annex remotedaemon
Now, tell the new peer about the address of the first peer.
@ -57,7 +57,7 @@ peer1 remote:
git annex sync --content peer1
You can also generate an address for this new peer, by running `git annex
p2p --gen-address`, and link other peers to that address using `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.
@ -94,7 +94,7 @@ that git-annex uses to make sure that only people you want to can access
your repository over Tor. That takes the form of a long string of numbers
and letters, like "7f53c5b65b8957ef626fd461ceaae8056e3dbc459ae715e4".
The addresses generated by `git annex peer --gen-address`
The addresses generated by `git annex peer --gen-addresses`
combine the onion address with the authentication data.
When you run `git annex peer --link`, it sets up a git remote using