aboutsummaryrefslogtreecommitdiff
path: root/doc/backends.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-27 22:52:13 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-27 22:52:13 -0400
commitc0fd38bfa9ade9dc4515140cf5cf5619582c5a89 (patch)
treedfb118de1277ce5a1f5beeb07d413486c76a7f5d /doc/backends.mdwn
parent65b72604d73b1d92dea1d81984964394235834bb (diff)
document S3 remotes
Diffstat (limited to 'doc/backends.mdwn')
-rw-r--r--doc/backends.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/backends.mdwn b/doc/backends.mdwn
index 22164850a..b0a2c882a 100644
--- a/doc/backends.mdwn
+++ b/doc/backends.mdwn
@@ -9,6 +9,10 @@ to retrieve the file's content (its value).
Multiple pluggable backends are supported, and a single repository
can use different backends for different files.
+These backends can transfer file contents in configured git remotes.
+It's also possible to use [[special_remotes]], such as Amazon S3 with
+these backends.
+
* `WORM` ("Write Once, Read Many") This backend assumes that any file with
the same basename, size, and modification time has the same content. So with
this backend, files can be moved around, but should never be added to
@@ -19,6 +23,9 @@ can use different backends for different files.
* `SHA512`, `SHA384`, `SHA256`, `SHA224` -- Like SHA1, but larger
checksums. Mostly useful for the very paranoid, or anyone who is
researching checksum collisions and wants to annex their colliding data. ;)
+
+These backends store file contents in other key/value stores.
+
* `URL` -- This backend downloads the file's content from an external URL.
The `annex.backends` git-config setting can be used to list the backends