This commit is contained in:
parent
d81765cb73
commit
19fbc10360
1 changed files with 13 additions and 0 deletions
13
doc/forum/git-annex_SSH_server_+_cloud_remote.mdwn
Normal file
13
doc/forum/git-annex_SSH_server_+_cloud_remote.mdwn
Normal file
|
@ -0,0 +1,13 @@
|
||||||
|
I'd like to accomplish something like this:
|
||||||
|
|
||||||
|
* shared git-annex remote hosted by SSL 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.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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'?
|
||||||
|
|
||||||
|
Thank you!
|
Loading…
Add table
Add a link
Reference in a new issue