@@ -26,9 +30,21 @@
## Overview
-Silo maintains one downstream release line based on MinIO [`RELEASE.2025-12-03T12-00-00Z`](https://github.com/minio/minio/releases/tag/RELEASE.2025-12-03T12-00-00Z). It provides maintained builds and release artifacts for existing MinIO-compatible deployments after upstream community distribution ended.
+Silo maintains one downstream release line based on MinIO [`RELEASE.2025-12-03T12-00-00Z`](https://github.com/minio/minio/releases/tag/RELEASE.2025-12-03T12-00-00Z). It provides maintained builds and release artifacts for existing MinIO-compatible deployments after upstream community distribution ended. Pigsty uses this fork for object storage as an optional PG backup repo.
-Pigsty uses this fork for object storage, including PostgreSQL backups.
+The official project portal is [silo.pgsty.com](https://silo.pgsty.com/). It brings documentation, downloads, release and security notes, and project background together. English is served at the site root; Chinese is available under [/zh/](https://silo.pgsty.com/zh/).
+
+## Find the Right Resource
+
+| Looking for | Canonical location |
+| :-- | :-- |
+| Project overview and navigation | [Silo Website](https://silo.pgsty.com/) ([中文](https://silo.pgsty.com/zh/)) |
+| Installation methods and downloads | [Download & Install](https://silo.pgsty.com/download/) ([中文](https://silo.pgsty.com/zh/download/)) |
+| Operations, administration, development, and reference | [Documentation](https://silo.pgsty.com/docs/) ([中文](https://silo.pgsty.com/zh/docs/)) |
+| Project news, release notes, and security notes | [Blog](https://silo.pgsty.com/blog/), including [releases](https://silo.pgsty.com/blog/release/) and [security](https://silo.pgsty.com/blog/security/) |
+| Versioned binaries, checksums, and source archives | [GitHub Releases](https://github.com/pgsty/minio/releases) |
+| Bug reports and feature discussions | [GitHub Issues](https://github.com/pgsty/minio/issues) |
+| License, attribution, and trademark information | [License](https://silo.pgsty.com/about/license/), [Attribution](https://silo.pgsty.com/about/attribution/), and [Trademark](https://silo.pgsty.com/about/trademark/) |
## Maintenance Policy
@@ -54,24 +70,24 @@ Changes are kept narrow and tested where practical. Maintenance is best effort;
Silo aims to preserve:
-- the `minio` executable and `github.com/minio/minio` module path;
- MinIO-compatible S3 APIs, configuration, environment variables, and CLI conventions;
- `RELEASE.YYYY-MM-DDTHH-MM-SSZ` tags, container entrypoints, and common deployment workflows.
-Compatibility is a goal, not a guarantee. Security fixes may change behavior. Treat each release as a downstream upgrade: pin versions, review [release notes](https://github.com/pgsty/minio/releases) and [security advisories](docs/security/advisories.md), keep a rollback path, and test before production use.
+Compatibility is the default constraint. Silo preserves existing wire, client, configuration, and operational behavior whenever doing so remains safe. Compatibility is broken only when necessary to close a major security issue, and the release notes must identify the affected behavior and migration path. Treat each release as a downstream upgrade: pin versions, review [release notes](https://silo.pgsty.com/blog/release/) and [security advisories](docs/security/advisories.md), keep a rollback path, and test before production use.
-## Release Artifacts
+## Downloads and Release Artifacts
+
+Use [Download & Install](https://silo.pgsty.com/download/) to choose an installation method. GitHub Releases remains the source for versioned server binaries, checksums, and source archives.
| Artifact | Location |
| :-- | :-- |
| Source | [`github.com/pgsty/minio`](https://github.com/pgsty/minio) |
| Container image | [`pgsty/minio`](https://hub.docker.com/r/pgsty/minio), multi-arch for `linux/amd64` and `linux/arm64` |
-| Server binaries | [GitHub Releases](https://github.com/pgsty/minio/releases) for Linux, macOS, and Windows on `amd64` and `arm64` |
+| Server binaries and checksums | [GitHub Releases](https://github.com/pgsty/minio/releases) for Linux, macOS, and Windows on `amd64` and `arm64` |
| Linux packages | RPM, DEB, and APK artifacts, also distributed through the [Pigsty repository](https://pigsty.io/docs/repo/) |
| Client | [`pgsty/mc`](https://github.com/pgsty/mc), bundled in the container as `mcli` with an `mc` compatibility alias |
| Console | Maintained [`georgmangold/console`](https://github.com/georgmangold/console) fork, embedded in the server build |
-| Documentation | [English](https://silo.pigsty.io), [Chinese](https://silo.pigsty.cc), and [`pgsty/minio-docs`](https://github.com/pgsty/minio-docs) |
-| Security record | [`SECURITY.md`](SECURITY.md), [`VULNERABILITY_REPORT.md`](VULNERABILITY_REPORT.md), and [fork advisories](docs/security/advisories.md) |
+| Shared library | [`pgsty/silo-pkg`](https://github.com/pgsty/silo-pkg) v3.7.0, consumed through a `replace` directive while preserving `github.com/minio/pkg/v3` import paths ([release notes](https://silo.pgsty.com/blog/release/pkg-3.7.0/)) |
## Quick Start
@@ -113,11 +129,11 @@ go build -o minio .
./minio --version
```
-Deployment: [Silo documentation](https://silo.pigsty.io) · [Pigsty MinIO module](https://pigsty.io/docs/minio/)
+For other installation paths—including native packages, binaries, Podman, Kubernetes, source, and Pigsty Ansible—use [Download & Install](https://silo.pgsty.com/download/). For production deployment and administration, start with the [Silo documentation](https://silo.pgsty.com/docs/). Pigsty users can also use the [Pigsty MinIO module](https://pigsty.io/docs/minio/).
## Security
-Security fixes target the active `master` branch and are recorded in the [advisory log](docs/security/advisories.md). Report vulnerabilities privately as described in [`SECURITY.md`](SECURITY.md) and [`VULNERABILITY_REPORT.md`](VULNERABILITY_REPORT.md). Report issues that also affect upstream MinIO there as well.
+Security fixes target the active `master` branch and are recorded in the [advisory log](docs/security/advisories.md) and the portal's [security notes](https://silo.pgsty.com/blog/security/). Report vulnerabilities privately as described in [`SECURITY.md`](SECURITY.md) and [`VULNERABILITY_REPORT.md`](VULNERABILITY_REPORT.md). Report issues that also affect upstream MinIO there as well.
## Contributing
@@ -131,9 +147,9 @@ This project was created in response to changes in the upstream community distri
| Essay | Subject |
| :-- | :-- |
-| [MinIO Is Dead](https://blog.vonng.com/en/db/minio-is-dead/) | Changes to the upstream project and distribution model |
-| [MinIO Is Dead, Long Live MinIO](https://blog.vonng.com/en/db/minio-resurrect/) | Establishing the fork and its release pipeline |
-| [Two months into maintaining a MinIO fork](https://blog.vonng.com/en/db/minio-promise-kept/) | Initial security and maintenance work |
+| [MinIO Is Dead](https://silo.pgsty.com/blog/post/minio-is-dead/) | Changes to the upstream project and distribution model |
+| [MinIO Is Dead, Long Live MinIO](https://silo.pgsty.com/blog/post/minio-resurrect/) | Establishing the fork and its release pipeline |
+| [Two months into maintaining a MinIO fork](https://silo.pgsty.com/blog/post/minio-promise-kept/) | Initial security and maintenance work |
## License and Trademark
diff --git a/README_ZH.md b/README_ZH.md
index fb8f729d5..4cd6b4c46 100644
--- a/README_ZH.md
+++ b/README_ZH.md
@@ -1,8 +1,7 @@
-
@@ -33,6 +34,21 @@ Silo 维护一条基于 MinIO [`RELEASE.2025-12-03T12-00-00Z`](https://github.co
Pigsty 使用本分支提供对象存储，包括 PostgreSQL 备份存储。
+项目统一门户为 [silo.pgsty.com](https://silo.pgsty.com/zh/)，集中提供文档、下载安装、版本与安全动态及项目背景。中文内容位于 `/zh/`，英文内容位于站点根路径。
+
+## 按需求选择入口
+
+| 需求 | 权威入口 |
+| :-- | :-- |
+| 项目概览与全站导航 | [Silo 中文门户](https://silo.pgsty.com/zh/)（[English](https://silo.pgsty.com/)） |
+| 安装方式与软件下载 | [下载与安装](https://silo.pgsty.com/zh/download/)（[English](https://silo.pgsty.com/download/)） |
+| 运维、管理、开发与参考指南 | [中文文档](https://silo.pgsty.com/zh/docs/)（[English](https://silo.pgsty.com/docs/)） |
+| 项目动态、版本说明与安全通告 | [博客](https://silo.pgsty.com/zh/blog/)，包括[版本发布](https://silo.pgsty.com/zh/blog/release/)与[安全通告](https://silo.pgsty.com/zh/blog/security/) |
+| 带版本的二进制、校验和与源码归档 | [GitHub Releases](https://github.com/pgsty/minio/releases) |
+| 缺陷报告与功能讨论 | [GitHub Issues](https://github.com/pgsty/minio/issues) |
+| 私密漏洞报告 | [`SECURITY.md`](SECURITY.md) 与 [`VULNERABILITY_REPORT.md`](VULNERABILITY_REPORT.md) |
+| 许可证、署名与商标信息 | [许可证](https://silo.pgsty.com/zh/about/license/)、[署名归属](https://silo.pgsty.com/zh/about/attribution/)与[商标政策](https://silo.pgsty.com/zh/about/trademark/) |
+
## 维护政策
活跃版本线的维护范围包括：
@@ -61,20 +77,21 @@ Silo 尽量保留：
- MinIO 兼容的 S3 API、配置、环境变量与命令行约定；
- `RELEASE.YYYY-MM-DDTHH-MM-SSZ` 标签、容器入口与常见部署方式。
-兼容是目标，而非保证。安全修复可能改变行为。每个版本都应视为下游升级：锁定版本，阅读[版本说明](https://github.com/pgsty/minio/releases)与[安全公告](docs/security/advisories.md)，保留回滚路径，并在生产使用前完成测试。
+兼容性是默认约束。只要不会留下安全问题，Silo 就保留既有的协议、客户端、配置与运维行为；只有在修复重大安全问题确有必要时才会打破兼容，并在版本说明中明确受影响行为与迁移方式。每个版本仍应视为下游升级：锁定版本，阅读[版本说明](https://silo.pgsty.com/zh/blog/release/)与[安全公告](docs/security/advisories.md)，保留回滚路径，并在生产使用前完成测试。
-## 发行产物
+## 下载与发行产物
+
+请先在[下载与安装](https://silo.pgsty.com/zh/download/)页面选择合适的安装方式；GitHub Releases 仍是带版本服务端二进制、校验和与源码归档的获取位置。
| 产物 | 位置 |
| :-- | :-- |
| 源码 | [`github.com/pgsty/minio`](https://github.com/pgsty/minio) |
| 容器镜像 | [`pgsty/minio`](https://hub.docker.com/r/pgsty/minio)，支持 `linux/amd64` 与 `linux/arm64` 多架构清单 |
-| 服务端二进制 | [GitHub Releases](https://github.com/pgsty/minio/releases)，覆盖 Linux、macOS、Windows 的 `amd64` 与 `arm64` |
+| 服务端二进制与校验和 | [GitHub Releases](https://github.com/pgsty/minio/releases)，覆盖 Linux、macOS、Windows 的 `amd64` 与 `arm64` |
| Linux 软件包 | RPM、DEB、APK，并通过 [Pigsty 软件仓库](https://pigsty.cc/docs/repo/) 分发 |
| 客户端 | [`pgsty/mc`](https://github.com/pgsty/mc)，容器内以 `mcli` 提供，并保留 `mc` 兼容别名 |
| 管理控制台 | 社区维护的 [`georgmangold/console`](https://github.com/georgmangold/console)，嵌入服务端构建 |
-| 文档 | [中文](https://silo.pigsty.cc)、[英文](https://silo.pigsty.io)与 [`pgsty/minio-docs`](https://github.com/pgsty/minio-docs) |
-| 安全记录 | [`SECURITY.md`](SECURITY.md)、[`VULNERABILITY_REPORT.md`](VULNERABILITY_REPORT.md) 与[本分支安全公告](docs/security/advisories.md) |
+| 共享库 | [`pgsty/silo-pkg`](https://github.com/pgsty/silo-pkg) v3.7.0，通过 `replace` 指令使用，同时保留 `github.com/minio/pkg/v3` 导入路径（[版本说明](https://silo.pgsty.com/zh/blog/release/pkg-3.7.0/)） |
## 快速开始
@@ -116,11 +133,11 @@ go build -o minio .
./minio --version
```
-部署：[Silo 中文文档](https://silo.pigsty.cc) · [Pigsty MinIO 模块](https://pigsty.cc/docs/minio/)
+其他安装方式（包括原生软件包、二进制、Podman、Kubernetes、源码构建与 Pigsty Ansible）请前往[下载与安装](https://silo.pgsty.com/zh/download/)；生产部署与管理请从 [Silo 中文文档](https://silo.pgsty.com/zh/docs/)开始。Pigsty 用户也可以直接使用 [Pigsty MinIO 模块](https://pigsty.cc/docs/minio/)。
## 安全
-安全修复面向活跃的 `master` 分支，并记录在[安全公告](docs/security/advisories.md)中。请按照 [`SECURITY.md`](SECURITY.md) 与 [`VULNERABILITY_REPORT.md`](VULNERABILITY_REPORT.md) 私密报告漏洞；同时影响上游 MinIO 的问题也应向上游报告。
+安全修复面向活跃的 `master` 分支，并记录在仓库[安全公告](docs/security/advisories.md)与门户[安全通告](https://silo.pgsty.com/zh/blog/security/)中。请按照 [`SECURITY.md`](SECURITY.md) 与 [`VULNERABILITY_REPORT.md`](VULNERABILITY_REPORT.md) 私密报告漏洞；同时影响上游 MinIO 的问题也应向上游报告。
## 参与贡献
@@ -134,10 +151,10 @@ Issue 与 Pull Request 应说明受影响版本、复现步骤、影响、预期
| 文章 | 主题 |
| :-- | :-- |
-| [MinIO已死](https://vonng.com/db/minio-is-dead/) | 上游项目与发行模式的变化 |
-| [MinIO已死，谁能接盘？](https://vonng.com/db/minio-alternative/) | 可选替代方案评估 |
-| [MinIO 已死，MinIO 复生](https://vonng.com/db/minio-resurrect/) | 建立分支及其发行流水线 |
-| [续命 MinIO：承诺兑现](https://vonng.com/db/minio-promise-kept/) | 初期安全与维护工作 |
+| [MinIO已死](https://silo.pgsty.com/zh/blog/post/minio-is-dead/) | 上游项目与发行模式的变化 |
+| [MinIO已死，谁能接盘？](https://silo.pgsty.com/zh/blog/post/minio-alternative/) | 可选替代方案评估 |
+| [MinIO 已死，MinIO 复生](https://silo.pgsty.com/zh/blog/post/minio-resurrect/) | 建立分支及其发行流水线 |
+| [续命 MinIO：承诺兑现](https://silo.pgsty.com/zh/blog/post/minio-promise-kept/) | 初期安全与维护工作 |
## 许可证与商标
diff --git a/cmd/format-erasure.go b/cmd/format-erasure.go
index 370a86a52..09031d4ed 100644
--- a/cmd/format-erasure.go
+++ b/cmd/format-erasure.go
@@ -177,7 +177,7 @@ func formatGetBackendErasureVersion(b []byte) (string, error) {
return "", fmt.Errorf(`format.Version expected: %s, got: %s`, formatMetaVersionV1, meta.Version)
}
if meta.Format != formatBackendErasure && meta.Format != formatBackendErasureSingle {
- return "", fmt.Errorf(`found backend type %s, expected %s or %s - to migrate to a supported backend visit https://silo.pigsty.io/operations/deployments/baremetal-migrate-fs-gateway.html`, meta.Format, formatBackendErasure, formatBackendErasureSingle)
+ return "", fmt.Errorf(`found backend type %s, expected %s or %s - to migrate to a supported backend visit https://silo.pgsty.com/operations/deployments/baremetal-migrate-fs-gateway/`, meta.Format, formatBackendErasure, formatBackendErasureSingle)
}
// Erasure backend found, proceed to detect version.
format := &formatErasureVersionDetect{}
diff --git a/cmd/server-startup-msg.go b/cmd/server-startup-msg.go
index 254a8d517..1d3a6579b 100644
--- a/cmd/server-startup-msg.go
+++ b/cmd/server-startup-msg.go
@@ -144,7 +144,7 @@ func printServerCommonMsg(apiEndpoints []string) {
// Prints startup message for Object API access, prints link to our SDK documentation.
func printObjectAPIMsg() {
- logger.Startup(color.Blue("\nDocs: ") + "https://silo.pigsty.io")
+ logger.Startup(color.Blue("\nDocs: ") + "https://silo.pgsty.com/docs/")
}
func printLambdaTargets() {
@@ -184,7 +184,7 @@ func printCLIAccessMsg(endPoint string, alias string) {
// Get saved credentials.
cred := globalActiveCred
- const mcQuickStartGuide = "https://silo.pigsty.io/reference/minio-mc.html#quickstart"
+ const mcQuickStartGuide = "https://silo.pgsty.com/reference/minio-mc/#quickstart"
// Configure 'mc', following block prints platform specific information for minio client.
if color.IsTerminal() && (!globalServerCtxt.Anonymous && globalAPIConfig.permitRootAccess()) {
diff --git a/cmd/update.go b/cmd/update.go
index 69847d719..26f93f370 100644
--- a/cmd/update.go
+++ b/cmd/update.go
@@ -450,10 +450,10 @@ func getLatestReleaseTime(u *url.URL, timeout time.Duration, mode string) (sha25
const (
// Kubernetes deployment doc link.
- kubernetesDeploymentDoc = "https://silo.pigsty.io/operations/deployments/kubernetes.html"
+ kubernetesDeploymentDoc = "https://silo.pgsty.com/operations/deployments/kubernetes/"
// Mesos deployment doc link.
- mesosDeploymentDoc = "https://silo.pigsty.io/operations/deployments/kubernetes.html"
+ mesosDeploymentDoc = "https://silo.pgsty.com/operations/deployments/kubernetes/"
)
func getDownloadURL(releaseTag string) (downloadURL string) {
diff --git a/docs/bigdata/README.md b/docs/bigdata/README.md
index 767e3dc68..dcb26ce61 100644
--- a/docs/bigdata/README.md
+++ b/docs/bigdata/README.md
@@ -16,7 +16,7 @@ MinIO also supports multi-cluster, multi-site federation similar to AWS regions
- [Setup Ambari](https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.1.0/bk_ambari-installation/content/set_up_the_ambari_server.html) which automatically sets up YARN
- [Installing Spark](https://docs.hortonworks.com/HDPDocuments/HDP3/HDP-3.0.1/installing-spark/content/installing_spark.html)
- Install MinIO Distributed Server using one of the guides below.
- - [Deployment based on Kubernetes](https://silo.pigsty.io/operations/deployments/kubernetes.html)
+ - [Deployment based on Kubernetes](https://silo.pgsty.com/operations/deployments/kubernetes/)
- [Deployment based on MinIO Helm Chart](https://github.com/helm/charts/tree/master/stable/minio)
## **3. Configure Hadoop, Spark, Hive to use MinIO**
diff --git a/docs/bucket/lifecycle/DESIGN.md b/docs/bucket/lifecycle/DESIGN.md
index 111066cca..78a95a1b9 100644
--- a/docs/bucket/lifecycle/DESIGN.md
+++ b/docs/bucket/lifecycle/DESIGN.md
@@ -51,5 +51,5 @@ Tiering and lifecycle transition are applicable only to erasure/distributed MinI
## Explore Further
-- [MinIO | Golang Client API Reference](https://silo.pigsty.io/developers/go/API.html#SetBucketLifecycle)
+- [MinIO | Golang Client API Reference](https://pkg.go.dev/github.com/minio/minio-go/v7#Client.SetBucketLifecycle)
- [Object Lifecycle Management](https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html)
diff --git a/docs/bucket/lifecycle/README.md b/docs/bucket/lifecycle/README.md
index af8610bee..db649e7ed 100644
--- a/docs/bucket/lifecycle/README.md
+++ b/docs/bucket/lifecycle/README.md
@@ -4,8 +4,8 @@ Enable object lifecycle configuration on buckets to setup automatic deletion of
## 1. Prerequisites
-- Install MinIO - [MinIO Quickstart Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html).
-- Install `mc` - [mc Quickstart Guide](https://silo.pigsty.io/reference/minio-mc.html#quickstart)
+- Install MinIO - [MinIO Quickstart Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/).
+- Install `mc` - [mc Quickstart Guide](https://silo.pgsty.com/reference/minio-mc/#quickstart)
## 2. Enable bucket lifecycle configuration
@@ -59,7 +59,7 @@ TempUploads | temp/ | ✓ | ✓ | 7 day(s) | ✗
## 3. Activate ILM versioning features
-This will only work with a versioned bucket, take a look at [Bucket Versioning Guide](https://silo.pigsty.io/administration/object-management/object-versioning.html) for more understanding.
+This will only work with a versioned bucket, take a look at [Bucket Versioning Guide](https://silo.pgsty.com/administration/object-management/object-versioning/) for more understanding.
### 3.1 Automatic removal of non current objects versions
@@ -228,5 +228,5 @@ Note that transition event notification is a MinIO extension.
## Explore Further
-- [MinIO | Golang Client API Reference](https://silo.pigsty.io/developers/go/API.html)
+- [MinIO | Golang Client API Reference](https://pkg.go.dev/github.com/minio/minio-go/v7)
- [Object Lifecycle Management](https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html)
diff --git a/docs/bucket/notifications/README.md b/docs/bucket/notifications/README.md
index cb50fab84..83c605c96 100644
--- a/docs/bucket/notifications/README.md
+++ b/docs/bucket/notifications/README.md
@@ -30,7 +30,7 @@ Various event types supported by MinIO server are
| `s3:BucketCreated` |
| `s3:BucketRemoved` |
-Use client tools like `mc` to set and listen for event notifications using the [`event` sub-command](https://silo.pigsty.io/reference/minio-mc/mc-event-add.html). MinIO SDK's [`BucketNotification` APIs](https://silo.pigsty.io/developers/go/API.html#setbucketnotification-ctx-context-context-bucketname-string-config-notification-configuration-error) can also be used. The notification message MinIO sends to publish an event is a JSON message with the following [structure](https://docs.aws.amazon.com/AmazonS3/latest/dev/notification-content-structure.html).
+Use client tools like `mc` to set and listen for event notifications using the [`event` sub-command](https://silo.pgsty.com/reference/minio-mc/mc-event-add/). MinIO SDK's [`BucketNotification` APIs](https://pkg.go.dev/github.com/minio/minio-go/v7#Client.SetBucketNotification) can also be used. The notification message MinIO sends to publish an event is a JSON message with the following [structure](https://docs.aws.amazon.com/AmazonS3/latest/dev/notification-content-structure.html).
Bucket events can be published to the following targets:
@@ -43,8 +43,8 @@ Bucket events can be published to the following targets:
## Prerequisites
-- Install and configure MinIO Server from [here](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html#procedure).
-- Install and configure MinIO Client from [here](https://silo.pigsty.io/reference/minio-mc.html#quickstart).
+- Install and configure MinIO Server from [here](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/#procedure).
+- Install and configure MinIO Client from [here](https://silo.pgsty.com/reference/minio-mc/#quickstart).
```
$ mc admin config get myminio | grep notify
diff --git a/docs/bucket/quota/README.md b/docs/bucket/quota/README.md
index 69c0f5c6b..f05a679cb 100644
--- a/docs/bucket/quota/README.md
+++ b/docs/bucket/quota/README.md
@@ -6,8 +6,8 @@ Buckets can be configured to have `Hard` quota - it disallows writes to the buck
## Prerequisites
-- Install MinIO - [MinIO Quickstart Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html#procedure).
-- [Use `mc` with MinIO Server](https://silo.pigsty.io/reference/minio-mc.html#quickstart)
+- Install MinIO - [MinIO Quickstart Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/#procedure).
+- [Use `mc` with MinIO Server](https://silo.pgsty.com/reference/minio-mc/#quickstart)
## Set bucket quota configuration
diff --git a/docs/bucket/replication/DESIGN.md b/docs/bucket/replication/DESIGN.md
index b3522ee94..94b5b4929 100644
--- a/docs/bucket/replication/DESIGN.md
+++ b/docs/bucket/replication/DESIGN.md
@@ -156,5 +156,5 @@ If 3 or more targets are participating in active-active replication, the replica
## Explore Further
-- [MinIO Bucket Versioning Implementation](https://silo.pigsty.io/administration/object-management/object-versioning.html)
-- [MinIO Client Quickstart Guide](https://silo.pigsty.io/reference/minio-mc.html#quickstart)
+- [MinIO Bucket Versioning Implementation](https://silo.pgsty.com/administration/object-management/object-versioning/)
+- [MinIO Client Quickstart Guide](https://silo.pgsty.com/reference/minio-mc/#quickstart)
diff --git a/docs/bucket/replication/README.md b/docs/bucket/replication/README.md
index 8551e05d4..76f599387 100644
--- a/docs/bucket/replication/README.md
+++ b/docs/bucket/replication/README.md
@@ -2,9 +2,9 @@
Bucket replication is designed to replicate selected objects in a bucket to a destination bucket.
-The contents of this page have been migrated to the new [MinIO Documentation: Bucket Replication](https://silo.pigsty.io/administration/bucket-replication.html) page. The [Bucket Replication](https://silo.pigsty.io/administration/bucket-replication/bucket-replication-requirements.html) page references dedicated tutorials for configuring one-way "Active-Passive" and two-way "Active-Active" bucket replication.
+The contents of this page have been migrated to the new [MinIO Documentation: Bucket Replication](https://silo.pgsty.com/administration/bucket-replication/) page. The [Bucket Replication](https://silo.pgsty.com/administration/bucket-replication/bucket-replication-requirements/) page references dedicated tutorials for configuring one-way "Active-Passive" and two-way "Active-Active" bucket replication.
-To replicate objects in a bucket to a destination bucket on a target site either in the same cluster or a different cluster, start by enabling [versioning](https://silo.pigsty.io/administration/object-management/object-versioning.html) for both source and destination buckets. Finally, the target site and the destination bucket need to be configured on the source MinIO server.
+To replicate objects in a bucket to a destination bucket on a target site either in the same cluster or a different cluster, start by enabling [versioning](https://silo.pgsty.com/administration/object-management/object-versioning/) for both source and destination buckets. Finally, the target site and the destination bucket need to be configured on the source MinIO server.
## Highlights
@@ -155,7 +155,7 @@ The replication configuration generated has the following format and can be expo
The replication configuration follows [AWS S3 Spec](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication-add-config.html). Any objects uploaded to the source bucket that meet replication criteria will now be automatically replicated by the MinIO server to the remote destination bucket. Replication can be disabled at any time by disabling specific rules in the configuration or deleting the replication configuration entirely.
-When object locking is used in conjunction with replication, both source and destination buckets needs to have [object locking](https://silo.pigsty.io/administration/object-management/object-retention.html) enabled. Similarly objects encrypted on the server side, will be replicated if destination also supports encryption.
+When object locking is used in conjunction with replication, both source and destination buckets needs to have [object locking](https://silo.pgsty.com/administration/object-management/object-retention/) enabled. Similarly objects encrypted on the server side, will be replicated if destination also supports encryption.
Replication status can be seen in the metadata on the source and destination objects. On the source side, the `X-Amz-Replication-Status` changes from `PENDING` to `COMPLETED` or `FAILED` after replication attempt either succeeded or failed respectively. On the destination side, a `X-Amz-Replication-Status` status of `REPLICA` indicates that the object was replicated successfully. Any replication failures are automatically re-attempted during a periodic disk scanner cycle.
@@ -277,5 +277,5 @@ MinIO does not support SSE-C encrypted objects on replicated buckets, any applic
## Explore Further
- [MinIO Bucket Replication Design](https://github.com/pgsty/minio/blob/master/docs/bucket/replication/DESIGN.md)
-- [MinIO Bucket Versioning Implementation](https://silo.pigsty.io/administration/object-management/object-retention.html)
-- [MinIO Client Quickstart Guide](https://silo.pigsty.io/reference/minio-mc.html#quickstart)
+- [MinIO Bucket Versioning Implementation](https://silo.pgsty.com/administration/object-management/object-retention/)
+- [MinIO Client Quickstart Guide](https://silo.pgsty.com/reference/minio-mc/#quickstart)
diff --git a/docs/bucket/retention/README.md b/docs/bucket/retention/README.md
index de2668e7e..0bc556afe 100644
--- a/docs/bucket/retention/README.md
+++ b/docs/bucket/retention/README.md
@@ -10,7 +10,7 @@ A default retention period and retention mode can be configured on a bucket to b
### 1. Prerequisites
-- Install MinIO - [MinIO Quickstart Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html)
+- Install MinIO - [MinIO Quickstart Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/)
- Install `awscli` - [Installing AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html)
### 2. Set bucket WORM configuration
@@ -53,7 +53,7 @@ See
## Explore Further
-- [Use `mc` with MinIO Server](https://silo.pigsty.io/reference/minio-mc.html#quickstart)
-- [Use `aws-cli` with MinIO Server](https://silo.pigsty.io/integrations/aws-cli-with-minio.html)
-- [Use `minio-go` SDK with MinIO Server](https://silo.pigsty.io/developers/go/minio-go.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [Use `mc` with MinIO Server](https://silo.pgsty.com/reference/minio-mc/#quickstart)
+- [Use `aws-cli` with MinIO Server](https://silo.pgsty.com/integrations/aws-cli-with-minio/)
+- [Use `minio-go` SDK with MinIO Server](https://silo.pgsty.com/developers/go/minio-go/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/bucket/versioning/README.md b/docs/bucket/versioning/README.md
index c14c6c9b4..01866a2a4 100644
--- a/docs/bucket/versioning/README.md
+++ b/docs/bucket/versioning/README.md
@@ -211,7 +211,7 @@ public class IsVersioningEnabled {
## Explore Further
-- [Use `minio-java` SDK with MinIO Server](https://silo.pigsty.io/developers/java/minio-java.html)
-- [Object Lock and Immutability Guide](https://silo.pigsty.io/administration/object-management/object-retention.html)
-- [MinIO Admin Complete Guide](https://silo.pigsty.io/reference/minio-mc-admin.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [Use `minio-java` SDK with MinIO Server](https://silo.pgsty.com/developers/java/minio-java/)
+- [Object Lock and Immutability Guide](https://silo.pgsty.com/administration/object-management/object-retention/)
+- [MinIO Admin Complete Guide](https://silo.pgsty.com/reference/minio-mc-admin/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/chroot/README.md b/docs/chroot/README.md
index d0887441a..ab9de68aa 100644
--- a/docs/chroot/README.md
+++ b/docs/chroot/README.md
@@ -51,8 +51,8 @@ Instance is now accessible on the host at port 9000, proceed to access the Web b
## Explore Further
-- [MinIO Erasure Code Overview](https://silo.pigsty.io/operations/concepts/erasure-coding.html)
-- [Use `mc` with MinIO Server](https://silo.pigsty.io/reference/minio-mc.html)
-- [Use `aws-cli` with MinIO Server](https://silo.pigsty.io/integrations/aws-cli-with-minio.html)
-- [Use `minio-go` SDK with MinIO Server](https://silo.pigsty.io/developers/go/minio-go.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [MinIO Erasure Code Overview](https://silo.pgsty.com/operations/concepts/erasure-coding/)
+- [Use `mc` with MinIO Server](https://silo.pgsty.com/reference/minio-mc/)
+- [Use `aws-cli` with MinIO Server](https://silo.pgsty.com/integrations/aws-cli-with-minio/)
+- [Use `minio-go` SDK with MinIO Server](https://silo.pgsty.com/developers/go/minio-go/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/compression/README.md b/docs/compression/README.md
index 99a054469..dce167c32 100644
--- a/docs/compression/README.md
+++ b/docs/compression/README.md
@@ -19,7 +19,7 @@ will increase speed when the content can be compressed.
### 1. Prerequisites
-Install MinIO - [MinIO Quickstart Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html).
+Install MinIO - [MinIO Quickstart Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/).
### 2. Run MinIO with compression
@@ -131,7 +131,7 @@ the data directory to view the size of the object.
## Explore Further
-- [Use `mc` with MinIO Server](https://silo.pigsty.io/reference/minio-mc.html)
-- [Use `aws-cli` with MinIO Server](https://silo.pigsty.io/integrations/aws-cli-with-minio.html)
-- [Use `minio-go` SDK with MinIO Server](https://silo.pigsty.io/developers/go/minio-go.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [Use `mc` with MinIO Server](https://silo.pgsty.com/reference/minio-mc/)
+- [Use `aws-cli` with MinIO Server](https://silo.pgsty.com/integrations/aws-cli-with-minio/)
+- [Use `minio-go` SDK with MinIO Server](https://silo.pgsty.com/developers/go/minio-go/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/config/README.md b/docs/config/README.md
index b0be45854..703a26347 100644
--- a/docs/config/README.md
+++ b/docs/config/README.md
@@ -6,7 +6,7 @@ MinIO stores all its config as part of the server deployment, config is erasure
### Certificate Directory
-TLS certificates by default are expected to be stored under ``${HOME}/.minio/certs`` directory. You need to place certificates here to enable `HTTPS` based access. Read more about [How to secure access to MinIO server with TLS](https://silo.pigsty.io/operations/network-encryption.html).
+TLS certificates by default are expected to be stored under ``${HOME}/.minio/certs`` directory. You need to place certificates here to enable `HTTPS` based access. Read more about [How to secure access to MinIO server with TLS](https://silo.pgsty.com/operations/network-encryption/).
Following is a sample directory structure for MinIO server with TLS certificates.
@@ -172,7 +172,7 @@ MINIO_API_OBJECT_MAX_VERSIONS (number) set max allowed number of
#### Notifications
-Notification targets supported by MinIO are in the following list. To configure individual targets please refer to more detailed documentation [here](https://silo.pigsty.io/administration/monitoring.html#bucket-notifications).
+Notification targets supported by MinIO are in the following list. To configure individual targets please refer to more detailed documentation [here](https://silo.pgsty.com/administration/monitoring/#bucket-notifications).
```
notify_webhook publish bucket notifications to webhook endpoints
@@ -336,5 +336,5 @@ minio server /data
## Explore Further
-* [MinIO Quickstart Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html)
-* [Configure MinIO Server with TLS](https://silo.pigsty.io/operations/network-encryption.html)
+* [MinIO Quickstart Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/)
+* [Configure MinIO Server with TLS](https://silo.pgsty.com/operations/network-encryption/)
diff --git a/docs/debugging/README.md b/docs/debugging/README.md
index be3015da4..14b3ed244 100644
--- a/docs/debugging/README.md
+++ b/docs/debugging/README.md
@@ -2,7 +2,7 @@
## HTTP Trace
-HTTP tracing can be enabled by using [`mc admin trace`](https://silo.pigsty.io/reference/minio-mc-admin/mc-admin-trace.html) command.
+HTTP tracing can be enabled by using [`mc admin trace`](https://silo.pgsty.com/reference/minio-mc-admin/mc-admin-trace/) command.
Example:
diff --git a/docs/distributed/README.md b/docs/distributed/README.md
index dc7ae19c9..6ee9385ee 100644
--- a/docs/distributed/README.md
+++ b/docs/distributed/README.md
@@ -8,7 +8,7 @@ MinIO in distributed mode can help you setup a highly-available storage system w
### Data protection
-Distributed MinIO provides protection against multiple node/drive failures and [bit rot](https://github.com/pgsty/minio/blob/master/docs/erasure/README.md#what-is-bit-rot-protection) using [erasure code](https://silo.pigsty.io/operations/concepts/erasure-coding.html). As the minimum drives required for distributed MinIO is 2 (same as minimum drives required for erasure coding), erasure code automatically kicks in as you launch distributed MinIO.
+Distributed MinIO provides protection against multiple node/drive failures and [bit rot](https://github.com/pgsty/minio/blob/master/docs/erasure/README.md#what-is-bit-rot-protection) using [erasure code](https://silo.pgsty.com/operations/concepts/erasure-coding/). As the minimum drives required for distributed MinIO is 2 (same as minimum drives required for erasure coding), erasure code automatically kicks in as you launch distributed MinIO.
If one or more drives are offline at the start of a PutObject or NewMultipartUpload operation the object will have additional data protection bits added automatically to provide additional safety for these objects.
@@ -38,11 +38,11 @@ Install MinIO either on Kubernetes or Distributed Linux.
Install MinIO on Kubernetes:
-- [MinIO Quickstart Guide for Kubernetes](https://silo.pigsty.io/operations/deployments/kubernetes.html).
-- [Deploy a Tenant from the MinIO Operator](https://silo.pigsty.io/operations/deployments/k8s-deploy-minio-tenant-on-kubernetes.html)
+- [MinIO Quickstart Guide for Kubernetes](https://silo.pgsty.com/operations/deployments/kubernetes/).
+- [Deploy a Tenant from the MinIO Operator](https://silo.pgsty.com/operations/deployments/k8s-deploy-minio-tenant-on-kubernetes/)
Install Distributed MinIO on Linux:
-- [Deploy Distributed MinIO on Linux](https://silo.pigsty.io/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html#deploy-distributed-minio)
+- [Deploy Distributed MinIO on Linux](https://silo.pgsty.com/operations/deployments/baremetal/#deploy-minio-distributed-baremetal)
### 2. Run distributed MinIO
@@ -98,12 +98,12 @@ Now the server has expanded total storage by _(newly_added_servers\*m)_ more dri
## 3. Test your setup
-To test this setup, access the MinIO server via browser or [`mc`](https://silo.pigsty.io/reference/minio-mc.html#quickstart).
+To test this setup, access the MinIO server via browser or [`mc`](https://silo.pgsty.com/reference/minio-mc/#quickstart).
## Explore Further
-- [MinIO Erasure Code QuickStart Guide](https://silo.pigsty.io/operations/concepts/erasure-coding.html)
-- [Use `mc` with MinIO Server](https://silo.pigsty.io/reference/minio-mc.html)
-- [Use `aws-cli` with MinIO Server](https://silo.pigsty.io/integrations/aws-cli-with-minio.html)
-- [Use `minio-go` SDK with MinIO Server](https://silo.pigsty.io/developers/go/minio-go.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [MinIO Erasure Code QuickStart Guide](https://silo.pgsty.com/operations/concepts/erasure-coding/)
+- [Use `mc` with MinIO Server](https://silo.pgsty.com/reference/minio-mc/)
+- [Use `aws-cli` with MinIO Server](https://silo.pgsty.com/integrations/aws-cli-with-minio/)
+- [Use `minio-go` SDK with MinIO Server](https://silo.pgsty.com/developers/go/minio-go/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/docker/README.md b/docs/docker/README.md
index c5fed87f4..cf4eeb031 100644
--- a/docs/docker/README.md
+++ b/docs/docker/README.md
@@ -10,7 +10,7 @@ Docker installed on your machine. Download the relevant installer from [here](ht
## Run Standalone MinIO on Docker
-*Note*: Standalone MinIO is intended for early development and evaluation. For production clusters, deploy a [Distributed](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-as-a-container.html) MinIO deployment.
+*Note*: Standalone MinIO is intended for early development and evaluation. For production clusters, deploy a [Distributed](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-as-a-container/) MinIO deployment.
MinIO needs a persistent volume to store configuration and application data. For testing purposes, you can launch MinIO by simply passing a directory (`/data` in the example below). This directory gets created in the container filesystem at the time of container start. But all the data is lost after container exits.
@@ -59,7 +59,7 @@ docker run \
We recommend kubernetes based deployment for production level deployment .
-See the [Kubernetes documentation](https://silo.pigsty.io/operations/deployments/kubernetes.html) for more information.
+See the [Kubernetes documentation](https://silo.pgsty.com/operations/deployments/kubernetes/) for more information.
## MinIO Docker Tips
@@ -213,5 +213,5 @@ docker stats
## Explore Further
-* [MinIO in a Container Installation Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-as-a-container.html)
-* [MinIO Erasure Code QuickStart Guide](https://silo.pigsty.io/operations/concepts/erasure-coding.html)
+* [MinIO in a Container Installation Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-as-a-container/)
+* [MinIO Erasure Code QuickStart Guide](https://silo.pgsty.com/operations/concepts/erasure-coding/)
diff --git a/docs/erasure/README.md b/docs/erasure/README.md
index 4a78a49d6..caa952b3e 100644
--- a/docs/erasure/README.md
+++ b/docs/erasure/README.md
@@ -26,7 +26,7 @@ MinIO's erasure coded backend uses high speed [HighwayHash](https://github.com/m
MinIO divides the drives you provide into erasure-coding sets of *2 to 16* drives. Therefore, the number of drives you present must be a multiple of one of these numbers. Each object is written to a single erasure-coding set.
-Minio uses the largest possible EC set size which divides into the number of drives given. For example, *18 drives* are configured as *2 sets of 9 drives*, and *24 drives* are configured as *2 sets of 12 drives*. This is true for scenarios when running MinIO as a standalone erasure coded deployment. In [distributed setup however node (affinity) based](https://silo.pigsty.io/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html) erasure stripe sizes are chosen.
+Minio uses the largest possible EC set size which divides into the number of drives given. For example, *18 drives* are configured as *2 sets of 9 drives*, and *24 drives* are configured as *2 sets of 12 drives*. This is true for scenarios when running MinIO as a standalone erasure coded deployment. In [distributed setup however node (affinity) based](https://silo.pgsty.com/operations/deployments/baremetal/) erasure stripe sizes are chosen.
The drives should all be of approximately the same size.
@@ -34,7 +34,7 @@ The drives should all be of approximately the same size.
### 1. Prerequisites
-Install MinIO - [MinIO Quickstart Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html)
+Install MinIO - [MinIO Quickstart Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/)
### 2. Run MinIO Server with Erasure Code
diff --git a/docs/erasure/storage-class/README.md b/docs/erasure/storage-class/README.md
index 3d523cb5b..641789caa 100644
--- a/docs/erasure/storage-class/README.md
+++ b/docs/erasure/storage-class/README.md
@@ -2,7 +2,7 @@
MinIO server supports storage class in erasure coding mode. This allows configurable data and parity drives per object.
-This page is intended as a summary of MinIO Erasure Coding. For a more complete explanation, see .
+This page is intended as a summary of MinIO Erasure Coding. For a more complete explanation, see .
## Overview
@@ -53,7 +53,7 @@ The default value for the `STANDARD` storage class depends on the number of volu
| 6-7 | EC:3 |
| 8 or more | EC:4 |
-For more complete documentation on Erasure Set sizing, see the [MinIO Documentation on Erasure Sets](https://silo.pigsty.io/operations/concepts/erasure-coding.html#erasure-sets).
+For more complete documentation on Erasure Set sizing, see the [MinIO Documentation on Erasure Sets](https://silo.pgsty.com/operations/concepts/erasure-coding/#minio-ec-erasure-set).
### Allowed values for REDUCED_REDUNDANCY storage class
diff --git a/docs/federation/lookup/README.md b/docs/federation/lookup/README.md
index 364628b47..c0277d8ca 100644
--- a/docs/federation/lookup/README.md
+++ b/docs/federation/lookup/README.md
@@ -6,7 +6,7 @@ This document explains how to configure MinIO with `Bucket lookup from DNS` styl
### 1. Prerequisites
-Install MinIO - [MinIO Quickstart Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html).
+Install MinIO - [MinIO Quickstart Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/).
### 2. Run MinIO in federated mode
@@ -76,11 +76,11 @@ it is randomized which cluster might provision the bucket.
### 3. Test your setup
-To test this setup, access the MinIO server via browser or [`mc`](https://silo.pigsty.io/reference/minio-mc.html#quickstart). You’ll see the uploaded files are accessible from the all the MinIO endpoints.
+To test this setup, access the MinIO server via browser or [`mc`](https://silo.pgsty.com/reference/minio-mc/#quickstart). You’ll see the uploaded files are accessible from the all the MinIO endpoints.
## Explore Further
-- [Use `mc` with MinIO Server](https://silo.pigsty.io/reference/minio-mc.html)
-- [Use `aws-cli` with MinIO Server](https://silo.pigsty.io/integrations/aws-cli-with-minio.html)
-- [Use `minio-go` SDK with MinIO Server](https://silo.pigsty.io/developers/go/minio-go.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [Use `mc` with MinIO Server](https://silo.pgsty.com/reference/minio-mc/)
+- [Use `aws-cli` with MinIO Server](https://silo.pgsty.com/integrations/aws-cli-with-minio/)
+- [Use `minio-go` SDK with MinIO Server](https://silo.pgsty.com/developers/go/minio-go/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/integrations/veeam/README.md b/docs/integrations/veeam/README.md
index a1f21b85e..b81252924 100644
--- a/docs/integrations/veeam/README.md
+++ b/docs/integrations/veeam/README.md
@@ -5,10 +5,10 @@ When using Veeam Backup and Replication, you can use S3 compatible object storag
## Prerequisites
- One or both of Veeam Backup and Replication with support for S3 compatible object store (e.g. 9.5.4) and Veeam Backup for Office365 (VBO)
-- MinIO object storage set up per
-- Veeam requires TLS connections to the object storage. This can be configured per
+- MinIO object storage set up per
+- Veeam requires TLS connections to the object storage. This can be configured per
- The S3 bucket, Access Key and Secret Key have to be created before and outside of Veeam.
-- Configure the minio client for the Veeam MinIO endpoint -
+- Configure the minio client for the Veeam MinIO endpoint -
## Setting up an S3 compatible object store for Veeam Backup and Replication
@@ -26,7 +26,7 @@ mc mb myminio/veeambackup
mc mb -l myminio/veeambackup
```
-> Object locking requires erasure coding enabled on the minio server. For more information see .
+> Object locking requires erasure coding enabled on the minio server. For more information see .
### Add MinIO as an object store for Veeam
diff --git a/docs/kms/README.md b/docs/kms/README.md
index 2bb532854..ca744db96 100644
--- a/docs/kms/README.md
+++ b/docs/kms/README.md
@@ -4,7 +4,7 @@ MinIO uses a key-management-system (KMS) to support SSE-S3. If a client requests
## Quick Start
-MinIO supports multiple KMS implementations via our [KES](https://github.com/minio/kes#kes) project. We run a KES instance at `https://play.min.io:7373` for you to experiment and quickly get started. To run MinIO with a KMS just fetch the root identity, set the following environment variables and then start your MinIO server. If you haven't installed MinIO, yet, then follow the MinIO [install instructions](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html) first.
+MinIO supports multiple KMS implementations via our [KES](https://github.com/minio/kes#kes) project. We run a KES instance at `https://play.min.io:7373` for you to experiment and quickly get started. To run MinIO with a KMS just fetch the root identity, set the following environment variables and then start your MinIO server. If you haven't installed MinIO, yet, then follow the MinIO [install instructions](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/) first.
### 1. Fetch the root identity
@@ -67,7 +67,7 @@ The MinIO-KES configuration is always the same - regardless of the underlying KM
### Further references
-- [Run MinIO with TLS / HTTPS](https://silo.pigsty.io/operations/network-encryption.html)
+- [Run MinIO with TLS / HTTPS](https://silo.pgsty.com/operations/network-encryption/)
- [Tweak the KES server configuration](https://github.com/minio/kes/wiki/Configuration)
- [Run a load balancer in front of KES](https://github.com/minio/kes/wiki/TLS-Proxy)
- [Understand the KES server concepts](https://github.com/minio/kes/wiki/Concepts)
@@ -137,7 +137,7 @@ Certificates are no secrets and sent in plaintext as part of the TLS handshake.
## Explore Further
-- [Use `mc` with MinIO Server](https://silo.pigsty.io/reference/minio-mc.html)
-- [Use `aws-cli` with MinIO Server](https://silo.pigsty.io/integrations/aws-cli-with-minio.html)
-- [Use `minio-go` SDK with MinIO Server](https://silo.pigsty.io/developers/go/minio-go.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [Use `mc` with MinIO Server](https://silo.pgsty.com/reference/minio-mc/)
+- [Use `aws-cli` with MinIO Server](https://silo.pgsty.com/integrations/aws-cli-with-minio/)
+- [Use `minio-go` SDK with MinIO Server](https://silo.pgsty.com/developers/go/minio-go/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/lambda/README.md b/docs/lambda/README.md
index c3d3a9ef9..536793048 100644
--- a/docs/lambda/README.md
+++ b/docs/lambda/README.md
@@ -4,7 +4,7 @@ MinIO's Object Lambda implementation allows for transforming your data to serve
MinIO's Object Lambda, enables application developers to process data retrieved from MinIO before returning it to an application. You can register a Lambda Function target on MinIO, once successfully registered it can be used to transform the data for application GET requests on demand.
-This document focuses on showing a working example on how to use Object Lambda with MinIO, you must have [MinIO deployed in your environment](https://silo.pigsty.io/operations/installation.html) before you can start using external lambda functions. You also must install Python version 3.8 or later for the lambda handlers to work.
+This document focuses on showing a working example on how to use Object Lambda with MinIO, you must have [MinIO deployed in your environment](https://silo.pgsty.com/operations/deployments/installation/) before you can start using external lambda functions. You also must install Python version 3.8 or later for the lambda handlers to work.
## Example Lambda handler
@@ -134,7 +134,7 @@ mc cp testobject myminio/functionbucket/
## Invoke Lambda transformation via PresignedGET
-Following example shows how you can use [`minio-go` PresignedGetObject](https://silo.pigsty.io/developers/go/API.html#presignedgetobject-ctx-context-context-bucketname-objectname-string-expiry-time-duration-reqparams-url-values-url-url-error)
+Following example shows how you can use [`minio-go` PresignedGetObject](https://pkg.go.dev/github.com/minio/minio-go/v7#Client.PresignedGetObject)
```go
package main
diff --git a/docs/logging/README.md b/docs/logging/README.md
index f99422507..d0a39eb2d 100644
--- a/docs/logging/README.md
+++ b/docs/logging/README.md
@@ -17,7 +17,7 @@ Console target is on always and cannot be disabled.
HTTP target logs to a generic HTTP endpoint in JSON format and is not enabled by default. To enable HTTP target logging you would have to update your MinIO server configuration using `mc admin config set` command.
-Assuming `mc` is already [configured](https://silo.pigsty.io/reference/minio-mc.html#quickstart)
+Assuming `mc` is already [configured](https://silo.pgsty.com/reference/minio-mc/#quickstart)
```
mc admin config get myminio/ logger_webhook
@@ -42,7 +42,7 @@ minio server /mnt/data
## Audit Targets
-Assuming `mc` is already [configured](https://silo.pigsty.io/reference/minio-mc.html#quickstart)
+Assuming `mc` is already [configured](https://silo.pgsty.com/reference/minio-mc/#quickstart)
### Audit HTTP Target
@@ -224,5 +224,5 @@ NOTE:
## Explore Further
-- [MinIO Quickstart Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html)
-- [Configure MinIO Server with TLS](https://silo.pigsty.io/operations/network-encryption.html)
+- [MinIO Quickstart Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/)
+- [Configure MinIO Server with TLS](https://silo.pgsty.com/operations/network-encryption/)
diff --git a/docs/metrics/prometheus/README.md b/docs/metrics/prometheus/README.md
index bce5db281..83b14dd40 100644
--- a/docs/metrics/prometheus/README.md
+++ b/docs/metrics/prometheus/README.md
@@ -9,7 +9,7 @@ This document explains how to setup Prometheus and configure it to scrape data f
## Prerequisites
-To get started with MinIO, refer [MinIO QuickStart Document](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html).
+To get started with MinIO, refer [MinIO QuickStart Document](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/).
Follow below steps to get started with MinIO monitoring using Prometheus.
### 1. Download Prometheus
@@ -49,7 +49,7 @@ minio server ~/test
> If MinIO is configured to expose metrics without authentication, you don't need to use `mc` to generate prometheus config. You can skip reading further and move to 3.2 section.
-The Prometheus endpoint in MinIO requires authentication by default. Prometheus supports a bearer token approach to authenticate prometheus scrape requests, override the default Prometheus config with the one generated using mc. To generate a Prometheus config for an alias, use [mc](https://silo.pigsty.io/reference/minio-mc.html#quickstart) as follows `mc admin prometheus generate [METRIC-TYPE]`. The valid values for METRIC-TYPE are `cluster`, `node`, `bucket` and `resource` and if not mentioned, it defaults to `cluster`.
+The Prometheus endpoint in MinIO requires authentication by default. Prometheus supports a bearer token approach to authenticate prometheus scrape requests, override the default Prometheus config with the one generated using mc. To generate a Prometheus config for an alias, use [mc](https://silo.pgsty.com/reference/minio-mc/#quickstart) as follows `mc admin prometheus generate [METRIC-TYPE]`. The valid values for METRIC-TYPE are `cluster`, `node`, `bucket` and `resource` and if not mentioned, it defaults to `cluster`.
The command will generate the `scrape_configs` section of the prometheus.yml as follows:
diff --git a/docs/metrics/prometheus/list.md b/docs/metrics/prometheus/list.md
index 0342cd2a0..4693ec710 100644
--- a/docs/metrics/prometheus/list.md
+++ b/docs/metrics/prometheus/list.md
@@ -78,8 +78,8 @@ For deployments behind a load balancer, use the load balancer hostname instead o
## Cluster Replication Metrics
-Metrics marked as ``Site Replication Only`` only populate on deployments with [Site Replication](https://silo.pigsty.io/operations/install-deploy-manage/multi-site-replication.html) configurations.
-For deployments with [bucket](https://silo.pigsty.io/administration/bucket-replication.html) or [batch](https://silo.pigsty.io/administration/batch-framework.html#replicate) configurations, these metrics populate instead under the [Bucket Metrics](#bucket-metrics) endpoint.
+Metrics marked as ``Site Replication Only`` only populate on deployments with [Site Replication](https://silo.pgsty.com/operations/replication/multi-site-replication/) configurations.
+For deployments with [bucket](https://silo.pgsty.com/administration/bucket-replication/) or [batch](https://silo.pgsty.com/administration/batch-framework-job-replicate/#minio-batch-framework-replicate-job) configurations, these metrics populate instead under the [Bucket Metrics](#bucket-metrics) endpoint.
| Name | Description
|:-----------------------------------------------------------|:---------------------------------------------------------------------------------------------------------|
@@ -108,8 +108,8 @@ For deployments with [bucket](https://silo.pigsty.io/administration/bucket-repli
## Node Replication Metrics
-Metrics marked as ``Site Replication Only`` only populate on deployments with [Site Replication](https://silo.pigsty.io/operations/install-deploy-manage/multi-site-replication.html) configurations.
-For deployments with [bucket](https://silo.pigsty.io/administration/bucket-replication.html) or [batch](https://silo.pigsty.io/administration/batch-framework.html#replicate) configurations, these metrics populate instead under the [Bucket Metrics](#bucket-metrics) endpoint.
+Metrics marked as ``Site Replication Only`` only populate on deployments with [Site Replication](https://silo.pgsty.com/operations/replication/multi-site-replication/) configurations.
+For deployments with [bucket](https://silo.pgsty.com/administration/bucket-replication/) or [batch](https://silo.pgsty.com/administration/batch-framework-job-replicate/#minio-batch-framework-replicate-job) configurations, these metrics populate instead under the [Bucket Metrics](#bucket-metrics) endpoint.
| Name | Description
|:-----------------------------------------------------------|:---------------------------------------------------------------------------------------------------------|
@@ -296,8 +296,8 @@ For deployments behind a load balancer, use the load balancer hostname instead o
## Replication Metrics
-These metrics only populate on deployments with [Bucket Replication](https://silo.pigsty.io/administration/bucket-replication.html) or [Batch Replication](https://silo.pigsty.io/administration/batch-framework.html) configurations.
-For deployments with [Site Replication](https://silo.pigsty.io/operations/install-deploy-manage/multi-site-replication.html) configured, select metrics populate under the [Cluster Metrics](#cluster-metrics) endpoint.
+These metrics only populate on deployments with [Bucket Replication](https://silo.pgsty.com/administration/bucket-replication/) or [Batch Replication](https://silo.pgsty.com/administration/batch-framework/) configurations.
+For deployments with [Site Replication](https://silo.pgsty.com/operations/replication/multi-site-replication/) configured, select metrics populate under the [Cluster Metrics](#cluster-metrics) endpoint.
| Name | Description |
|:----------------------------------------------------|:---------------------------------------------------------------------------------|
diff --git a/docs/minio-limits.md b/docs/minio-limits.md
index 125958ae3..a9c72838f 100644
--- a/docs/minio-limits.md
+++ b/docs/minio-limits.md
@@ -42,14 +42,14 @@ We found the following APIs to be redundant or less useful outside of AWS S3. If
### List of Amazon S3 Bucket APIs not supported on MinIO
-- BucketACL (Use [bucket policies](https://silo.pigsty.io/administration/identity-access-management/policy-based-access-control.html) instead)
+- BucketACL (Use [bucket policies](https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/) instead)
- BucketCORS (CORS enabled by default on all buckets for all HTTP verbs, you can optionally restrict the CORS domains)
- BucketWebsite (Use [`caddy`](https://github.com/caddyserver/caddy) or [`nginx`](https://www.nginx.com/resources/wiki/))
-- BucketAnalytics, BucketMetrics, BucketLogging (Use [bucket notification](https://silo.pigsty.io/administration/monitoring/bucket-notifications.html) APIs)
+- BucketAnalytics, BucketMetrics, BucketLogging (Use [bucket notification](https://silo.pgsty.com/administration/monitoring/bucket-notifications/) APIs)
### List of Amazon S3 Object APIs not supported on MinIO
-- ObjectACL (Use [bucket policies](https://silo.pigsty.io/administration/identity-access-management/policy-based-access-control.html) instead)
+- ObjectACL (Use [bucket policies](https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/) instead)
## Object name restrictions on MinIO
diff --git a/docs/multi-tenancy/README.md b/docs/multi-tenancy/README.md
index 62c42b0ff..0c4f5db4a 100644
--- a/docs/multi-tenancy/README.md
+++ b/docs/multi-tenancy/README.md
@@ -64,4 +64,4 @@ minio server --address :9003 http://192.168.10.1{1...4}/data/tenant3
## Cloud Scale Deployment
-A container orchestration platform (e.g. Kubernetes) is recommended for large-scale, multi-tenant MinIO deployments. See the [MinIO Deployment Quickstart Guide](https://silo.pigsty.io/operations/deployments/kubernetes.html) to get started with MinIO on orchestration platforms.
+A container orchestration platform (e.g. Kubernetes) is recommended for large-scale, multi-tenant MinIO deployments. See the [MinIO Deployment Quickstart Guide](https://silo.pgsty.com/operations/deployments/kubernetes/) to get started with MinIO on orchestration platforms.
diff --git a/docs/multi-user/README.md b/docs/multi-user/README.md
index 2e4cf9f99..f5bf52b47 100644
--- a/docs/multi-user/README.md
+++ b/docs/multi-user/README.md
@@ -8,13 +8,13 @@ In this document we will explain in detail on how to configure multiple users.
### 1. Prerequisites
-- Install mc - [MinIO Client Quickstart Guide](https://silo.pigsty.io/reference/minio-mc.html#quickstart)
-- Install MinIO - [MinIO Quickstart Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html)
+- Install mc - [MinIO Client Quickstart Guide](https://silo.pgsty.com/reference/minio-mc/#quickstart)
+- Install MinIO - [MinIO Quickstart Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/)
- Configure etcd - [Etcd V3 Quickstart Guide](https://github.com/pgsty/minio/blob/master/docs/sts/etcd.md)
### 2. Create a new user with canned policy
-Use [`mc admin policy`](https://silo.pigsty.io/reference/minio-mc-admin/mc-admin-policy.html) to create canned policies. Server provides a default set of canned policies namely `writeonly`, `readonly` and `readwrite` *(these policies apply to all resources on the server)*. These can be overridden by custom policies using `mc admin policy` command.
+Use [`mc admin policy`](https://silo.pgsty.com/reference/minio-mc-admin/mc-admin-policy/) to create canned policies. Server provides a default set of canned policies namely `writeonly`, `readonly` and `readwrite` *(these policies apply to all resources on the server)*. These can be overridden by custom policies using `mc admin policy` command.
Create new canned policy file `getonly.json`. This policy enables users to download all objects under `my-bucketname`.
@@ -272,7 +272,7 @@ Following example shows LDAP users full programmatic access to a LDAP user-speci
## Explore Further
-- [MinIO Client Complete Guide](https://silo.pigsty.io/reference/minio-mc.html)
-- [MinIO STS Quickstart Guide](https://silo.pigsty.io/developers/security-token-service.html)
-- [MinIO Admin Complete Guide](https://silo.pigsty.io/reference/minio-mc-admin.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [MinIO Client Complete Guide](https://silo.pgsty.com/reference/minio-mc/)
+- [MinIO STS Quickstart Guide](https://silo.pgsty.com/developers/security-token-service/)
+- [MinIO Admin Complete Guide](https://silo.pgsty.com/reference/minio-mc-admin/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/multi-user/admin/README.md b/docs/multi-user/admin/README.md
index 9638a5807..79142cd21 100644
--- a/docs/multi-user/admin/README.md
+++ b/docs/multi-user/admin/README.md
@@ -8,12 +8,12 @@ In this document we will explain in detail on how to configure admin users.
### 1. Prerequisites
-- Install mc - [MinIO Client Quickstart Guide](https://silo.pigsty.io/reference/minio-mc.html#quickstart)
-- Install MinIO - [MinIO Quickstart Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html)
+- Install mc - [MinIO Client Quickstart Guide](https://silo.pgsty.com/reference/minio-mc/#quickstart)
+- Install MinIO - [MinIO Quickstart Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/)
### 2. Create a new admin user with CreateUser, DeleteUser and ConfigUpdate permissions
-Use [`mc admin policy`](https://silo.pigsty.io/reference/minio-mc-admin/mc-admin-policy.html#command-mc.admin.policy) to create custom admin policies.
+Use [`mc admin policy`](https://silo.pgsty.com/reference/minio-mc-admin/mc-admin-policy/#command-mc.admin.policy) to create custom admin policies.
Create new canned policy file `adminManageUser.json`. This policy enables admin user to
manage other users.
@@ -162,11 +162,11 @@ mc admin policy attach myminio-admin1 user1policy --user=user1
### 5. Using an external IDP for admin users
Admin users can also be externally managed by an IDP by configuring admin policy with
-special permissions listed above. Follow [MinIO STS Quickstart Guide](https://silo.pigsty.io/developers/security-token-service.html) to manage users with an IDP.
+special permissions listed above. Follow [MinIO STS Quickstart Guide](https://silo.pgsty.com/developers/security-token-service/) to manage users with an IDP.
## Explore Further
-- [MinIO Client Complete Guide](https://silo.pigsty.io/reference/minio-mc.html)
-- [MinIO STS Quickstart Guide](https://silo.pigsty.io/developers/security-token-service.html)
-- [MinIO Admin Complete Guide](https://silo.pigsty.io/reference/minio-mc-admin.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [MinIO Client Complete Guide](https://silo.pgsty.com/reference/minio-mc/)
+- [MinIO STS Quickstart Guide](https://silo.pgsty.com/developers/security-token-service/)
+- [MinIO Admin Complete Guide](https://silo.pgsty.com/reference/minio-mc-admin/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/orchestration/README.md b/docs/orchestration/README.md
index 3bbfb3810..3882645eb 100644
--- a/docs/orchestration/README.md
+++ b/docs/orchestration/README.md
@@ -4,7 +4,7 @@ MinIO is a cloud-native application designed to scale in a sustainable manner in
| Orchestration platforms |
|:---------------------------------------------------------------------------------------------------|
-| [`Kubernetes`](https://silo.pigsty.io/operations/deployments/kubernetes.html) |
+| [`Kubernetes`](https://silo.pgsty.com/operations/deployments/kubernetes/) |
## Why is MinIO cloud-native?
diff --git a/docs/orchestration/docker-compose/README.md b/docs/orchestration/docker-compose/README.md
index 698194c8a..b99f10c42 100644
--- a/docs/orchestration/docker-compose/README.md
+++ b/docs/orchestration/docker-compose/README.md
@@ -50,10 +50,10 @@ Distributed instances are now accessible on the host using the Minio CLI on port
* Update the command section in each service.
* Add a new MinIO server instance to the upstream directive in the Nginx configuration file.
- Read more about distributed MinIO [here](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-as-a-container.html).
+ Read more about distributed MinIO [here](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-as-a-container/).
### Explore Further
* [Overview of Docker Compose](https://docs.docker.com/compose/overview/)
-* [MinIO Docker Quickstart Guide](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-as-a-container.html)
-* [MinIO Erasure Code QuickStart Guide](https://silo.pigsty.io/operations/concepts/erasure-coding.html)
+* [MinIO Docker Quickstart Guide](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-as-a-container/)
+* [MinIO Erasure Code QuickStart Guide](https://silo.pgsty.com/operations/concepts/erasure-coding/)
diff --git a/docs/orchestration/kubernetes/README.md b/docs/orchestration/kubernetes/README.md
index 0af6cd27b..352f1987e 100644
--- a/docs/orchestration/kubernetes/README.md
+++ b/docs/orchestration/kubernetes/README.md
@@ -16,6 +16,6 @@ MinIO server exposes un-authenticated liveness endpoints so Kubernetes can nativ
## Explore Further
-- [MinIO Erasure Code QuickStart Guide](https://silo.pigsty.io/operations/concepts/erasure-coding.html)
+- [MinIO Erasure Code QuickStart Guide](https://silo.pgsty.com/operations/concepts/erasure-coding/)
- [Kubernetes Documentation](https://kubernetes.io/docs/home/)
- [Helm package manager for kubernetes](https://helm.sh/)
diff --git a/docs/select/README.md b/docs/select/README.md
index 62d30a04c..876b460bb 100644
--- a/docs/select/README.md
+++ b/docs/select/README.md
@@ -12,7 +12,7 @@ You can use the Select API to query objects with following features:
Type inference and automatic conversion of values is performed based on the context when the value is un-typed (such as when reading CSV data). If present, the CAST function overrides automatic conversion.
-The [mc sql](https://silo.pigsty.io/reference/minio-mc/mc-sql.html) command can be used for executing queries using the command line.
+The [mc sql](https://silo.pgsty.com/reference/minio-mc/mc-sql/) command can be used for executing queries using the command line.
(*) Parquet is disabled on the MinIO server by default. See below how to enable it.
@@ -27,7 +27,7 @@ To enable Parquet set the environment variable `MINIO_API_SELECT_PARQUET=on`.
### 1. Prerequisites
-- Install MinIO Server from [here](https://silo.pigsty.io/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html#procedure).
+- Install MinIO Server from [here](https://silo.pgsty.com/operations/deployments/baremetal-deploy-minio-on-redhat-linux/#procedure).
- Familiarity with AWS S3 API.
- Familiarity with Python and installing dependencies.
@@ -113,11 +113,11 @@ For a more detailed SELECT SQL reference, please see [here](https://docs.aws.ama
## 5. Explore Further
-- [Use `mc` with MinIO Server](https://silo.pigsty.io/reference/minio-mc.html)
-- [Use `mc sql` with MinIO Server](https://silo.pigsty.io/reference/minio-mc/mc-sql.html#command-mc.sql)
-- [Use `minio-go` SDK with MinIO Server](https://silo.pigsty.io/developers/go/minio-go.html)
-- [Use `aws-cli` with MinIO Server](https://silo.pigsty.io/integrations/aws-cli-with-minio.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [Use `mc` with MinIO Server](https://silo.pgsty.com/reference/minio-mc/)
+- [Use `mc sql` with MinIO Server](https://silo.pgsty.com/reference/minio-mc/mc-sql/#command-mc.sql)
+- [Use `minio-go` SDK with MinIO Server](https://silo.pgsty.com/developers/go/minio-go/)
+- [Use `aws-cli` with MinIO Server](https://silo.pgsty.com/integrations/aws-cli-with-minio/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
## 6. Implementation Status
diff --git a/docs/site-replication/README.md b/docs/site-replication/README.md
index 394b567ef..6e288a27b 100644
--- a/docs/site-replication/README.md
+++ b/docs/site-replication/README.md
@@ -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://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.
+- For [SSE-S3 or SSE-KMS encryption via KMS](https://silo.pgsty.com/operations/server-side-encryption/ "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
diff --git a/docs/sts/README.md b/docs/sts/README.md
index e666d10e4..a08f6f8c5 100644
--- a/docs/sts/README.md
+++ b/docs/sts/README.md
@@ -106,5 +106,5 @@ These credentials can now be used to perform MinIO API operations.
## Explore Further
-- [MinIO Admin Complete Guide](https://silo.pigsty.io/reference/minio-mc-admin.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [MinIO Admin Complete Guide](https://silo.pgsty.com/reference/minio-mc-admin/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/sts/assume-role.md b/docs/sts/assume-role.md
index 963eef912..2263ef353 100644
--- a/docs/sts/assume-role.md
+++ b/docs/sts/assume-role.md
@@ -89,7 +89,7 @@ export MINIO_ROOT_PASSWORD=minio123
minio server ~/test
```
-Create new users following the multi-user guide [here](https://silo.pigsty.io/administration/identity-access-management.html)
+Create new users following the multi-user guide [here](https://silo.pgsty.com/administration/identity-access-management/)
### Testing an example with awscli tool
@@ -134,5 +134,5 @@ SessionToken: eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhY2Nlc3NLZXkiOiIyN1lEUllFT
## Explore Further
-- [MinIO Admin Complete Guide](https://silo.pigsty.io/reference/minio-mc-admin.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [MinIO Admin Complete Guide](https://silo.pgsty.com/reference/minio-mc-admin/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/sts/casdoor.md b/docs/sts/casdoor.md
index 67ce95597..5a0109127 100644
--- a/docs/sts/casdoor.md
+++ b/docs/sts/casdoor.md
@@ -112,5 +112,5 @@ This will open the login page of Casdoor, upon successful login, STS credentials
## Explore Further
- [Casdoor MinIO Integration](https://casdoor.org/docs/integration/minio)
-- [MinIO STS Quickstart Guide](https://silo.pigsty.io/developers/security-token-service.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [MinIO STS Quickstart Guide](https://silo.pgsty.com/developers/security-token-service/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/sts/client-grants.md b/docs/sts/client-grants.md
index daefd77d7..766e7f5df 100644
--- a/docs/sts/client-grants.md
+++ b/docs/sts/client-grants.md
@@ -113,5 +113,5 @@ $ go run client-grants.go -cid PoEgXP6uVO45IsENRngDXj5Au5Ya -csec eKsw6z8CtOJVBt
## Explore Further
-- [MinIO Admin Complete Guide](https://silo.pigsty.io/reference/minio-mc-admin.html)
-- [The MinIO documentation website](https://silo.pigsty.io/index.html)
+- [MinIO Admin Complete Guide](https://silo.pgsty.com/reference/minio-mc-admin/)
+- [The MinIO documentation website](https://silo.pgsty.com/docs/)
diff --git a/docs/sts/dex.md b/docs/sts/dex.md
index d88cb9107..01b758ed4 100644
--- a/docs/sts/dex.md
+++ b/docs/sts/dex.md
@@ -99,5 +99,5 @@ and add relevant policies on MinIO using `mc admin policy create myminio/ MinIO publishes a separate [MinIO Kubernetes Operator and Tenant Helm Chart](https://github.com/minio/operator/tree/master/helm) that is officially maintained and supported. MinIO strongly recommends using the MinIO Kubernetes Operator for production deployments. See [Deploy Operator With Helm](https://silo.pigsty.io/operations/deployments/k8s-deploy-operator-helm-on-kubernetes.html?ref=github) for additional documentation. |
+| This Helm chart is community built, maintained, and supported. MinIO does not guarantee support for any given bug, feature request, or update referencing this chart.
MinIO publishes a separate [MinIO Kubernetes Operator and Tenant Helm Chart](https://github.com/minio/operator/tree/master/helm) that is officially maintained and supported. MinIO strongly recommends using the MinIO Kubernetes Operator for production deployments. See [Deploy Operator With Helm](https://silo.pgsty.com/operations/deployments/k8s-deploy-operator-helm-on-kubernetes/?ref=github) for additional documentation. |
## Introduction
diff --git a/helm/minio/templates/NOTES.txt b/helm/minio/templates/NOTES.txt
index 1769cf57a..2127f0f7e 100644
--- a/helm/minio/templates/NOTES.txt
+++ b/helm/minio/templates/NOTES.txt
@@ -12,7 +12,7 @@ Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubec
You can now access MinIO server on http://localhost:9000. Follow the below steps to connect to MinIO server with mc client:
- 1. Download the MinIO mc client - https://silo.pigsty.io/reference/minio-mc.html#quickstart
+ 1. Download the MinIO mc client - https://silo.pgsty.com/reference/minio-mc/#quickstart
2. export MC_HOST_{{ template "minio.fullname" . }}_local=http://$(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "minio.secretName" . }} -o jsonpath="{.data.rootUser}" | base64 --decode):$(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "minio.secretName" . }} -o jsonpath="{.data.rootPassword}" | base64 --decode)@localhost:{{ .Values.service.port }}
@@ -27,13 +27,13 @@ Note that the public IP may take a couple of minutes to be available.
You can now access MinIO server on http://:9000. Follow the below steps to connect to MinIO server with mc client:
- 1. Download the MinIO mc client - https://silo.pigsty.io/reference/minio-mc.html#quickstart
+ 1. Download the MinIO mc client - https://silo.pgsty.com/reference/minio-mc/#quickstart
2. export MC_HOST_{{ template "minio.fullname" . }}_local=http://$(kubectl get secret {{ template "minio.secretName" . }} --namespace {{ .Release.Namespace }} -o jsonpath="{.data.rootUser}" | base64 --decode):$(kubectl get secret {{ template "minio.secretName" . }} -o jsonpath="{.data.rootPassword}" | base64 --decode)@:{{ .Values.service.port }}
3. mc ls {{ template "minio.fullname" . }}
-Alternately, you can use your browser or the MinIO SDK to access the server - https://silo.pigsty.io/reference/minio-server/minio-server.html
+Alternately, you can use your browser or the MinIO SDK to access the server - https://silo.pgsty.com/reference/minio-server/minio-server/
{{- end }}
{{ if and (.Values.networkPolicy.enabled) (not .Values.networkPolicy.allowExternal) }}
diff --git a/helm/minio/values.yaml b/helm/minio/values.yaml
index a23fc1d12..4f8c55d8a 100644
--- a/helm/minio/values.yaml
+++ b/helm/minio/values.yaml
@@ -88,7 +88,7 @@ runtimeClassName: ""
## Set default rootUser, rootPassword
## rootUser and rootPassword is generated when not set
-## Distributed MinIO ref: https://silo.pigsty.io/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html
+## Distributed MinIO ref: https://silo.pgsty.com/operations/deployments/baremetal/
##
rootUser: ""
rootPassword: ""
@@ -132,7 +132,7 @@ tls:
publicCrt: public.crt
privateKey: private.key
-## Trusted Certificates Settings for MinIO. Ref: https://silo.pigsty.io/operations/network-encryption.html#third-party-certificate-authorities
+## Trusted Certificates Settings for MinIO. Ref: https://silo.pgsty.com/operations/network-encryption/#third-party-certificate-authorities
## Bundle multiple trusted certificates into one secret and pass that here. Ref: https://github.com/minio/minio/tree/master/docs/tls/kubernetes#2-create-kubernetes-secret
## When using self-signed certificates, remember to include MinIO's own certificate in the bundle with key public.crt.
## If certSecret is left empty and tls is enabled, this chart installs the public certificate from .Values.tls.certSecret.
@@ -367,7 +367,7 @@ makePolicyJob:
## List of users to be created after minio install
## Username, password and policy to be assigned to the user.
## Default policies are [readonly|readwrite|writeonly|consoleAdmin|diagnostics].
-## Add new policies as explained here https://silo.pigsty.io/administration/identity-access-management.html#access-management
+## Add new policies as explained here https://silo.pgsty.com/administration/identity-access-management/#access-management
## NOTE: this will fail if LDAP is enabled in your MinIO deployment.
##
## Example:
@@ -399,7 +399,7 @@ makeUserJob:
svcaccts:
[]
## accessKey, secretKey and parent user to be assigned to the service accounts
- ## Add new service accounts as explained here https://silo.pigsty.io/administration/identity-access-management/minio-user-management.html#access-keys
+ ## Add new service accounts as explained here https://silo.pgsty.com/administration/identity-access-management/minio-user-management/#access-keys
# - accessKey: console-svcacct
# secretKey: console123
# user: console
@@ -516,7 +516,7 @@ postJob:
## Use this field to add environment variables relevant to MinIO server. These fields will be passed on to MinIO container(s)
## when Chart is deployed
environment:
- ## Please refer for comprehensive list https://silo.pigsty.io/reference/minio-server/minio-server.html
+ ## Please refer for comprehensive list https://silo.pgsty.com/reference/minio-server/minio-server/
## MINIO_SUBNET_LICENSE: "License key obtained from https://subnet.min.io"
## MINIO_BROWSER: "off"
@@ -528,7 +528,7 @@ extraSecret: ~
## OpenID Identity Management
## The following section documents environment variables for enabling external identity management using an OpenID Connect (OIDC)-compatible provider.
-## See https://silo.pigsty.io/operations/external-iam/configure-openid-external-identity-management.html for a tutorial on using these variables.
+## See https://silo.pgsty.com/operations/external-iam/configure-openid-external-identity-management/ for a tutorial on using these variables.
oidc:
enabled: false
configUrl: "https://identity-provider-url/.well-known/openid-configuration"
diff --git a/internal/config/errors.go b/internal/config/errors.go
index 46c05202b..f43a01370 100644
--- a/internal/config/errors.go
+++ b/internal/config/errors.go
@@ -106,13 +106,13 @@ var (
ErrInvalidErasureEndpoints = newErrFn(
"Invalid endpoint(s) in erasure mode",
"Please provide correct combination of local/remote paths",
- "For more information, please refer to https://silo.pigsty.io/operations/concepts/erasure-coding.html",
+ "For more information, please refer to https://silo.pgsty.com/operations/concepts/erasure-coding/",
)
ErrInvalidNumberOfErasureEndpoints = newErrFn(
"Invalid total number of endpoints for erasure mode",
"Please provide number of endpoints greater or equal to 2",
- "For more information, please refer to https://silo.pigsty.io/operations/concepts/erasure-coding.html",
+ "For more information, please refer to https://silo.pgsty.com/operations/concepts/erasure-coding/",
)
ErrStorageClassValue = newErrFn(
@@ -192,7 +192,7 @@ Examples:
ErrNoCertsAndHTTPSEndpoints = newErrFn(
"HTTPS specified in endpoints, but no TLS certificate is found on the local machine",
"Please add TLS certificate or use HTTP endpoints only",
- "Refer to https://silo.pigsty.io/operations/network-encryption.html for information about how to load a TLS certificate in your server",
+ "Refer to https://silo.pgsty.com/operations/network-encryption/ for information about how to load a TLS certificate in your server",
)
ErrCertsAndHTTPEndpoints = newErrFn(
diff --git a/minio.service b/minio.service
index 25bcb9cea..21c5c4854 100644
--- a/minio.service
+++ b/minio.service
@@ -1,6 +1,6 @@
[Unit]
Description=MinIO
-Documentation=https://silo.pigsty.io
+Documentation=https://silo.pgsty.com/docs/
Wants=network-online.target
After=network-online.target
AssertFileIsExecutable=/usr/local/bin/minio
+
-
+