summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-05-16 11:46:34 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-05-16 11:46:34 -0400
commit2a8efc7af19aa149dbf0ebc158954bb376f9c3a6 (patch)
tree879eef3ffe3c8bdac8cb9b489f8298a00f058042 /doc
parent1d2984441c654f01e88e427f3289f8066cd2e6b0 (diff)
Added filename extension preserving variant backends SHA1E, SHA256E, etc.
Diffstat (limited to 'doc')
-rw-r--r--doc/backends.mdwn3
-rw-r--r--doc/walkthrough/Internet_Archive_via_S3.mdwn18
2 files changed, 11 insertions, 10 deletions
diff --git a/doc/backends.mdwn b/doc/backends.mdwn
index b0a2c882a..4290da33b 100644
--- a/doc/backends.mdwn
+++ b/doc/backends.mdwn
@@ -23,6 +23,9 @@ these backends.
* `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. ;)
+* `SHA1E`, `SHA512E`, etc -- Variants that preserve filename extension as
+ part of the key. Useful for archival tasks where the filename extension
+ contains metadata that should be preserved.
These backends store file contents in other key/value stores.
diff --git a/doc/walkthrough/Internet_Archive_via_S3.mdwn b/doc/walkthrough/Internet_Archive_via_S3.mdwn
index e0f8fafb4..f92e0ee9d 100644
--- a/doc/walkthrough/Internet_Archive_via_S3.mdwn
+++ b/doc/walkthrough/Internet_Archive_via_S3.mdwn
@@ -32,20 +32,18 @@ specify `x-archive-meta*` headers to add metadata as explained in their
Then you can annex files and copy them to the remote as usual:
- # git annex add photo1.jpeg
- add photo1.jpeg ok
+ # git annex add photo1.jpeg --backend=SHA1E
+ add photo1.jpeg (checksum...) ok
# git annex copy photo1.jpeg --fast --to archive-panama
copy (to archive-panama...) ok
------
+Note the use of the SHA1E [[backend|backends]]. It makes most sense
+to use the WORM or SHA1E backend for files that will be stored in
+the Internet Archive, since the key name will be exposed as the filename
+there, and since the Archive does special processing of files based on
+their extension.
-Note that it probably makes the most sense to use the WORM backend
-for files, since that exposes the original filename in the key stored
-in the Archive, which allows its special processing for sound files,
-movies, etc to be done.
-
-Also, the Internet Archive has restrictions on what is allowed in a
-filename; particularly no spaces are allowed.
+----
There seems to be a bug in either hS3 or the archive that breaks
authentication when the bucket name contains spaces or upper-case letters..