vincent/aptly
1
0
Fork 0
mirror of https://github.com/aptly-dev/aptly.git synced 2026-06-09 06:04:12 +00:00
Code Issues Projects Releases Wiki Activity

Document additional S3 options [ci skip]

Browse Source
This commit is contained in:
Andrey Smirnov
2017-07-21 00:57:06 +03:00
parent fcd453118b
commit 58ab4e8902
2 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/aptly.1
+8
View File
@@ -235,6 +235,14 @@ bucket name
\fBdisableMultiDel\fR \fBdisableMultiDel\fR
(optional) for S3\-compatible cloud storages which do not support \fBMultiDel\fR S3 API, enable this setting (file deletion would be slower with this setting enabled) (optional) for S3\-compatible cloud storages which do not support \fBMultiDel\fR S3 API, enable this setting (file deletion would be slower with this setting enabled)
. .
.TP
\fBforceSigV2\fR
(optional) disable Signature V4 support, useful with non\-AWS S3\-compatible object stores which do not support SigV4, shouldn\(cqt be enabled for AWS
.
.TP
\fBdebug\fR
(optional) enables detailed request/response dump for each S3 operation
.
.P .P
In order to publish to S3, specify endpoint as \fBs3:endpoint\-name:\fR before publishing prefix on the command line, e\.g\.: In order to publish to S3, specify endpoint as \fBs3:endpoint\-name:\fR before publishing prefix on the command line, e\.g\.:
. .
man/aptly.1.ronn.tmpl
+5
View File
@@ -222,6 +222,11 @@ and associated settings:
* `disableMultiDel`: * `disableMultiDel`:
(optional) for S3-compatible cloud storages which do not support `MultiDel` S3 API, (optional) for S3-compatible cloud storages which do not support `MultiDel` S3 API,
enable this setting (file deletion would be slower with this setting enabled) enable this setting (file deletion would be slower with this setting enabled)
* `forceSigV2`:
(optional) disable Signature V4 support, useful with non-AWS S3-compatible object stores
which do not support SigV4, shouldn't be enabled for AWS
* `debug`:
(optional) enables detailed request/response dump for each S3 operation
In order to publish to S3, specify endpoint as `s3:endpoint-name:` before In order to publish to S3, specify endpoint as `s3:endpoint-name:` before
publishing prefix on the command line, e.g.: publishing prefix on the command line, e.g.: