From 3590a17f9e18243d345ba99beab25205c6aad1ab Mon Sep 17 00:00:00 2001 From: "m.risse@77eac2c22d673d5f10305c0bade738ad74055f92" Date: Tue, 16 Jul 2024 09:21:54 +0000 Subject: [PATCH] Added a comment --- .../comment_1_1f06e694a186d8801730f1f6cc48a995._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/design/p2p_protocol_over_http/comment_1_1f06e694a186d8801730f1f6cc48a995._comment diff --git a/doc/design/p2p_protocol_over_http/comment_1_1f06e694a186d8801730f1f6cc48a995._comment b/doc/design/p2p_protocol_over_http/comment_1_1f06e694a186d8801730f1f6cc48a995._comment new file mode 100644 index 0000000000..543e359ad0 --- /dev/null +++ b/doc/design/p2p_protocol_over_http/comment_1_1f06e694a186d8801730f1f6cc48a995._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="m.risse@77eac2c22d673d5f10305c0bade738ad74055f92" + nickname="m.risse" + avatar="http://cdn.libravatar.org/avatar/59541f50d845e5f81aff06e88a38b9de" + subject="comment 1" + date="2024-07-16T09:21:54Z" + content=""" +I just want to say that this would be nice to have for https://codeberg.org/matrss/forgejo-aneksajo as well, since only being able to use ssh is a pain point in some places (e.g. outgoing ssh connections are forbidden on the HPC systems at FZ Jülich, which means an intermediary is necessary to copy data from the HPC systems to a forgejo-aneksajo instance, currently). Being able to read and write via https (possibly reusing the existing access tokens from forgejo? That would be on me to see if it is doable) would alleviate this problem entirely. +"""]]