diff --git a/README.md b/README.md index e93590a7f..ef0bf52da 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ Use the following commands to run a standalone MinIO server as a container. Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, -with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Overview](https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html) +with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Overview](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html) for more complete documentation. ### Stable @@ -38,7 +38,7 @@ root credentials. You can use the Browser to create buckets, upload objects, and You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, -see to view MinIO SDKs for supported languages. +see to view MinIO SDKs for supported languages. > [!NOTE] > To deploy MinIO on with persistent storage, you must map local persistent directories from the host OS to the container using the `podman -v` option. @@ -48,7 +48,7 @@ see to view MinI Use the following commands to run a standalone MinIO server on macOS. -Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Overview](https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html) for more complete documentation. +Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Overview](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html) for more complete documentation. ### Homebrew (recommended) @@ -69,7 +69,7 @@ brew install minio/stable/minio The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded web-based object browser built into MinIO Server. Point a web browser running on the host machine to and log in with the root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. -You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see to view MinIO SDKs for supported languages. +You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see to view MinIO SDKs for supported languages. ### Binary Download @@ -83,7 +83,7 @@ chmod +x minio The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded web-based object browser built into MinIO Server. Point a web browser running on the host machine to and log in with the root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. -You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see to view MinIO SDKs for supported languages. +You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see to view MinIO SDKs for supported languages. ## GNU/Linux @@ -105,10 +105,10 @@ The following table lists supported architectures. Replace the `wget` URL with t The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded web-based object browser built into MinIO Server. Point a web browser running on the host machine to and log in with the root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. -You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see to view MinIO SDKs for supported languages. +You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see to view MinIO SDKs for supported languages. > [!NOTE] -> Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Overview](https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html#) for more complete documentation. +> Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Overview](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html) for more complete documentation. ## Microsoft Windows @@ -126,10 +126,10 @@ minio.exe server D:\ The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded web-based object browser built into MinIO Server. Point a web browser running on the host machine to and log in with the root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. -You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see to view MinIO SDKs for supported languages. +You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see to view MinIO SDKs for supported languages. > [!NOTE] -> Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Overview](https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html#) for more complete documentation. +> Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Overview](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html) for more complete documentation. ## Install from Source @@ -141,10 +141,10 @@ go install github.com/minio/minio@latest The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded web-based object browser built into MinIO Server. Point a web browser running on the host machine to and log in with the root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. -You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see to view MinIO SDKs for supported languages. +You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see to view MinIO SDKs for supported languages. > [!NOTE] -> Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Overview](https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html) for more complete documentation. +> Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Overview](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html) for more complete documentation. MinIO strongly recommends *against* using compiled-from-source MinIO servers for production environments. @@ -229,7 +229,7 @@ For example, consider a MinIO deployment behind a proxy `https://minio.example.n ## Test using MinIO Client `mc` -`mc` provides a modern alternative to UNIX commands like ls, cat, cp, mirror, diff etc. It supports filesystems and Amazon S3 compatible cloud storage services. Follow the MinIO Client [Quickstart Guide](https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart) for further instructions. +`mc` provides a modern alternative to UNIX commands like ls, cat, cp, mirror, diff etc. It supports filesystems and Amazon S3 compatible cloud storage services. Follow the MinIO Client [Quickstart Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart) for further instructions. ## Upgrading MinIO @@ -238,7 +238,7 @@ Upgrades require zero downtime in MinIO, all upgrades are non-disruptive, all tr > [!NOTE] > requires internet access to update directly from , optionally you can host any mirrors at -- For deployments that installed the MinIO server binary by hand, use [`mc admin update`](https://min.io/docs/minio/linux/reference/minio-mc-admin/mc-admin-update.html) +- For deployments that installed the MinIO server binary by hand, use [`mc admin update`](https://docs.min.io/community/minio-object-store/reference/minio-mc-admin/mc-admin-update.html) ```sh mc admin update @@ -258,10 +258,10 @@ mc admin update ## Explore Further -- [MinIO Erasure Code Overview](https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html) -- [Use `mc` with MinIO Server](https://min.io/docs/minio/linux/reference/minio-mc.html) -- [Use `minio-go` SDK with MinIO Server](https://min.io/docs/minio/linux/developers/go/minio-go.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [MinIO Erasure Code Overview](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html) +- [Use `mc` with MinIO Server](https://docs.min.io/community/minio-object-store/reference/minio-mc.html) +- [Use `minio-go` SDK with MinIO Server](https://docs.min.io/community/minio-object-store/developers/go/minio-go.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) ## Contribute to MinIO Project diff --git a/cmd/format-erasure.go b/cmd/format-erasure.go index d37833349..5cbcb495a 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://min.io/docs/minio/linux/operations/install-deploy-manage/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://docs.min.io/community/minio-object-store/operations/deployments/baremetal-migrate-fs-gateway.html`, 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 c2ef35649..ce98d0086 100644 --- a/cmd/server-startup-msg.go +++ b/cmd/server-startup-msg.go @@ -184,7 +184,7 @@ func printCLIAccessMsg(endPoint string, alias string) { // Get saved credentials. cred := globalActiveCred - const mcQuickStartGuide = "https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart" + const mcQuickStartGuide = "https://docs.min.io/community/minio-object-store/reference/minio-mc.html#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 2965c38e1..d122f4d0d 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://min.io/docs/minio/kubernetes/upstream/index.html#quickstart-for-kubernetes" + kubernetesDeploymentDoc = "https://docs.min.io/community/minio-object-store/operations/deployments/kubernetes.html" // Mesos deployment doc link. - mesosDeploymentDoc = "https://min.io/docs/minio/kubernetes/upstream/index.html#quickstart-for-kubernetes" + mesosDeploymentDoc = "https://docs.min.io/community/minio-object-store/operations/deployments/kubernetes.html" ) func getDownloadURL(releaseTag string) (downloadURL string) { diff --git a/docs/bigdata/README.md b/docs/bigdata/README.md index d77c5160a..39a7efe5c 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://min.io/docs/minio/kubernetes/upstream/index.html#quickstart-for-kubernetes) + - [Deployment based on Kubernetes](https://docs.min.io/community/minio-object-store/operations/deployments/kubernetes.html) - [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 ff72a252d..f534023ac 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://min.io/docs/minio/linux/developers/go/API.html#setbucketlifecycle-ctx-context-context-bucketname-config-lifecycle-configuration-error) +- [MinIO | Golang Client API Reference](https://docs.min.io/community/minio-object-store/developers/go/API.html#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 edf5cab22..6888838f7 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://min.io/docs/minio/linux/index.html#quickstart-for-linux). -- Install `mc` - [mc Quickstart Guide](https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart) +- Install MinIO - [MinIO Quickstart Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html). +- Install `mc` - [mc Quickstart Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#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://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/administration/object-management/object-versioning.html) 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://min.io/docs/minio/linux/developers/go/API.html) +- [MinIO | Golang Client API Reference](https://docs.min.io/community/minio-object-store/developers/go/API.html) - [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 15feebff9..062f75fe6 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://min.io/docs/minio/linux/reference/minio-mc/mc-event-add.html). MinIO SDK's [`BucketNotification` APIs](https://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/reference/minio-mc/mc-event-add.html). MinIO SDK's [`BucketNotification` APIs](https://docs.min.io/community/minio-object-store/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). 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://min.io/docs/minio/linux/index.html#procedure). -- Install and configure MinIO Client from [here](https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart). +- Install and configure MinIO Server from [here](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html#procedure). +- Install and configure MinIO Client from [here](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart). ``` $ mc admin config get myminio | grep notify diff --git a/docs/bucket/quota/README.md b/docs/bucket/quota/README.md index 003ad5d40..643a65cc9 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://min.io/docs/minio/linux/index.html#procedure). -- [Use `mc` with MinIO Server](https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart) +- Install MinIO - [MinIO Quickstart Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html#procedure). +- [Use `mc` with MinIO Server](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart) ## Set bucket quota configuration diff --git a/docs/bucket/replication/DESIGN.md b/docs/bucket/replication/DESIGN.md index 9ad87cff5..2f3d55f0d 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://min.io/docs/minio/linux/administration/object-management/object-versioning.html) -- [MinIO Client Quickstart Guide](https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart) +- [MinIO Bucket Versioning Implementation](https://docs.min.io/community/minio-object-store/administration/object-management/object-versioning.html) +- [MinIO Client Quickstart Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart) diff --git a/docs/bucket/replication/README.md b/docs/bucket/replication/README.md index 67165ac21..829d98f00 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://min.io/docs/minio/linux/administration/bucket-replication.html) page. The [Bucket Replication](https://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/administration/bucket-replication.html) page. The [Bucket Replication](https://docs.min.io/community/minio-object-store/administration/bucket-replication/bucket-replication-requirements.html) 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://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/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. ## 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://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/administration/object-management/object-retention.html) 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/minio/minio/blob/master/docs/bucket/replication/DESIGN.md) -- [MinIO Bucket Versioning Implementation](https://min.io/docs/minio/linux/administration/object-management/object-retention.html) -- [MinIO Client Quickstart Guide](https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart) +- [MinIO Bucket Versioning Implementation](https://docs.min.io/community/minio-object-store/administration/object-management/object-retention.html) +- [MinIO Client Quickstart Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart) diff --git a/docs/bucket/retention/README.md b/docs/bucket/retention/README.md index f588ca162..c5087b22a 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://min.io/docs/minio/linux/index.html#quickstart-for-linux) +- Install MinIO - [MinIO Quickstart Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html) - 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://min.io/docs/minio/linux/reference/minio-mc.html#quickstart) -- [Use `aws-cli` with MinIO Server](https://min.io/docs/minio/linux/integrations/aws-cli-with-minio.html) -- [Use `minio-go` SDK with MinIO Server](https://min.io/docs/minio/linux/developers/go/minio-go.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [Use `mc` with MinIO Server](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart) +- [Use `aws-cli` with MinIO Server](https://docs.min.io/community/minio-object-store/integrations/aws-cli-with-minio.html) +- [Use `minio-go` SDK with MinIO Server](https://docs.min.io/community/minio-object-store/developers/go/minio-go.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/bucket/versioning/README.md b/docs/bucket/versioning/README.md index 44e5d0401..aeb9aa001 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://min.io/docs/minio/linux/developers/java/minio-java.html) -- [Object Lock and Immutability Guide](https://min.io/docs/minio/linux/administration/object-management/object-retention.html) -- [MinIO Admin Complete Guide](https://min.io/docs/minio/linux/reference/minio-mc-admin.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [Use `minio-java` SDK with MinIO Server](https://docs.min.io/community/minio-object-store/developers/java/minio-java.html) +- [Object Lock and Immutability Guide](https://docs.min.io/community/minio-object-store/administration/object-management/object-retention.html) +- [MinIO Admin Complete Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc-admin.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/chroot/README.md b/docs/chroot/README.md index c551ceb79..e2d2c3381 100644 --- a/docs/chroot/README.md +++ b/docs/chroot/README.md @@ -39,8 +39,8 @@ Instance is now accessible on the host at port 9000, proceed to access the Web b ## Explore Further -- [MinIO Erasure Code Overview](https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html) -- [Use `mc` with MinIO Server](https://min.io/docs/minio/linux/reference/minio-mc.html) -- [Use `aws-cli` with MinIO Server](https://min.io/docs/minio/linux/integrations/aws-cli-with-minio.html) -- [Use `minio-go` SDK with MinIO Server](https://min.io/docs/minio/linux/developers/go/minio-go.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [MinIO Erasure Code Overview](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html) +- [Use `mc` with MinIO Server](https://docs.min.io/community/minio-object-store/reference/minio-mc.html) +- [Use `aws-cli` with MinIO Server](https://docs.min.io/community/minio-object-store/integrations/aws-cli-with-minio.html) +- [Use `minio-go` SDK with MinIO Server](https://docs.min.io/community/minio-object-store/developers/go/minio-go.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/compression/README.md b/docs/compression/README.md index 1a8500514..cc7bac663 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://min.io/docs/minio/linux/index.html#quickstart-for-linux). +Install MinIO - [MinIO Quickstart Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html). ### 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://min.io/docs/minio/linux/reference/minio-mc.html) -- [Use `aws-cli` with MinIO Server](https://min.io/docs/minio/linux/integrations/aws-cli-with-minio.html) -- [Use `minio-go` SDK with MinIO Server](https://min.io/docs/minio/linux/developers/go/minio-go.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [Use `mc` with MinIO Server](https://docs.min.io/community/minio-object-store/reference/minio-mc.html) +- [Use `aws-cli` with MinIO Server](https://docs.min.io/community/minio-object-store/integrations/aws-cli-with-minio.html) +- [Use `minio-go` SDK with MinIO Server](https://docs.min.io/community/minio-object-store/developers/go/minio-go.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/config/README.md b/docs/config/README.md index 030032962..943475274 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://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/operations/network-encryption.html). 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://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/administration/monitoring.html#bucket-notifications). ``` notify_webhook publish bucket notifications to webhook endpoints @@ -336,5 +336,5 @@ minio server /data ## Explore Further -* [MinIO Quickstart Guide](https://min.io/docs/minio/linux/index.html#quickstart-for-linux) -* [Configure MinIO Server with TLS](https://min.io/docs/minio/linux/operations/network-encryption.html) +* [MinIO Quickstart Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html) +* [Configure MinIO Server with TLS](https://docs.min.io/community/minio-object-store/operations/network-encryption.html) diff --git a/docs/debugging/README.md b/docs/debugging/README.md index 08e7c1ce8..df01c6e35 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://min.io/docs/minio/linux/reference/minio-mc-admin/mc-admin-trace.html) command. +HTTP tracing can be enabled by using [`mc admin trace`](https://docs.min.io/community/minio-object-store/reference/minio-mc-admin/mc-admin-trace.html) command. Example: diff --git a/docs/distributed/README.md b/docs/distributed/README.md index 9fe7e9edb..0ebf6cfcb 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/minio/minio/blob/master/docs/erasure/README.md#what-is-bit-rot-protection) using [erasure code](https://min.io/docs/minio/linux/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/minio/minio/blob/master/docs/erasure/README.md#what-is-bit-rot-protection) using [erasure code](https://docs.min.io/community/minio-object-store/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. 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://min.io/docs/minio/kubernetes/upstream/index.html#quickstart-for-kubernetes). -- [Deploy a Tenant from the MinIO Operator](https://min.io/docs/minio/kubernetes/upstream/operations/install-deploy-manage/deploy-minio-tenant.html) +- [MinIO Quickstart Guide for Kubernetes](https://docs.min.io/community/minio-object-store/operations/deployments/kubernetes.html). +- [Deploy a Tenant from the MinIO Operator](https://docs.min.io/community/minio-object-store/operations/deployments/k8s-deploy-minio-tenant-on-kubernetes.html) Install Distributed MinIO on Linux: -- [Deploy Distributed MinIO on Linux](https://min.io/docs/minio/linux/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html#deploy-distributed-minio) +- [Deploy Distributed MinIO on Linux](https://docs.min.io/community/minio-object-store/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html#deploy-distributed-minio) ### 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://min.io/docs/minio/linux/reference/minio-mc.html#quickstart). +To test this setup, access the MinIO server via browser or [`mc`](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart). ## Explore Further -- [MinIO Erasure Code QuickStart Guide](https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html) -- [Use `mc` with MinIO Server](https://min.io/docs/minio/linux/reference/minio-mc.html) -- [Use `aws-cli` with MinIO Server](https://min.io/docs/minio/linux/integrations/aws-cli-with-minio.html) -- [Use `minio-go` SDK with MinIO Server](https://min.io/docs/minio/linux/developers/go/minio-go.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [MinIO Erasure Code QuickStart Guide](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html) +- [Use `mc` with MinIO Server](https://docs.min.io/community/minio-object-store/reference/minio-mc.html) +- [Use `aws-cli` with MinIO Server](https://docs.min.io/community/minio-object-store/integrations/aws-cli-with-minio.html) +- [Use `minio-go` SDK with MinIO Server](https://docs.min.io/community/minio-object-store/developers/go/minio-go.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/docker/README.md b/docs/docker/README.md index 093467579..ccc9031f5 100644 --- a/docs/docker/README.md +++ b/docs/docker/README.md @@ -8,7 +8,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://min.io/docs/minio/container/operations/install-deploy-manage/deploy-minio-single-node-multi-drive.html) MinIO deployment. +*Note*: Standalone MinIO is intended for early development and evaluation. For production clusters, deploy a [Distributed](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-as-a-container.html) 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. @@ -57,7 +57,7 @@ docker run \ We recommend kubernetes based deployment for production level deployment . -See the [Kubernetes documentation](https://min.io/docs/minio/kubernetes/upstream/index.html) for more information. +See the [Kubernetes documentation](https://docs.min.io/community/minio-object-store/operations/deployments/kubernetes.html) for more information. ## MinIO Docker Tips @@ -211,5 +211,5 @@ docker stats ## Explore Further -* [Distributed MinIO Quickstart Guide](https://min.io/docs/minio/container/operations/install-deploy-manage/deploy-minio-single-node-multi-drive.html) -* [MinIO Erasure Code QuickStart Guide](https://min.io/docs/minio/container/operations/concepts/erasure-coding.html) +* [MinIO in a Container Installation Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-as-a-container.html) +* [MinIO Erasure Code QuickStart Guide](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html) diff --git a/docs/erasure/README.md b/docs/erasure/README.md index cbee49ac1..48b3cb6bb 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://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html) 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://min.io/docs/minio/linux/index.html#quickstart-for-linux) +Install MinIO - [MinIO Quickstart Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html) ### 2. Run MinIO Server with Erasure Code diff --git a/docs/erasure/storage-class/README.md b/docs/erasure/storage-class/README.md index 3842d4a01..15190a65a 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://min.io/docs/minio/linux/operations/concepts/erasure-coding.html#erasure-sets). +For more complete documentation on Erasure Set sizing, see the [MinIO Documentation on Erasure Sets](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html#erasure-sets). ### Allowed values for REDUCED_REDUNDANCY storage class diff --git a/docs/federation/lookup/README.md b/docs/federation/lookup/README.md index 5ab514fab..b2cebd63b 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://min.io/docs/minio/linux/index.html#quickstart-for-linux). +Install MinIO - [MinIO Quickstart Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html). ### 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://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart). You’ll see the uploaded files are accessible from the all the MinIO endpoints. ## Explore Further -- [Use `mc` with MinIO Server](https://min.io/docs/minio/linux/reference/minio-mc.html) -- [Use `aws-cli` with MinIO Server](https://min.io/docs/minio/linux/integrations/aws-cli-with-minio.html) -- [Use `minio-go` SDK with MinIO Server](https://min.io/docs/minio/linux/developers/go/minio-go.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [Use `mc` with MinIO Server](https://docs.min.io/community/minio-object-store/reference/minio-mc.html) +- [Use `aws-cli` with MinIO Server](https://docs.min.io/community/minio-object-store/integrations/aws-cli-with-minio.html) +- [Use `minio-go` SDK with MinIO Server](https://docs.min.io/community/minio-object-store/developers/go/minio-go.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/integrations/veeam/README.md b/docs/integrations/veeam/README.md index 830130e86..c8c7556d1 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 10ee57e99..86d9d8c05 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://min.io/docs/minio/linux/index.html#quickstart-for-linux) 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://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html) 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://min.io/docs/minio/linux/operations/network-encryption.html) +- [Run MinIO with TLS / HTTPS](https://docs.min.io/community/minio-object-store/operations/network-encryption.html) - [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://min.io/docs/minio/linux/reference/minio-mc.html) -- [Use `aws-cli` with MinIO Server](https://min.io/docs/minio/linux/integrations/aws-cli-with-minio.html) -- [Use `minio-go` SDK with MinIO Server](https://min.io/docs/minio/linux/developers/go/minio-go.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [Use `mc` with MinIO Server](https://docs.min.io/community/minio-object-store/reference/minio-mc.html) +- [Use `aws-cli` with MinIO Server](https://docs.min.io/community/minio-object-store/integrations/aws-cli-with-minio.html) +- [Use `minio-go` SDK with MinIO Server](https://docs.min.io/community/minio-object-store/developers/go/minio-go.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/lambda/README.md b/docs/lambda/README.md index f4994224e..7e571e850 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://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/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. ## 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://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/developers/go/API.html#presignedgetobject-ctx-context-context-bucketname-objectname-string-expiry-time-duration-reqparams-url-values-url-url-error) ```go package main diff --git a/docs/logging/README.md b/docs/logging/README.md index 0706233d5..7abc62a1e 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://min.io/docs/minio/linux/reference/minio-mc.html#quickstart) +Assuming `mc` is already [configured](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart) ``` mc admin config get myminio/ logger_webhook @@ -42,7 +42,7 @@ minio server /mnt/data ## Audit Targets -Assuming `mc` is already [configured](https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart) +Assuming `mc` is already [configured](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart) ### Audit HTTP Target @@ -224,5 +224,5 @@ NOTE: ## Explore Further -- [MinIO Quickstart Guide](https://min.io/docs/minio/linux/index.html#quickstart-for-linux) -- [Configure MinIO Server with TLS](https://min.io/docs/minio/linux/operations/network-encryption.html) +- [MinIO Quickstart Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html) +- [Configure MinIO Server with TLS](https://docs.min.io/community/minio-object-store/operations/network-encryption.html) diff --git a/docs/metrics/prometheus/README.md b/docs/metrics/prometheus/README.md index 0921ae675..3cfb94e41 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://min.io/docs/minio/linux/index.html#quickstart-for-linux). +To get started with MinIO, refer [MinIO QuickStart Document](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html). 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://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/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 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 d45cce054..705000648 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://min.io/docs/minio/linux/operations/install-deploy-manage/multi-site-replication.html) configurations. -For deployments with [bucket](https://min.io/docs/minio/linux/administration/bucket-replication.html) or [batch](https://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/operations/install-deploy-manage/multi-site-replication.html) configurations. +For deployments with [bucket](https://docs.min.io/community/minio-object-store/administration/bucket-replication.html) or [batch](https://docs.min.io/community/minio-object-store/administration/batch-framework.html#replicate) configurations, these metrics populate instead under the [Bucket Metrics](#bucket-metrics) endpoint. | Name | Description |:-----------------------------------------------------------|:---------------------------------------------------------------------------------------------------------| @@ -108,8 +108,8 @@ For deployments with [bucket](https://min.io/docs/minio/linux/administration/buc ## Node Replication Metrics -Metrics marked as ``Site Replication Only`` only populate on deployments with [Site Replication](https://min.io/docs/minio/linux/operations/install-deploy-manage/multi-site-replication.html) configurations. -For deployments with [bucket](https://min.io/docs/minio/linux/administration/bucket-replication.html) or [batch](https://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/operations/install-deploy-manage/multi-site-replication.html) configurations. +For deployments with [bucket](https://docs.min.io/community/minio-object-store/administration/bucket-replication.html) or [batch](https://docs.min.io/community/minio-object-store/administration/batch-framework.html#replicate) 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://min.io/docs/minio/linux/administration/bucket-replication.html) or [Batch Replication](https://min.io/docs/minio/linux/administration/batch-framework.html) configurations. -For deployments with [Site Replication](https://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/administration/bucket-replication.html) or [Batch Replication](https://docs.min.io/community/minio-object-store/administration/batch-framework.html) configurations. +For deployments with [Site Replication](https://docs.min.io/community/minio-object-store/operations/install-deploy-manage/multi-site-replication.html) configured, select metrics populate under the [Cluster Metrics](#cluster-metrics) endpoint. | Name | Description | |:----------------------------------------------------|:---------------------------------------------------------------------------------| diff --git a/docs/metrics/v3.md b/docs/metrics/v3.md index 5901b2e2f..050bf0925 100644 --- a/docs/metrics/v3.md +++ b/docs/metrics/v3.md @@ -11,7 +11,7 @@ Querying the base endpoint returns "404 Not Found." Metrics are organized into groups at paths **relative** to the top-level endpoint above. -Metrics are also available using the [MinIO Admin Client](https://min.io/docs/minio/linux/reference/minio-mc-admin.html) and the `mc admin prometheus metrics` command. For more information, see [Metrics and Alerts](https://min.io/docs/minio/linux/operations/monitoring/metrics-and-alerts.html) in the MinIO Documentation. +Metrics are also available using the [MinIO Admin Client](https://docs.min.io/community/minio-object-store/reference/minio-mc-admin.html) and the `mc admin prometheus metrics` command. For more information, see [Metrics and Alerts](https://docs.min.io/community/minio-object-store/operations/monitoring/metrics-and-alerts.html) in the MinIO Documentation. ## Metrics Request Handling diff --git a/docs/minio-limits.md b/docs/minio-limits.md index 47f27bd81..e7295d195 100644 --- a/docs/minio-limits.md +++ b/docs/minio-limits.md @@ -36,20 +36,20 @@ For optimal production setup MinIO recommends Linux kernel version 4.x and later > NOTE: While MinIO does not implement an upper boundary on buckets, your cluster's hardware has natural limits that depend on the workload and its scaling patterns. We strongly recommend [MinIO SUBNET](https://min.io/pricing) for architecture and sizing guidance for your production use case. -## List of Amazon S3 API's not supported on MinIO +## List of Amazon S3 APIs not supported on MinIO We found the following APIs to be redundant or less useful outside of AWS S3. If you have a different view on any of the APIs we missed, please consider opening a [GitHub issue](https://github.com/minio/minio/issues) with relevant details on why MinIO must implement them. -### List of Amazon S3 Bucket API's not supported on MinIO +### List of Amazon S3 Bucket APIs not supported on MinIO -- BucketACL (Use [bucket policies](https://min.io/docs/minio/linux/administration/identity-access-management/policy-based-access-control.html) instead) +- BucketACL (Use [bucket policies](https://docs.min.io/community/minio-object-store/administration/identity-access-management/policy-based-access-control.html) 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://min.io/docs/minio/linux/administration/monitoring/bucket-notifications.html) APIs) +- BucketAnalytics, BucketMetrics, BucketLogging (Use [bucket notification](https://docs.min.io/community/minio-object-store/administration/monitoring/bucket-notifications.html) APIs) -### List of Amazon S3 Object API's not supported on MinIO +### List of Amazon S3 Object APIs not supported on MinIO -- ObjectACL (Use [bucket policies](https://min.io/docs/minio/linux/administration/identity-access-management/policy-based-access-control.html) instead) +- ObjectACL (Use [bucket policies](https://docs.min.io/community/minio-object-store/administration/identity-access-management/policy-based-access-control.html) instead) ## Object name restrictions on MinIO diff --git a/docs/multi-tenancy/README.md b/docs/multi-tenancy/README.md index 9af1e15d8..055535e7a 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://min.io/docs/minio/container/index.html#quickstart-for-linux) 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://docs.min.io/community/minio-object-store/operations/deployments/kubernetes.html) to get started with MinIO on orchestration platforms. diff --git a/docs/multi-user/README.md b/docs/multi-user/README.md index b36e1386d..3dbd6ce14 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://min.io/docs/minio/linux/reference/minio-mc.html#quickstart) -- Install MinIO - [MinIO Quickstart Guide](https://min.io/docs/minio/linux/index.html#quickstart-for-linux) +- Install mc - [MinIO Client Quickstart Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart) +- Install MinIO - [MinIO Quickstart Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html) - Configure etcd - [Etcd V3 Quickstart Guide](https://github.com/minio/minio/blob/master/docs/sts/etcd.md) ### 2. Create a new user with canned policy -Use [`mc admin policy`](https://min.io/docs/minio/linux/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://docs.min.io/community/minio-object-store/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. 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://min.io/docs/minio/linux/reference/minio-mc.html) -- [MinIO STS Quickstart Guide](https://min.io/docs/minio/linux/developers/security-token-service.html) -- [MinIO Admin Complete Guide](https://min.io/docs/minio/linux/reference/minio-mc-admin.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [MinIO Client Complete Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc.html) +- [MinIO STS Quickstart Guide](https://docs.min.io/community/minio-object-store/developers/security-token-service.html) +- [MinIO Admin Complete Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc-admin.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/multi-user/admin/README.md b/docs/multi-user/admin/README.md index ae9084e4a..ff43cd7b1 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://min.io/docs/minio/linux/reference/minio-mc.html#quickstart) -- Install MinIO - [MinIO Quickstart Guide](https://min.io/docs/minio/linux/index.html#quickstart-for-linux) +- Install mc - [MinIO Client Quickstart Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc.html#quickstart) +- Install MinIO - [MinIO Quickstart Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html) ### 2. Create a new admin user with CreateUser, DeleteUser and ConfigUpdate permissions -Use [`mc admin policy`](https://min.io/docs/minio/linux/reference/minio-mc-admin/mc-admin-policy.html#command-mc.admin.policy) to create custom admin policies. +Use [`mc admin policy`](https://docs.min.io/community/minio-object-store/reference/minio-mc-admin/mc-admin-policy.html#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://min.io/docs/minio/linux/developers/security-token-service.html) to manage users with an IDP. +special permissions listed above. Follow [MinIO STS Quickstart Guide](https://docs.min.io/community/minio-object-store/developers/security-token-service.html) to manage users with an IDP. ## Explore Further -- [MinIO Client Complete Guide](https://min.io/docs/minio/linux/reference/minio-mc.html) -- [MinIO STS Quickstart Guide](https://min.io/docs/minio/linux/developers/security-token-service.html) -- [MinIO Admin Complete Guide](https://min.io/docs/minio/linux/reference/minio-mc-admin.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [MinIO Client Complete Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc.html) +- [MinIO STS Quickstart Guide](https://docs.min.io/community/minio-object-store/developers/security-token-service.html) +- [MinIO Admin Complete Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc-admin.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/orchestration/README.md b/docs/orchestration/README.md index 6b6d5cf3c..327f83b9d 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://min.io/docs/minio/kubernetes/upstream/index.html#quickstart-for-kubernetes) | +| [`Kubernetes`](https://docs.min.io/community/minio-object-store/operations/deployments/kubernetes.html) | ## Why is MinIO cloud-native? diff --git a/docs/orchestration/docker-compose/README.md b/docs/orchestration/docker-compose/README.md index 220db2cc5..93fc4aa34 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://min.io/docs/minio/container/operations/install-deploy-manage/deploy-minio-single-node-multi-drive.html). + Read more about distributed MinIO [here](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-as-a-container.html). ### Explore Further * [Overview of Docker Compose](https://docs.docker.com/compose/overview/) -* [MinIO Docker Quickstart Guide](https://min.io/docs/minio/container/index.html#quickstart-for-containers) -* [MinIO Erasure Code QuickStart Guide](https://min.io/docs/minio/container/operations/concepts/erasure-coding.html) +* [MinIO Docker Quickstart Guide](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-as-a-container.html) +* [MinIO Erasure Code QuickStart Guide](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html) diff --git a/docs/orchestration/kubernetes/README.md b/docs/orchestration/kubernetes/README.md index 7a46418e6..3ea3fb27a 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://min.io/docs/minio/linux/operations/concepts/erasure-coding.html) +- [MinIO Erasure Code QuickStart Guide](https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html) - [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 ee5333d46..7aff35538 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://min.io/docs/minio/linux/reference/minio-mc/mc-sql.html) command can be used for executing queries using the command line. +The [mc sql](https://docs.min.io/community/minio-object-store/reference/minio-mc/mc-sql.html) 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://min.io/docs/minio/linux/index.html#procedure). +- Install MinIO Server from [here](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html#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://min.io/docs/minio/linux/reference/minio-mc.html) -- [Use `mc sql` with MinIO Server](https://min.io/docs/minio/linux/reference/minio-mc/mc-sql.html#command-mc.sql) -- [Use `minio-go` SDK with MinIO Server](https://min.io/docs/minio/linux/developers/go/minio-go.html) -- [Use `aws-cli` with MinIO Server](https://min.io/docs/minio/linux/integrations/aws-cli-with-minio.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [Use `mc` with MinIO Server](https://docs.min.io/community/minio-object-store/reference/minio-mc.html) +- [Use `mc sql` with MinIO Server](https://docs.min.io/community/minio-object-store/reference/minio-mc/mc-sql.html#command-mc.sql) +- [Use `minio-go` SDK with MinIO Server](https://docs.min.io/community/minio-object-store/developers/go/minio-go.html) +- [Use `aws-cli` with MinIO Server](https://docs.min.io/community/minio-object-store/integrations/aws-cli-with-minio.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) ## 6. Implementation Status diff --git a/docs/site-replication/README.md b/docs/site-replication/README.md index 15024af30..8edcc09de 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://min.io/docs/minio/linux/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://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. ## Configuring Site Replication diff --git a/docs/sts/README.md b/docs/sts/README.md index 87098ce6c..62fa48b18 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://min.io/docs/minio/linux/reference/minio-mc-admin.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [MinIO Admin Complete Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc-admin.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/sts/assume-role.md b/docs/sts/assume-role.md index e94b54103..8b9600f7f 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://min.io/docs/minio/linux/administration/identity-access-management.html) +Create new users following the multi-user guide [here](https://docs.min.io/community/minio-object-store/administration/identity-access-management.html) ### Testing an example with awscli tool @@ -134,5 +134,5 @@ SessionToken: eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhY2Nlc3NLZXkiOiIyN1lEUllFT ## Explore Further -- [MinIO Admin Complete Guide](https://min.io/docs/minio/linux/reference/minio-mc-admin.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [MinIO Admin Complete Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc-admin.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/sts/casdoor.md b/docs/sts/casdoor.md index d11814abe..4bdf745b3 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://min.io/docs/minio/linux/developers/security-token-service.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [MinIO STS Quickstart Guide](https://docs.min.io/community/minio-object-store/developers/security-token-service.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/sts/client-grants.md b/docs/sts/client-grants.md index 1ae0286c9..1d4132adf 100644 --- a/docs/sts/client-grants.md +++ b/docs/sts/client-grants.md @@ -111,5 +111,5 @@ $ go run client-grants.go -cid PoEgXP6uVO45IsENRngDXj5Au5Ya -csec eKsw6z8CtOJVBt ## Explore Further -- [MinIO Admin Complete Guide](https://min.io/docs/minio/linux/reference/minio-mc-admin.html) -- [The MinIO documentation website](https://min.io/docs/minio/linux/index.html) +- [MinIO Admin Complete Guide](https://docs.min.io/community/minio-object-store/reference/minio-mc-admin.html) +- [The MinIO documentation website](https://docs.min.io/community/minio-object-store/index.html) diff --git a/docs/sts/dex.md b/docs/sts/dex.md index e2439b0e0..e7bf3d835 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://min.io/docs/minio/kubernetes/upstream/operations/install-deploy-manage/deploy-operator-helm.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://docs.min.io/community/minio-object-store/operations/deployments/k8s-deploy-operator-helm-on-kubernetes.html?ref=github) for additional documentation. | ## Introduction diff --git a/helm/minio/templates/NOTES.txt b/helm/minio/templates/NOTES.txt index ee02a6fd8..73d77e188 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://min.io/docs/minio/linux/reference/minio-mc.html#quickstart + 1. Download the MinIO mc client - https://docs.min.io/community/minio-object-store/reference/minio-mc.html#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://min.io/docs/minio/linux/reference/minio-mc.html#quickstart + 1. Download the MinIO mc client - https://docs.min.io/community/minio-object-store/reference/minio-mc.html#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://min.io/docs/minio/linux/reference/minio-server/minio-server.html +Alternately, you can use your browser or the MinIO SDK to access the server - https://docs.min.io/community/minio-object-store/reference/minio-server/minio-server.html {{- end }} {{ if and (.Values.networkPolicy.enabled) (not .Values.networkPolicy.allowExternal) }} diff --git a/helm/minio/values.yaml b/helm/minio/values.yaml index 82b3dd8bb..2ea13b10d 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://min.io/docs/minio/linux/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html +## Distributed MinIO ref: https://docs.min.io/community/minio-object-store/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html ## rootUser: "" rootPassword: "" @@ -132,7 +132,7 @@ tls: publicCrt: public.crt privateKey: private.key -## Trusted Certificates Settings for MinIO. Ref: https://min.io/docs/minio/linux/operations/network-encryption.html#third-party-certificate-authorities +## Trusted Certificates Settings for MinIO. Ref: https://docs.min.io/community/minio-object-store/operations/network-encryption.html#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. @@ -369,7 +369,7 @@ makePolicyJob: users: ## 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://min.io/docs/minio/kubernetes/upstream/administration/identity-access-management.html#access-management + ## Add new policies as explained here https://docs.min.io/community/minio-object-store/administration/identity-access-management.html#access-management ## NOTE: this will fail if LDAP is enabled in your MinIO deployment ## make sure to disable this if you are using LDAP. - accessKey: console @@ -398,7 +398,7 @@ makeUserJob: svcaccts: [] ## accessKey, secretKey and parent user to be assigned to the service accounts - ## Add new service accounts as explained here https://min.io/docs/minio/kubernetes/upstream/administration/identity-access-management/minio-user-management.html#service-accounts + ## Add new service accounts as explained here https://docs.min.io/community/minio-object-store/administration/identity-access-management/minio-user-management.html#access-keys # - accessKey: console-svcacct # secretKey: console123 # user: console @@ -515,7 +515,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://min.io/docs/minio/linux/reference/minio-server/minio-server.html + ## Please refer for comprehensive list https://docs.min.io/community/minio-object-store/reference/minio-server/minio-server.html ## MINIO_SUBNET_LICENSE: "License key obtained from https://subnet.min.io" ## MINIO_BROWSER: "off" @@ -527,7 +527,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://min.io/docs/minio/linux/operations/external-iam/configure-openid-external-identity-management.html for a tutorial on using these variables. +## See https://docs.min.io/community/minio-object-store/operations/external-iam/configure-openid-external-identity-management.html 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 44423f42f..3bcb79ce9 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://min.io/docs/minio/linux/operations/concepts/erasure-coding.html", + "For more information, please refer to https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html", ) 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://min.io/docs/minio/linux/operations/concepts/erasure-coding.html", + "For more information, please refer to https://docs.min.io/community/minio-object-store/operations/concepts/erasure-coding.html", ) 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://min.io/docs/minio/linux/operations/network-encryption.html for information about how to load a TLS certificate in your server", + "Refer to https://docs.min.io/community/minio-object-store/operations/network-encryption.html for information about how to load a TLS certificate in your server", ) ErrCertsAndHTTPEndpoints = newErrFn(