From b642800d8cddde394d859b0e839eb6a500667f6b Mon Sep 17 00:00:00 2001 From: mih Date: Thu, 17 Oct 2024 20:26:08 +0000 Subject: [PATCH] Tag with project ID --- doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site.mdwn b/doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site.mdwn index 7064048b83..f637a5addb 100644 --- a/doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site.mdwn +++ b/doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site.mdwn @@ -12,3 +12,5 @@ There is the gcrypt special remote (and it worked with the forgejo instance I tr The advantage of having the annexed files but not the git repo encrypted is that the file tree, commit history, readme and all the things typically displayed by the site would still be viewable (communicating repository layout, contents), but GPG keys would be used to control practical access (possibly on top of site's access premissions). Thanks in advance for considering! -- MSz + +[[!tag projects/INM7]]