aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-07-05 11:51:49 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-07-05 11:51:49 -0400
commitdc003f82bfc8e90786abda21d62e96911071fe14 (patch)
treef875b2b69a696cf08344e839eff7f4d2868e8029 /doc
parent618fdd89517b6756e35e4b0f1b97557006114f28 (diff)
parent0de154a03a28d45ed40ccade681d72b0ca22e530 (diff)
Merge branch 'master' of ssh://git-annex.branchable.com
Diffstat (limited to 'doc')
-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!