Updating all references to docs.min.io URLs (#584)

Updating remaining links to the old docs site to point to the new URLs.

Closes #581

source/administration/minio-console.rst

@@ -332,7 +332,7 @@ Some subsections may not be visible if the authenticated user does not have the
 
       The Audit Log section provides an interface for viewing :ref:`audit logs <minio-logging>` collected by a configured PostgreSQL service.
 
-      The Audit Logging feature is configured and enabled automatically for MinIO deployments created using the :docs-k8s:`MinIO Kubernetes Operator <>`.
+      The Audit Logging feature is configured and enabled automatically for MinIO deployments created using the :ref:`MinIO Operator Console <minio-operator-console>`.
 
    .. tab-item:: Trace
 

source/administration/monitoring/bucket-notifications.rst

@@ -161,7 +161,7 @@ Global Events
 ~~~~~~~~~~~~~
 
 MinIO supports triggering notifications on the following global events. 
-You can only listen to these events through the :legacy:`ListenNotification <golang-client-api-reference.html#ListenNotification>` API:
+You can only listen to these events through the `ListenNotification <https://min.io/docs/minio/linux/developers/go/API.html#listennotification-context-context-context-prefix-suffix-string-events-string-chan-notification-info>` API:
 
 .. data:: s3:BucketCreated
 .. data:: s3:BucketRemoved

source/default-conf.py

@@ -73,8 +73,6 @@ extlinks = {
     'iam-docs'        : ('https://docs.aws.amazon.com/IAM/latest/UserGuide/%s',''),
     'minio-release'   : ('https://github.com/minio/minio/releases/tag/%s',''),
     'mc-release'      : ('https://github.com/minio/mc/releases/tag/%s',''),
-    'legacy'          : ('https://docs.min.io/docs/%s',''),
-    'docs-k8s'        : ('https://docs.min.io/minio/k8s/%s',''),
     'prometheus-docs' : ('https://prometheus.io/docs/%s',''),
     'podman-docs'     : ('https://docs.podman.io/en/latest/%s',''),
     'podman-git'      : ('https://github.com/containers/podman/%s',''),

source/includes/common-minio-tiering.rst

@@ -73,7 +73,7 @@ secret key as per your organizations best practices for password generation.
 .. code-block:: shell
    :class: copyable
 
-   wget -O - https://docs.min.io/minio/baremetal/examples/LifecycleManagementAdmin.json | \
+   wget -O - https://min.io/docs/minio/linux/examples/LifecycleManagementAdmin.json | \
    mc admin policy add Alpha LifecycleAdminPolicy /dev/stdin
    mc admin user add Alpha alphaLifecycleAdmin LongRandomSecretKey
    mc admin policy set Alpha LifecycleAdminPolicy user=alphaLifecycleAdmin

source/includes/common-replication.rst

@@ -69,7 +69,7 @@ Bucket replication requires specific permissions on the source and destination d
       .. code-block:: shell
          :class: copyable
 
-         wget -O - https://docs.min.io/minio/baremetal/examples/ReplicationAdminPolicy.json | \
+         wget -O - https://min.io/docs/minio/linux/examples/ReplicationAdminPolicy.json | \
          mc admin policy add TARGET ReplicationAdminPolicy /dev/stdin
          mc admin user add TARGET ReplicationAdmin LongRandomSecretKey
          mc admin policy set TARGET ReplicationAdminPolicy user=ReplicationAdmin
@@ -96,7 +96,7 @@ Bucket replication requires specific permissions on the source and destination d
       .. code-block:: shell
          :class: copyable
 
-         wget -O - https://docs.min.io/minio/baremetal/examples/ReplicationRemoteUserPolicy.json | \
+         wget -O - https://min.io/docs/minio/linux/examples/ReplicationRemoteUserPolicy.json | \
          mc admin policy add TARGET ReplicationRemoteUserPolicy /dev/stdin
          mc admin user add TARGET ReplicationRemoteUser LongRandomSecretKey
          mc admin policy set TARGET ReplicationRemoteUserPolicy user=ReplicationRemoteUser

source/includes/container/steps-deploy-minio-single-node-multi-drive.rst

@@ -138,10 +138,10 @@ The following table describes each line of the command and provides additional c
    RootUser: myminioadmin 
    RootPass: minio-secret-key-change-me 
 
-   Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
+   Command-line: https://min.io/docs/minio/linux/reference/minio-mc.html
       $ mc alias set myminio http://10.0.2.100:9000 myminioadmin minio-secret-key-change-me
 
-   Documentation: https://docs.min.io
+   Documentation: https://min.io/docs/minio/container/index.html
 
 .. admonition:: Container Networks May Not Be Accessible Outside of the Host
 

source/includes/container/steps-deploy-minio-single-node-single-drive.rst

@@ -132,10 +132,10 @@ The command should return a unique ID for the created container.
    RootUser: myminioadmin 
    RootPass: minio-secret-key-change-me 
 
-   Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
+   Command-line: https://min.io/docs/minio/linux/reference/minio-mc.html
       $ mc alias set myminio http://10.0.2.100:9000 myminioadmin minio-secret-key-change-me
 
-   Documentation: https://docs.min.io
+   Documentation: https://min.io/docs/minio/container/index.html
 
 .. admonition:: Container Networks May Not Be Accessible Outside of the Host
 

source/includes/linux/common-installation.rst

@@ -76,10 +76,10 @@ to the following:
    RootUser: minioadmin 
    RootPass: minioadmin 
 
-   Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
+   Command-line: https://min.io/docs/minio/linux/reference/minio-mc.html
       $ mc alias set myminio http://192.0.2.10:9000 minioadmin minioadmin
 
-   Documentation: https://docs.min.io
+   Documentation: https://min.io/docs/minio/linux/index.html
 
    WARNING: Detected default credentials 'minioadmin:minioadmin', we recommend that you change these values with 'MINIO_ROOT_USER' and 'MINIO_ROOT_PASSWORD' environment variables
 
@@ -159,7 +159,7 @@ file manually on all MinIO hosts:
 
    [Unit]
    Description=MinIO
-   Documentation=https://docs.min.io
+   Documentation=https://min.io/docs/minio/linux/index.html
    Wants=network-online.target
    After=network-online.target
    AssertFileIsExecutable=/usr/local/bin/minio

source/includes/linux/deploy-standalone.rst

@@ -77,10 +77,10 @@ to the following:
    RootUser: minioadmin 
    RootPass: minioadmin 
 
-   Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
+   Command-line: https://min.io/docs/minio/linux/reference/minio-mc.html
       $ mc alias set myminio http://192.0.2.10:9000 minioadmin minioadmin
 
-   Documentation: https://docs.min.io
+   Documentation: https://min.io/docs/minio/linux/index.html
 
    WARNING: Detected default credentials 'minioadmin:minioadmin', we recommend that you change these values with 'MINIO_ROOT_USER' and 'MINIO_ROOT_PASSWORD' environment variables
 

source/includes/linux/quickstart.rst

@@ -56,10 +56,10 @@ Procedure
       RootUser: minioadmin
       RootPass: minioadmin
 
-      Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
+      Command-line: https://min.io/docs/minio/linux/reference/minio-mc.html
          $ mc alias set myminio http://192.0.2.10:9000 minioadmin minioadmin
 
-      Documentation: https://docs.min.io
+      Documentation: https://min.io/docs/minio/linux/index.html
 
       WARNING: Detected default credentials 'minioadmin:minioadmin', we recommend that you change these values with 'MINIO_ROOT_USER' and 'MINIO_ROOT_PASSWORD' environment variables.
 

source/includes/linux/steps-deploy-minio-single-node-multi-drive.rst

@@ -40,10 +40,10 @@ The ``journalctl`` output should resemble the following:
    RootUser: myminioadmin 
    RootPass: minio-secret-key-change-me 
 
-   Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
+   Command-line: https://min.io/docs/minio/linux/reference/minio-mc.html
       $ mc alias set myminio http://10.0.2.100:9000 myminioadmin minio-secret-key-change-me
 
-   Documentation: https://docs.min.io
+   Documentation: https://min.io/docs/minio/linux/index.html
 
 The ``API`` block lists the network interfaces and port on which clients can access the MinIO S3 API.
 The ``Console`` block lists the network interfaces and port on which clients can access the MinIO Web Console.

source/includes/linux/steps-deploy-minio-single-node-single-drive.rst

@@ -40,10 +40,10 @@ The ``journalctl`` output should resemble the following:
    RootUser: myminioadmin 
    RootPass: minio-secret-key-change-me 
 
-   Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
+   Command-line: https://min.io/docs/minio/linux/reference/minio-mc.html
       $ mc alias set myminio http://10.0.2.100:9000 myminioadmin minio-secret-key-change-me
 
-   Documentation: https://docs.min.io
+   Documentation: https://min.io/docs/minio/linux/index.html
 
 The ``API`` block lists the network interfaces and port on which clients can access the MinIO S3 API.
 The ``Console`` block lists the network interfaces and port on which clients can access the MinIO Web Console.

source/includes/macos/common-installation.rst

@@ -66,10 +66,10 @@ If desired, you can replace ``~/data`` with another location to which the user h
    RootUser: myminioadmin 
    RootPass: minio-secret-key-change-me 
 
-   Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
+   Command-line: https://min.io/docs/minio/linux/reference/minio-mc.html
       $ mc alias set myminio http://10.0.2.100:9000 myminioadmin minio-secret-key-change-me
 
-   Documentation: https://docs.min.io
+   Documentation: https://min.io/docs/minio/linux/index.html
 
 The ``API`` block lists the network interfaces and port on which clients can access the MinIO S3 API.
 The ``Console`` block lists the network interfaces and port on which clients can access the MinIO Web Console.

source/includes/windows/quickstart.rst

@@ -58,10 +58,10 @@ Procedure
       RootUser: minioadmin
       RootPass: minioadmin
 
-      Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
+      Command-line: https://min.io/docs/minio/linux/reference/minio-mc.html
          $ mc alias set myminio http://192.0.2.10:9000 minioadmin minioadmin
 
-      Documentation: https://docs.min.io
+      Documentation: https://min.io/docs/minio/linux/index.html
 
       WARNING: Detected default credentials 'minioadmin:minioadmin', we recommend that you change these values with 'MINIO_ROOT_USER' and 'MINIO_ROOT_PASSWORD' environment variables.
    

source/integrations/aws-cli-with-minio.md

@@ -6,7 +6,7 @@ In this recipe we will learn how to configure and use AWS CLI to manage data wit
 
 ## 1. Prerequisites
 
-Install MinIO Server from [here](https://docs.min.io).
+Install MinIO Server from [here](https://min.io/docs/minio/linux/index.html#procedure).
 
 ## 2. Installation
 

source/integrations/disaggregated-spark-and-hadoop-hive-with-minio.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://docs.min.io/docs/deploy-minio-on-kubernetes.html#minio-distributed-server-deployment)
+  - [Deployment based on Kubernetes](https://min.io/docs/minio/kubernetes/upstream/operations/installation.html)
   - [Deployment based on MinIO Helm Chart](https://github.com/helm/charts/tree/master/stable/minio)
 
 ## **3. Configure Hadoop, Spark, Hive to use MinIO**

source/integrations/generate-lets-encrypt-certificate-using-certbot-for-minio.md

@@ -6,7 +6,7 @@
 In this recipe, we will generate a Let's Encypt certificate using Certbot. This certificate will then be deployed for use in the MinIO server.
 
 ## 1. Prerequisites
-- Install MinIO Server from [here](https://docs.min.io/docs/minio-quickstart-guide).
+- Install MinIO Server from [here](https://min.io/docs/minio/linux/index.html#procedure).
 - Install Certbot from [here](https://certbot.eff.org/)
 
 ## 2. Dependencies

source/integrations/presigned-put-upload-via-browser.md

@@ -2,7 +2,7 @@
 
 Using pre-signed URLs, a client can upload files directly to an S3-compatible cloud storage server (S3) without exposing the S3 credentials to the user. 
 
-This guide describes how to use the [`presignedPutObject`](https://docs.min.io/docs/javascript-client-api-reference#presignedPutObject) API from the [MinIO JavaScript Library](https://github.com/minio/minio-js) to generate a pre-signed URL. This is demonstrated through a JavaScript example in which an Express Node.js server exposes an endpoint to generate a pre-signed URL and a client-side web application uploads a file to MinIO Server using that URL.
+This guide describes how to use the [`presignedPutObject`](https://min.io/docs/minio/linux/developers/javascript/API.html#presignedPutObject) API from the [MinIO JavaScript Library](https://github.com/minio/minio-js) to generate a pre-signed URL. This is demonstrated through a JavaScript example in which an Express Node.js server exposes an endpoint to generate a pre-signed URL and a client-side web application uploads a file to MinIO Server using that URL.
 
 1. [Create the Server](#createserver) 
 2. [Create the Client-side Web Application](#createclient)
@@ -27,7 +27,7 @@ var client = new Minio.Client({
 
 // Instantiate an `express` server and expose an endpoint called `/presignedUrl` as a `GET` request that
 // accepts a filename through a query parameter called `name`. For the implementation of this endpoint,
-// invoke [`presignedPutObject`](https://docs.min.io/docs/javascript-client-api-reference#presignedPutObject) 
+// invoke [`presignedPutObject`](https://min.io/docs/minio/linux/developers/javascript/API.html#presignedPutObjectt) 
 // on the `Minio.Client` instance to generate a pre-signed URL, and return that URL in the response:
 
 // express is a small HTTP server wrapper, but this works with any HTTP server

source/integrations/setup-nginx-proxy-with-minio.md

@@ -6,7 +6,7 @@ In this recipe we will learn how to set up Nginx proxy with MinIO Server.
 
 ## 1. Prerequisites
 
-Install MinIO Server from [here](https://docs.min.io/docs/minio-quickstart-guide).
+Install MinIO Server from [here](https://min.io/docs/minio/linux/reference/minio-mc.html).
 
 ## 2. Installation
 

source/integrations/using-minio-with-veeam.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 <https://docs.min.io/docs/minio-quickstart-guide.html>
+- MinIO object storage set up per <https://min.io/docs/minio/linux/index.html#procedure>
-- Veeam requires TLS connections to the object storage.  This can be configured per <https://docs.minio.io/docs/how-to-secure-access-to-minio-server-with-tls.html>
+- Veeam requires TLS connections to the object storage.  This can be configured per <https://min.io/docs/minio/linux/operations/network-encryption.html>
 - 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 - <https://docs.min.io/docs/minio-client-quickstart-guide.html>
+- Configure the minio client for the Veeam MinIO endpoint - <https://min.io/docs/minio/linux/reference/minio-mc.html>
 
 ## 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 <https://docs.minio.io/docs/minio-erasure-code-quickstart-guide.html>.
+> Object locking requires erasure coding enabled on the minio server. For more information see <https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html>.
 
 ### Add MinIO as an object store for Veeam
 

source/operations/install-deploy-manage/multi-site-replication.rst

@@ -53,14 +53,14 @@ After enabling site replication, identity and access management (IAM) settings s
          Service accounts for ``root`` do not sync.
 
       #. Policy mapping for synced user accounts
-      #. Policy mapping for `Security Token Service (STS) users <https://docs.min.io/docs/minio-sts-quickstart-guide.html>`__
+      #. Policy mapping for :ref:`Security Token Service (STS) users <minio-security-token-service>`__
 
    .. tab-item:: OIDC
 
       #. Policies
       #. Service accounts associated to OIDC accounts with a valid :ref:`MinIO Policy <minio-policy>`. ``root`` service accounts do not sync.
       #. Policy mapping for synced user accounts
-      #. Policy mapping for `Security Token Service (STS) users <https://docs.min.io/docs/minio-sts-quickstart-guide.html>`__
+      #. Policy mapping for :ref:`Security Token Service (STS) users <minio-security-token-service>`__
 
    .. tab-item:: LDAP
 
@@ -68,7 +68,7 @@ After enabling site replication, identity and access management (IAM) settings s
       #. Groups
       #. Service accounts associated to LDAP accounts with a valid :ref:`MinIO Policy <minio-policy>`. ``root`` service accounts do not sync.
       #. Policy mapping for synced user accounts
-      #. Policy mapping for `Security Token Service (STS) users <https://docs.min.io/docs/minio-sts-quickstart-guide.html>`__
+      #. Policy mapping for :ref:`Security Token Service (STS) users <minio-security-token-service>`__
 
 After the initial synchronization of data across peer sites, MinIO continually replicates and synchronizes :ref:`replicable data <minio-site-replication-what-replicates>` among all sites as they occur on any site.
 

source/reference/minio-mc-admin/mc-admin-prometheus.rst

@@ -20,10 +20,8 @@ use with `Prometheus <https://prometheus.io/>`__.
 
 .. end-mc-admin-prometheus-desc
 
-For more complete documentation on using MinIO with Prometheus, see our
+For more complete documentation on using MinIO with Prometheus, see :ref:`How to monitor MinIO server with Prometheus 
-legacy documentation site 
+<minio-metrics-collect-using-prometheus>`
-:legacy:`How to monitor MinIO server with Prometheus 
-<how-to-monitor-minio-using-prometheus.html>`
 
 .. admonition:: Use ``mc admin`` on MinIO Deployments Only
    :class: note

source/reference/minio-server/minio-server.rst

@@ -24,7 +24,7 @@ For examples of deploying :mc:`minio server` on a bare metal environment,
 see :ref:`minio-installation`.
 
 For examples of deploying :mc:`minio server` on a Kubernetes environment,
-see :docs-k8s:`Kubernetes documentation <>`.
+see :ref:`Deploying a MinIO Tenant <minio-k8s-deploy-minio-tenant>`.
 
 .. admonition:: AGPLv3
    :class: note