From ffec23d7b099e71e8bae7daee032fccc60824980 Mon Sep 17 00:00:00 2001 From: andrew Date: Sun, 20 Jan 2019 21:14:03 +0000 Subject: [PATCH] Added a comment --- .../comment_4_4afea3a65b6b5c57a4dac5cdbbf89432._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/use_case_question__58___developer_repo_with_s3/comment_4_4afea3a65b6b5c57a4dac5cdbbf89432._comment diff --git a/doc/forum/use_case_question__58___developer_repo_with_s3/comment_4_4afea3a65b6b5c57a4dac5cdbbf89432._comment b/doc/forum/use_case_question__58___developer_repo_with_s3/comment_4_4afea3a65b6b5c57a4dac5cdbbf89432._comment new file mode 100644 index 0000000000..9ead218908 --- /dev/null +++ b/doc/forum/use_case_question__58___developer_repo_with_s3/comment_4_4afea3a65b6b5c57a4dac5cdbbf89432._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="andrew" + avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435" + subject="comment 4" + date="2019-01-20T21:14:03Z" + content=""" +Great, glad to hear this setup might work for you. Also, I also forgot to mention another drawback with `encryption=pubkey` is that you can't easily add add a key for a newly added developer later on, if you want to add a new developer key after you have uploaded files to s3 you will have to drop all the files, add the new key to git-annex, make sure all your devs do a `git-annex sync` to get the new set of public keys to use for encryption, then re-upload all the files to s3. +"""]]