summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar krazyjosh5@ab1e3964e59d02a093b27f93562012e47aa2b4c9 <krazyjosh5@web>2016-07-05 15:00:33 +0000
committerGravatar admin <admin@branchable.com>2016-07-05 15:00:33 +0000
commit0de154a03a28d45ed40ccade681d72b0ca22e530 (patch)
tree9f27df4f94602fab19e832f3633f18eb5885e3c2
parent182b47d902ead0e3a8acd9f9b7a6201102444bf7 (diff)
-rw-r--r--doc/forum/git-annex_SSH_server_+_cloud_remote.mdwn8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/forum/git-annex_SSH_server_+_cloud_remote.mdwn b/doc/forum/git-annex_SSH_server_+_cloud_remote.mdwn
index 3c0cb4aa7..873b75650 100644
--- a/doc/forum/git-annex_SSH_server_+_cloud_remote.mdwn
+++ b/doc/forum/git-annex_SSH_server_+_cloud_remote.mdwn
@@ -1,13 +1,13 @@
I'd like to accomplish something like this:
-* shared git-annex remote hosted by SSL server
+* shared git-annex remote hosted by SSH server
* file contents stored in S3
* everything encrypted
-The use case here is to achieve the availability of an SSL server (that is, multiple clients will sync to one, main server, eliminating a dependency on each other) and a single source of truth for the repository (i.e. eliminating P2P repo synchronization), and having the bulk of the disk space consumption living on S3 hosting.
+The use case here is to achieve the availability of an SSH server (that is, multiple clients will sync to one, main server, eliminating a dependency on each other) and a single source of truth for the repository (i.e. eliminating P2P repo synchronization), and having the bulk of the disk space consumption living on S3 hosting.
-Is this possible? If so, any suggestions on how to do it? I understand how to do everything, except configure the SSL server to store annexed files on S3 hosting.
+Is this possible? If so, any suggestions on how to do it? I understand how to do everything, except configure the SSH server to store annexed files on S3 hosting.
-Also, any thoughts on how much space the SSL server's git repo (without annexed files) could possibly grow to, with average use? Is it reasonable to say that it would never get bigger than 'tens of megabytes'?
+Also, any thoughts on how much space the SSH server's git repo (without annexed files) could possibly grow to, with average use? Is it reasonable to say that it would never get bigger than 'tens of megabytes'?
Thank you!