astelm/minio
1
0
Fork 0
mirror of https://github.com/pgsty/minio.git synced 2026-08-02 16:45:57 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs: point documentation links to silo.pigsty.io (#41)

Browse Source 
Replace upstream docs.min.io references with the SILO documentation domain and remove the upstream community path prefix.

Co-authored-by: waterkip <6317502+waterkip@users.noreply.github.com>
This commit is contained in:
Wesley Schwengle
2026-07-20 07:43:45 -04:00
committed by Feng Ruohang
parent 3e61b1d3a5
commit d495d30d57
57 changed files with 458 additions and 198 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/site-replication/README.md
+1 -1
View File
@@ -25,7 +25,7 @@ The following Bucket features will **not be replicated**, is designed to differ
- **Removing a site** is not allowed from a set of replicated sites once configured.
- All sites must be using the **same** external IDP(s) if any.
- For [SSE-S3 or SSE-KMS encryption via KMS](https://docs.min.io/community/minio-object-store/operations/server-side-encryption.html "MinIO KMS Guide"), all sites **must** have access to a central KMS deployment. This can be achieved via a central KES server or multiple KES servers (say one per site) connected via a central KMS (Vault) server.
- For [SSE-S3 or SSE-KMS encryption via KMS](https://silo.pigsty.io/operations/server-side-encryption.html "MinIO KMS Guide"), all sites **must** have access to a central KMS deployment. This can be achieved via a central KES server or multiple KES servers (say one per site) connected via a central KMS (Vault) server.
## Configuring Site Replication