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

fix example that combined encryption=shared with keyid=

Browse source
This commit is contained in:
Joey Hess 2024-01-19 20:41:55 -04:00
parent 1f8996614e
commit f8b73e0286
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment
View file

@ -9,7 +9,7 @@ sufficient to back that up. You can run `git annex enableremote`
in an clone to enable an existing special remote.
The only catch is that, if you have chosen to initremote a special remote
using a gpg key, with `encryption=shared keyid=whatever`, you'll of course
using a gpg key, with `keyid=whatever`, you'll of course
also need that gpg key to to use it. If you run `git annex info $myremote`
it will tell you amoung other things, any gpg keys that are used by that
remote.

4
doc/special_remotes/rsync.mdwn
View file

@ -2,12 +2,12 @@ This special remote type rsyncs file contents to somewhere else.
Setup example:
# git annex initremote myrsync type=rsync rsyncurl=rsync://rsync.example.com/myrsync keyid=id@joeyh.name encryption=shared
# git annex initremote myrsync type=rsync rsyncurl=rsync://rsync.example.com/myrsync encryption=shared
# git annex describe myrsync "rsync server"
Or for using rsync over SSH
# git annex initremote myrsync type=rsync rsyncurl=ssh.example.com:/myrsync keyid=id@joeyh.name encryption=shared
# git annex initremote myrsync type=rsync rsyncurl=ssh.example.com:/myrsync encryption=shared
# git annex describe myrsync "rsync server"
## configuration