This commit is contained in:
Joey Hess 2011-05-16 11:52:33 -04:00
parent e7b309ce02
commit b4301c208f

View file

@ -3,11 +3,10 @@ collections using an Amazon S3
[compatible API](http://www.archive.org/help/abouts3.txt), and this can
be used with git-annex's [[special_remotes/S3]] support.
So, if you're an archivist, you can locally archive things with git-annex,
and define remotes that correspond to "items" at the Internet Archive,
and use git-annex to upload your files to there.
Of course, your use of the Internet Archive must comply with their
[terms of service](http://www.archive.org/about/terms.php).
So, you can locally archive things with git-annex, define remotes that
correspond to "items" at the Internet Archive, and use git-annex to upload
your files to there. Of course, your use of the Internet Archive must
comply with their [terms of service](http://www.archive.org/about/terms.php).
Sign up for an account, and get your access keys here:
<http://www.archive.org/account/s3.php>
@ -22,8 +21,14 @@ rather than letting git-annex pick a random one; and you can optionally
specify `x-archive-meta*` headers to add metadata as explained in their
[documentation](http://www.archive.org/help/abouts3.txt).
# git annex initremote archive-panama type=S3
# host=s3.us.archive.org bucket=panama-canal-lock-blueprints \
[[!template id=note text="""
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..
use all lowercase and no spaces when making the bucket with `initremote`.
"""]]
# git annex initremote archive-panama type=S3 \
host=s3.us.archive.org bucket=panama-canal-lock-blueprints \
x-archive-meta-mediatype=texts x-archive-meta-language=eng \
x-archive-meta-title="original Panama Canal lock design blueprints"
initremote archive-panama (Internet Archive mode) (checking bucket) (creating bucket in US) ok
@ -42,9 +47,3 @@ 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.
----
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..
use all lowercase and no spaces when making the bucket with `initremote`.