psi-jack/yadm
1
0
Fork 0
mirror of synced 2024-11-05 17:28:59 -05:00
Code Issues Releases Wiki Activity

Update encryption info in FAQ

Browse source
This commit is contained in:
LFdev 2023-11-14 14:19:35 -03:00
parent 21a95d05e0
commit 64864ba10a
No known key found for this signature in database
GPG key ID: 2F374E5CD5D09119
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
_docs/110_faq.md
View file

@ -113,18 +113,18 @@ you when you clone your repository.
### Should I `yadm add` encrypted files to repository?
No, you should not. Files you want encrypted should be added to the file
`.config/yadm/files.gpg` using the `yadm encrypt` command. Then
`.config/yadm/files.gpg` should be added to the yadm repository. This way, only
`$HOME/.local/share/yadm/archive` using the `yadm encrypt` command. Then
`$HOME/.local/share/yadm/archive` should be added to the yadm repository. This way, only
an encrypted collection of those files are put into the repository. After
cloning or updating your repository, you can use `yadm decrypt` to extract those
files from `.config/yadm/files.gpg`. See the
files from `$HOME/.local/share/yadm/archive`. See the
[encryption help](encryption) for more details.
### I modified an encrypted file, but yadm doesn't show any modifications. Why?
If you changed files which are matched by `.config/yadm/encrypt`, you must
re-run `yadm encrypt` to generate a new version of `.config/yadm/files.gpg`.
Then `.config/yadm/files.gpg` can be added to a new commit.
re-run `yadm encrypt` to generate a new version of `$HOME/.local/share/yadm/archive`.
Then `$HOME/.local/share/yadm/archive` can be added to a new commit.
### Why do I get the error `Inappropriate ioctl for device` when encrypting.