summaryrefslogtreecommitdiff
path: root/doc/todo/S3.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-29 18:30:41 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-29 18:30:41 -0400
commite7c1332fa2f447f46781641821d1ff2c71716657 (patch)
treef34dac416d3d3f182a25403c862b974b657b31ed /doc/todo/S3.mdwn
parent8f9951369d5e85e3a1bf323760f0c873a3f21b97 (diff)
updat
Diffstat (limited to 'doc/todo/S3.mdwn')
-rw-r--r--doc/todo/S3.mdwn28
1 files changed, 5 insertions, 23 deletions
diff --git a/doc/todo/S3.mdwn b/doc/todo/S3.mdwn
index 356b2af2e..dd0174cc5 100644
--- a/doc/todo/S3.mdwn
+++ b/doc/todo/S3.mdwn
@@ -1,33 +1,15 @@
-[[done]]
-
Support Amazon S3 as a file storage backend.
There's a haskell library that looks good. Not yet in Debian.
-Multiple ways of using S3 are possible. Current plan is to
-have a special type of git remote (though git won't know how to use it;
-only git-annex will) that uses a S3 bucket.
-
-Something like:
-
- [remote "s3"]
- annex-s3bucket = mybucket
- annex-s3datacenter = Europe
- annex-uuid = 1a586cf6-45e9-11e0-ba9c-3b0a3397aec2
- annex-cost = 500
-
-The UUID will be stored as a special file in the S3 bucket.
+Multiple ways of using S3 are possible. Currently implemented as
+a special type of git remote.
-Using a different type of remote like this will allow S3 to be used
-anywhere a regular remote would be used. `git annex get` will transparently
-download a file from S3 if S3 has it and is the cheapest remote.
+Before this can be close, I need to fix:
- git annex copy --to s3
- git annex move --from s3
- git annex drop --from s3 # not currently allowed, will need adding
+## encryption
-Each s3 remote will count as one copy for numcopies handling, just like
-any other remote.
+TODO
## unused checking