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

change back to git-remote-gcrypt 1.4 url forms, with a note that that version is needed

Browse source
This commit is contained in:
Joey Hess 2021-04-13 12:55:50 -04:00
parent 6f7730f6cf
commit 948dd8a0cc
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 11 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/special_remotes/gcrypt.mdwn
View file

@ -32,14 +32,11 @@ gcrypt:
To use a local git repository, use: `gitrepo=/path/to/repo`
For a git repository accessed using rsync over ssh, use:
`gitrepo=rsync://user@host:/path/to/repo`
For a git repository accessed over ssh, and using git-annex-shell
to transfer data, use:
`gitrepo=ssh://user@host/path/to/repo` or `gitrepo=host:path`
For a git repository accessed over ssh, an `rsync://` url uses rsync over
ssh, while a `ssh://` url uses git-annex-shell over ssh.
Note that each `git push` has to re-send the whole content of the git
repository when using this option.
repository when using the latter option, so rsync urls are generally more
efficient.
* `chunk` - Enables [[chunking]] when storing large files.

10
doc/tips/fully_encrypted_git_repositories_with_gcrypt.mdwn
View file

@ -13,7 +13,7 @@ repositories.
## prerequisites
* Install [git-remote-gcrypt](https://spwhitton.name/tech/code/git-remote-gcrypt/)
* Install [git-remote-gcrypt](https://spwhitton.name/tech/code/git-remote-gcrypt/).
* Set up a gpg key. You might consider generating a special purpose key
just for this use case, since you may end up wanting to put the key
@ -70,13 +70,17 @@ If you have a server that has ssh and rsync installed on it, you can set up an
encrypted repository there. Works just like the encrypted drive except
without the cable.
This example uses rsync urls in a form supported by git-remote-gcrypt since
version 1.4. Older versions won't work with the urls used here, consult
its documentation if you have to use an old version.
First, on the server, run:
git init --bare encryptedrepo
Now, in your existing git-annex repository, set up the encrypted remote:
git annex initremote encryptedrepo type=gcrypt gitrepo=rsync://my.server:/home/me/encryptedrepo keyid=$mykey
git annex initremote encryptedrepo type=gcrypt gitrepo=rsync://my.server/home/me/encryptedrepo keyid=$mykey
git annex sync encryptedrepo
(Remember to replace "$mykey" with the keyid of your gpg key.)
@ -100,7 +104,7 @@ used to encrypt it can check it out:
git clone gcrypt::rsync://my.server/home/me/encryptedrepo myrepo
cd myrepo
git annex enableremote encryptedrepo gitrepo=rsync://my.server:/home/me/encryptedrepo
git annex enableremote encryptedrepo gitrepo=rsync://my.server/home/me/encryptedrepo
git annex get --from encryptedrepo
## private encrypted git remote on a git-lfs hosting site