Deployed 7468e82 to 12.0 with MkDocs 1.6.1 and mike 2.1.3

haiwen · Nov 11, 2024 · 5fe1c8d · 5fe1c8d
1 parent 351d474
commit 5fe1c8d
Show file tree

Hide file tree

Showing 4 changed files with 120 additions and 124 deletions.
diff --git a/12.0/search/search_index.json b/12.0/search/search_index.json
diff --git a/12.0/setup/setup_with_amazon_s3/index.html b/12.0/setup/setup_with_amazon_s3/index.html
@@ -4576,10 +4576,6 @@ <h2 id="self-hosted-s3-storage">Self-hosted S3 Storage<a class="headerlink" href
 <td><code>use_v4_signature</code></td>
 <td>There are two versions of authentication protocols that can be used with S3 storage. Version 2 is the protocol supported by most self-hosted storage; version 4 is the current protocol used by AWS S3, but may not be supported by some self-hosted storage. If you don't set this option, Seafile will use the v2 protocol by default. We recommend to use V4 if possible. Please note that if you want to migrate from S3 storage to other storage, the migration script doesn't work with V2 authentication protocol due to limitation of third-party library.</td>
 </tr>
-<tr>
-<td><code>aws_region</code></td>
-<td>If you use the v4 protocol, set this option to the region you chose when you created the buckets. If it's not set and you're using the v4 protocol, Seafile will use <code>us-east-1</code> as the default. This default value should work with most self-hosted S3 storage. This option will be ignored if you use the v2 protocol.</td>
-</tr>
 </tbody>
 </table>
 <h2 id="use-https-connections-to-s3">Use HTTPS connections to S3<a class="headerlink" href="#use-https-connections-to-s3" title="Permanent link">&para;</a></h2>