mirror of
https://github.com/minio/docs.git
synced 2025-07-31 18:04:52 +03:00
Final pass on platformization (#555)
This commit is contained in:
@ -121,7 +121,7 @@ F) Select :guilabel:`Save` to finish adding the replication rule
|
||||
|
||||
.. start-create-bucket-replication-rule-cli-desc
|
||||
|
||||
Use the :mc-cmd:`mc replicate add` command to add a new replication rule to each MinIO deployment.
|
||||
Use the :mc:`mc replicate add` command to add a new replication rule to each MinIO deployment.
|
||||
|
||||
.. code-block:: shell
|
||||
:class: copyable
|
||||
@ -147,7 +147,7 @@ Use the :mc-cmd:`mc replicate add` command to add a new replication rule to each
|
||||
See :mc-cmd:`mc replicate add --replicate` for more complete documentation.
|
||||
Omit any field to disable replication of that component.
|
||||
|
||||
Specify any other supported optional arguments for :mc-cmd:`mc replicate add`.
|
||||
Specify any other supported optional arguments for :mc:`mc replicate add`.
|
||||
|
||||
.. end-create-bucket-replication-rule-cli-desc
|
||||
|
||||
@ -175,14 +175,14 @@ F) Go to the other deployment's console and select the destination bucket define
|
||||
|
||||
.. start-validate-bucket-replication-cli-desc
|
||||
|
||||
Use :mc-cmd:`mc cp` to copy a new object to the replicated bucket on one of the deployments.
|
||||
Use :mc:`mc cp` to copy a new object to the replicated bucket on one of the deployments.
|
||||
|
||||
.. code-block:: shell
|
||||
:class: copyable
|
||||
|
||||
mc cp ~/foo.txt ALIAS/BUCKET
|
||||
|
||||
Use :mc-cmd:`mc ls` to verify the object exists on the destination bucket:
|
||||
Use :mc:`mc ls` to verify the object exists on the destination bucket:
|
||||
|
||||
.. code-block:: shell
|
||||
:class: copyable
|
||||
|
@ -91,7 +91,7 @@ Include any other environment variables as required for your local deployment.
|
||||
You can access the MinIO deployment over a Terminal or Shell using the :ref:`MinIO Client <minio-client>` (:mc:`mc`).
|
||||
See :ref:`MinIO Client Installation Quickstart <mc-install>` for instructions on installing :mc:`mc`.
|
||||
|
||||
Create a new :mc-cmd:`alias <mc alias set>` corresponding to the MinIO deployment.
|
||||
Create a new :mc:`alias <mc alias set>` corresponding to the MinIO deployment.
|
||||
Specify any of the hostnames or IP addresses from the MinIO Server ``API`` block, such as http://localhost:9000.
|
||||
|
||||
.. code-block:: shell
|
||||
|
@ -109,7 +109,7 @@ If you run |KES| without tying it to the current shell session (e.g. with ``nohu
|
||||
.. start-kes-generate-key-desc
|
||||
|
||||
MinIO requires that the |EK| exist on the root KMS *before* performing |SSE| operations using that key.
|
||||
Use ``kes key create`` *or* :mc:`mc admin kms key create` to add a new |EK| for use with |SSE|.
|
||||
Use ``kes key create`` *or* :mc-cmd:`mc admin kms key create` to add a new |EK| for use with |SSE|.
|
||||
|
||||
The following command uses the ``kes key create`` command to add a new External Key (EK) stored on the root KMS server for use with encrypting the MinIO backend.
|
||||
|
||||
|
Reference in New Issue
Block a user