diff options
author | 2017-09-08 15:41:31 -0400 | |
---|---|---|
committer | 2017-09-08 15:46:24 -0400 | |
commit | 5ef1c9b5690057e5b18dc7dcc3627776b400c544 (patch) | |
tree | f71d9ad13509977736bd55698cb4ccc18311e091 /doc/special_remotes/S3.mdwn | |
parent | 23f55c0efdd58f8024d9b0c9e4b02db7b8d27b61 (diff) |
S3 export (untested)
It opens a http connection per file exported, but then so does git
annex copy --to s3.
Decided not to munge exported filenames for IA. Too large a chance of
the munging having confusing results. Instead, export of files not
supported by IA, eg with spaces in their name, will fail.
This commit was supported by the NSF-funded DataLad project.
Diffstat (limited to 'doc/special_remotes/S3.mdwn')
-rw-r--r-- | doc/special_remotes/S3.mdwn | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/special_remotes/S3.mdwn b/doc/special_remotes/S3.mdwn index d526d35f5..138105f1d 100644 --- a/doc/special_remotes/S3.mdwn +++ b/doc/special_remotes/S3.mdwn @@ -66,6 +66,10 @@ the S3 remote. so by default, a bucket name is chosen based on the remote name and UUID. This can be specified to pick a bucket name. +* `exporttree` - Set to "yes" to make this special remote usable + by [[git-annex-export]]. It will not be usable as a general-purpose + special remote. + * `public` - Set to "yes" to allow public read access to files sent to the S3 remote. This is accomplished by setting an ACL when each file is uploaded to the remote. So, changes to this setting will |