Update man. #218 [ci skip]

man/aptly.1.ronn.tmpl

@@ -44,13 +44,15 @@ Configuration file is stored in JSON format (default values shown below):
         "test": {
           "region": "us-east-1",
           "bucket": "repo",
+          "endpoint": "",
           "awsAccessKeyID": "",
           "awsSecretAccessKey": "",
           "prefix": "",
           "acl": "public-read",
           "storageClass": "",
           "encryptionMethod": "",
-          "plusWorkaround": false
+          "plusWorkaround": false,
+          "disableMultiDel": false
         }
       },
       "SwiftPublishEndpoints": {
@@ -118,7 +120,8 @@ Options:
 
 ## S3 PUBLISHING ENDPOINTS
 
-aptly could be configured to publish repository directly to Amazon S3. First, publishing
+aptly could be configured to publish repository directly to Amazon S3 (or S3-compatible
+cloud storage). First, publishing
 endpoints should be described in aptly configuration file. Each endpoint has name
 and associated settings:
 
@@ -126,6 +129,10 @@ and associated settings:
      Amazon region for S3 bucket (e.g. `us-east-1`)
    * `bucket`:
      bucket name
+   * `endpoint`:
+     (optional) when using S3-compatible cloud storage, specify hostname of service endpoint here,
+     region is ignored if endpoint is set (set region to some human-readable name)
+     (should be left blank for real Amazon S3)
    * `prefix`:
      (optional) do publishing under specified prefix in the bucket, defaults to
      no prefix (bucket root)
@@ -152,7 +159,10 @@ and associated settings:
      and another one with spaces instead of plus signs
      With `plusWorkaround` enabled, package files with plus sign
      would be stored twice. aptly might not cleanup files with spaces when published
-     repository is dropped or updated (switched) to new version of repository (snapshot).
+     repository is dropped or updated (switched) to new version of repository (snapshot)
+   * `disableMultiDel`:
+     for S3-compatible cloud storages which do not support `MultiDel` S3 API,
+     enable this setting (file deletion would be slower with this setting enabled)
 
 In order to publish to S3, specify endpoint as `s3:endpoint-name:` before
 publishing prefix on the command line, e.g.: