add new walkthrough chapter on using special remotes

This commit is contained in:
Joey Hess 2015-01-20 12:41:49 -04:00
parent 3de04f9d2d
commit 05bb05b385
3 changed files with 59 additions and 5 deletions

View file

@ -5,13 +5,13 @@ that is truly remote, a host accessed by ssh.
Say you have a desktop on the same network as your laptop and want
to clone the laptop's annex to it:
# git clone ssh://mylaptop/home/me/annex ~/annex
# cd ~/annex
# git annex init "my desktop"
desktop# git clone ssh://mylaptop/home/me/annex ~/annex
desktop# cd ~/annex
desktop# git annex init "my desktop"
Now you can get files and they will be transferred (using `rsync` via `ssh`):
# git annex get my_cool_big_file
desktop# git annex get my_cool_big_file
get my_cool_big_file (getting UUID for origin...) (from origin...)
SHA256-s86050597--6ae2688bc533437766a48aa19f2c06be14d1bab9c70b468af445d4f07b65f41e 100% 2159 2.1KB/s 00:00
ok
@ -19,7 +19,7 @@ Now you can get files and they will be transferred (using `rsync` via `ssh`):
When you drop files, git-annex will ssh over to the remote and make
sure the file's content is still there before removing it locally:
# git annex drop my_cool_big_file
desktop# git annex drop my_cool_big_file
drop my_cool_big_file (checking origin..) ok
Note that normally git-annex prefers to use non-ssh remotes, like