minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-06-04 08:42:23 +03:00
Code

DOCS-448: Create new per-platform quickstart guides

Browse Source 
Co-authored by: Ravind Kumar <ravind@min.io>
Co-authored by: Daryl White <53910321+djwfyi@users.noreply.github.com>
This commit is contained in:
Ravind Kumar 2022-03-22 19:18:03 -04:00 committed by Daryl White
parent eb1e901858
commit a566631be2
18 changed files with 1206 additions and 92 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
source/_static/scss/includes/_base.scss
View File

@ -199,9 +199,13 @@ button.toggle-button {
}
.content__main {
img {
a img {
box-shadow: 0px 0px 5px lightgray;
}
a.noshadow img {
box-shadow: none;
}
}
ul.simple li {

40
source/extra/examples/minio-dev.yaml Normal file
View File

@ -0,0 +1,40 @@
# Deploys a new Namespace for the MinIO Pod
apiVersion: v1
kind: Namespace
metadata:
name: minio-dev # Change this value if you want a different namespace name
labels:
name: minio-dev # Change this value to match metadata.name
---
# Deploys a new MinIO Pod into the metadata.namespace Kubernetes namespace
#
# The `spec.containers[0].args` contains the command run on the pod
# The `/data` directory corresponds to the `spec.containers[0].volumeMounts[0].mountPath`
# That mount path corresponds to a Kubernetes HostPath which binds `/data` to a local drive or volume on the worker node where the pod runs
#
apiVersion: v1
kind: Pod
metadata:
labels:
app: minio
name: minio
namespace: minio-dev # Change this value to match the namespace metadata.name
spec:
containers:
- name: minio
image: quay.io/minio/minio:latest
command:
- /bin/bash
- -c
args:
- minio server /data --console-address :9090
volumeMounts:
- mountPath: /data
name: localvolume # Corresponds to the `spec.volumes` Persistent Volume
nodeSelector:
kubernetes.io/hostname: kubealpha.local # Specify a node label associated to the Worker Node on which you want to deploy the pod.
volumes:
- name: localvolume
hostPath: # MinIO generally recommends using locally-attached volumes
path: /mnt/disk1/data # Specify a path to a local drive or volume on the Kubernetes worker node
type: DirectoryOrCreate # The path to the last directory must exist

1
source/images/logos/docker.svg Normal file
View File

@ -0,0 +1 @@
<svg xmlns="http://www.w3.org/2000/svg" width="24" height="17" xmlns:v="https://vecta.io/nano"><path d="M17.816 7.513a3.235 3.235 0 01-.448-2.264c.118-.738.419-1.434.876-2.025.522.26.978.635 1.336 1.096.348.459.578.996.668 1.565l.803-.062a3.61 3.61 0 011.66.27c.207.106.406.229.594.366a.115.115 0 010 .125 2.963 2.963 0 01-1.398 1.712c-.637.353-1.36.52-2.087.48a.146.146 0 00-.167.114 15.068 15.068 0 01-1.711 3.246 10.435 10.435 0 01-5.667 4.017c-1.568.453-3.2.644-4.83.564a12.877 12.877 0 01-2.954-.45A5.28 5.28 0 011.81 14.61a6.918 6.918 0 01-1.22-2.16 10.633 10.633 0 01-.585-2.86v-.866a.73.73 0 01.647-.803h15.402a4.174 4.174 0 001.628-.334l.135-.073zM6.049 4.831h-.96c-.188 0-.25-.052-.25-.24V2.88c0-.177.051-.24.229-.24h1.951c.178 0 .24.063.24.24v1.711c0 .188-.062.24-.25.24h-.96zM8.95 2.66h.96c.187 0 .24.053.24.24v1.712c0 .188-.063.24-.25.24H7.968c-.178 0-.24-.052-.24-.24v-1.7c0-.189.052-.251.24-.251h.98z"/><path d="M11.777 4.831h-.97c-.177 0-.24-.062-.24-.23V2.87c0-.167.063-.23.23-.23h1.961c.167 0 .23.063.23.22v1.742c0 .167-.063.23-.23.23h-.98zM6.06 5.28h.96c.177 0 .24.052.24.22v1.742c0 .167-.063.23-.23.23H5.068c-.167 0-.23-.063-.23-.23V5.51c0-.178.063-.23.23-.23h.991zm2.89 2.191h-.96c-.178 0-.24-.052-.24-.23V5.52c0-.177.062-.24.24-.24h1.95c.168 0 .23.063.23.24v1.722c0 .177 0 .23-.23.23h-.99zm5.697-2.191h.98c.168 0 .23.063.23.22v1.742c0 .167-.062.23-.219.23h-1.982c-.157 0-.22-.063-.22-.23V5.499c0-.167.063-.219.23-.219h.981zM3.2 5.28h.991c.167 0 .23.052.23.23v1.732c0 .167-.063.23-.23.23H2.23c-.167 0-.23-.063-.23-.23V5.499c0-.156.063-.219.23-.219h.97zm8.577 0h.981c.167 0 .23.052.23.23v1.742c0 .157-.063.22-.22.22h-1.982c-.156 0-.219-.063-.219-.22V5.5c0-.167.063-.219.23-.219h.98zm0-3.089h-.98c-.178 0-.23-.052-.23-.23V.24c0-.177.063-.24.23-.24h1.95c.178 0 .24.063.24.24v1.722c0 .177-.062.23-.24.23h-.97z"/></svg>
Side by Side

After

Width:  |  Height:  |  Size: 1.8 KiB

1
source/images/logos/kubernetes.svg Normal file
View File

@ -0,0 +1 @@
<svg xmlns="http://www.w3.org/2000/svg" width="22" height="21" fill="#1e1e1e" xmlns:v="https://vecta.io/nano"><path d="M10.684 20.976c-1.333 0-2.667-.006-4 0a1.544 1.544 0 0 1-1.287-.607 1590.937 1590.937 0 0 0-5.012-6.135A1.47 1.47 0 0 1 .07 12.9l1.809-7.721c.092-.446.398-.821.82-1.007L9.986.742a1.565 1.565 0 0 1 1.394 0l7.29 3.42c.437.191.753.58.847 1.041a5787.78 5787.78 0 0 0 1.81 7.744 1.36 1.36 0 0 1-.283 1.238l-5.108 6.248a1.44 1.44 0 0 1-1.188.544c-1.354-.006-2.708 0-4.063 0zm-.526-15.503a5.68 5.68 0 0 0-3.591 1.682 1.343 1.343 0 0 1-.992-.577l-.239-.246a2.06 2.06 0 0 0-.223-.2.45.45 0 0 0-.606.039.45.45 0 0 0 .046.617c.081.07.169.132.262.186.43.264.954.424 1.111 1.016a5.58 5.58 0 0 0-.881 3.761c.004.04.005.107-.018.12a4.155 4.155 0 0 1-.611.317c-.168.039-.34.062-.512.067a4.74 4.74 0 0 0-.657.11.42.42 0 0 0-.293.485c.04.205.233.345.444.32.157-.017.31-.054.457-.111a1.89 1.89 0 0 1 1.298-.223c.074.022.136.07.175.136a5.671 5.671 0 0 0 2.375 2.904c.04.026.102.068.098.098a2.41 2.41 0 0 1-.113.624 5.501 5.501 0 0 1-.396.656 2.118 2.118 0 0 0-.222.408.39.39 0 0 0 .203.487.4.4 0 0 0 .51-.095c.101-.127.18-.27.23-.424.087-.488.359-.926.76-1.224a5.862 5.862 0 0 0 3.978.015 1.18 1.18 0 0 1 .6.78l.166.482c.044.121.102.235.176.34.11.161.318.224.5.151a.362.362 0 0 0 .26-.436 1.848 1.848 0 0 0-.221-.476l-.463-.766a.592.592 0 0 1 .052-.611 5.702 5.702 0 0 0 2.365-2.924c.019-.05.05-.132.083-.137.192-.042.389-.055.584-.039.251.06.498.14.737.234a3.83 3.83 0 0 0 .43.136.46.46 0 0 0 .512-.271.364.364 0 0 0-.23-.432 1.73 1.73 0 0 0-.494-.132c-.304-.05-.621-.059-.916-.135a1.024 1.024 0 0 1-.455-.283c-.056-.055.005-.214 0-.325l-.109-1.523a5.288 5.288 0 0 0-.817-2.022c.123-.51.537-.697.918-.917a2.87 2.87 0 0 0 .276-.162 1.12 1.12 0 0 0 .234-.219.445.445 0 0 0-.022-.55.432.432 0 0 0-.553-.053 2.499 2.499 0 0 0-.35.313c-.33.327-.621.71-1.164.748a5.779 5.779 0 0 0-3.495-1.7.218.218 0 0 1-.138-.072 1.161 1.161 0 0 1-.156-.87 7.73 7.73 0 0 0 .1-.82.44.44 0 0 0-.12-.334.455.455 0 0 0-.328-.142.463.463 0 0 0-.44.484 1.3 1.3 0 0 0 .008.234c.194.491.148 1.042-.123 1.495v.007z"/><path d="M13.178 14.972l-.499-1.175-.38-.923a.616.616 0 0 1 .034-.433c.078-.155.254-.176.436-.145l2.125.355c.033.006.069.018.138.037-.349.94-1 1.742-1.854 2.284zM7.46 7.912a4.57 4.57 0 0 1 2.677-1.273l-.025.386-.098 1.803a.482.482 0 0 1-.241.465c-.192.098-.342.009-.494-.1L7.46 7.912zM6.103 11.62a4.607 4.607 0 0 1 .665-2.852l1.6 1.401a1.83 1.83 0 0 1 .189.174.374.374 0 0 1-.152.612l-2.302.665zm2.105 3.35a4.593 4.593 0 0 1-1.845-2.28l1.167-.204 1-.168a.477.477 0 0 1 .513.125.47.47 0 0 1 .015.52l-.85 2.007zm5.72-7.058l-1.93 1.341a.384.384 0 0 1-.382.037.374.374 0 0 1-.22-.309l-.127-2.249a.312.312 0 0 1 .028-.079 4.502 4.502 0 0 1 2.63 1.26zm1.354 3.706l-.646-.184-1.533-.431a.44.44 0 0 1-.358-.328.399.399 0 0 1 .178-.409l1.54-1.365.164-.13a4.67 4.67 0 0 1 .655 2.847zm-6.071 3.836l.538-.965.575-1.02a.384.384 0 0 1 .695-.03l1.144 2.01a4.718 4.718 0 0 1-2.952.005zm1.498-5.075c.138.04.316.042.406.13a1.1 1.1 0 0 1 .35.533.827.827 0 0 1-.162.612.809.809 0 0 1-1.218-.011.83.83 0 0 1-.165-.618c.064-.207.19-.392.361-.528.092-.083.272-.078.428-.118z"/></svg>
Side by Side

After

Width:  |  Height:  |  Size: 3.1 KiB

1
source/images/logos/linux.svg Normal file
View File

@ -0,0 +1 @@
<svg xmlns="http://www.w3.org/2000/svg" width="19" height="21" xmlns:v="https://vecta.io/nano"><path d="M18.014 17.15a1.245 1.245 0 0 1-.975-1.24c.01-.438-.176-.86-.508-1.156a4.922 4.922 0 0 0 .043-2.685c-.424-1.24-1.864-3.181-2.922-4.668s-.17-3.18-1.144-5.371S8.95-.036 7.557.914s-.974 3.263-.89 4.338A6.292 6.292 0 0 1 6.584 7.4c-.127.29-1.017 1.322-1.609 2.19s-.993 2.662-1.417 3.39a1.65 1.65 0 0 0-.127 1.403 1.04 1.04 0 0 0-.508.579c-.212.495-.678.702-1.525.866s-.805.661-.636 1.24a2.64 2.64 0 0 1-.211 1.653c-.212.744.847.992 1.99 1.116s2.372.826 3.43.95a1.28 1.28 0 0 0 1.398-.703 14.819 14.819 0 0 1 2.414-.288 10.45 10.45 0 0 1 2.413.247c.147.307.383.565.678.743a1.769 1.769 0 0 0 1.949-.372 16.397 16.397 0 0 1 3.05-1.859c.887-.496.692-1.198.142-1.405zM10.306 2.988a1.124 1.124 0 0 1 1.02 1.198c.01.425-.197.827-.552 1.074l-.254-.124a.7.7 0 0 0 .34-.62.624.624 0 0 0-.551-.66.624.624 0 0 0-.551.688.84.84 0 0 0 .085.372l-.466-.165a1.458 1.458 0 0 1-.127-.537c-.036-.294.049-.59.237-.823a1.15 1.15 0 0 1 .764-.417h.007l.048.014zm-.085 2.56c.296.083.593.29.55.455s-.169.165-.55.413c-.464.3-.962.549-1.483.743-.254.042-.424-.123-.678-.288s-.805-.62-.677-.827l.593-.454c.17-.165.635-.537.93-.496l1.315.454zM7.68 3.194c.466 0 .805.538.805 1.157a1.612 1.612 0 0 1-.042.33l-.34.166-.169.123a.806.806 0 0 0 .085-.495c-.042-.331-.296-.62-.551-.579s-.38.372-.338.702.296.62.55.58h.085l-.339.288a1.188 1.188 0 0 1-.549-1.115c.005-.661.385-1.157.809-1.157H7.68zm-.847 16.184c-.13.328-.368.605-.678.784-.508.166-1.906-.453-2.542-.701s-2.203-.29-2.415-.538.127-.743.17-1.24-.17-.784-.085-1.114 1.1-.33 1.483-.579.466-.908.804-1.073.89.454 1.144.826a26.55 26.55 0 0 0 1.528 2.312c.382.338.599.819.597 1.322l-.006.001zm5.797-4.46a19.23 19.23 0 0 0-.085 2.106 4.415 4.415 0 0 1-2.582 1.61 7.721 7.721 0 0 1-2.373.083l-.887-.992a.665.665 0 0 0 .598-.727v-.058c-.085-.661-2.119-1.611-2.456-2.437a3.855 3.855 0 0 1 .381-2.973c.466-.745.762-2.231 1.229-2.769a3.01 3.01 0 0 0 .677-2.066c-.127-.454.974 1.157 1.695.95s2.245-1.322 2.457-1.115 2.202 4.42 2.414 5.785a5.735 5.735 0 0 1-.127 2.355s-.81-.203-.937.252l-.004-.005zm5.036 3.015c-.296.289-2.033.95-2.542 1.486s-1.186.95-1.567.827a1.211 1.211 0 0 1-.594-1.487 9.92 9.92 0 0 0 .297-2.189c-.042-.496-.127-1.157 0-1.28a.433.433 0 0 1 .34-.042s-.086.951.465 1.198c.593.164 1.23.024 1.695-.372.171-.184.314-.393.423-.62a.532.532 0 0 1 .212.538 1.31 1.31 0 0 0 .55 1.156c.466.248 1.06.538.763.785h-.042z" fill="#1e1e1e"/></svg>
Side by Side

After

Width:  |  Height:  |  Size: 2.4 KiB

1
source/images/logos/macos.svg Normal file
View File

@ -0,0 +1 @@
<svg xmlns="http://www.w3.org/2000/svg" width="17" height="21" xmlns:v="https://vecta.io/nano"><path d="M16.199 7.137a4.723 4.723 0 0 0-2.194 4.335 4.696 4.696 0 0 0 2.768 3.98l-.582 1.42a12.135 12.135 0 0 1-2.161 3.219 2.457 2.457 0 0 1-2.064.868 5.979 5.979 0 0 1-1.15-.297 13.36 13.36 0 0 0-1.283-.45 3.814 3.814 0 0 0-2.364.265 9.29 9.29 0 0 1-1.278.453 2.036 2.036 0 0 1-1.704-.315A5.66 5.66 0 0 1 2.95 19.39a13.326 13.326 0 0 1-2.805-6.38A8.392 8.392 0 0 1 .56 8.438 5.091 5.091 0 0 1 4.221 5.24a4.37 4.37 0 0 1 2.772.327l.964.374a1.56 1.56 0 0 0 1.122 0l1.942-.7a4.785 4.785 0 0 1 5.086 1.762l.092.134zm-7.806-2.37C8.28 2.33 10.066.233 12.453.003c.335 2.336-1.88 5.035-4.06 4.762z" fill="#1e1e1e"/></svg>
Side by Side

After

Width:  |  Height:  |  Size: 711 B

1
source/images/logos/windows.svg Normal file
View File

@ -0,0 +1 @@
<svg xmlns="http://www.w3.org/2000/svg" width="17" height="17" xmlns:v="https://vecta.io/nano"><path d="M16.737.16v7.836H7.954a.929.929 0 0 1-.043-.17V1.643c0-.263.122-.309.344-.328l4.837-.678 3.645-.478zm0 8.55v7.837a3.442 3.442 0 0 1-.354 0l-5.572-.815-2.877-.443V8.711h8.803zM.441 2.384l5.526-.757 1.19-.157v6.526H.441V2.384zm0 6.326H7.17v6.46l-1.934-.262-4.795-.678V8.71z" fill="#1e1e1e"/></svg>
Side by Side

After

Width:  |  Height:  |  Size: 399 B

BIN
source/images/minio-console-buckets.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 69 KiB

BIN
source/images/minio-console-login.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 124 KiB

135
source/index.rst
View File

@ -41,94 +41,68 @@ for complete documentation on the available :mc:`mc` commands.
Quickstart
----------
The following steps deploys MinIO in filesystem mode with a single folder or
disk on the local host. This deployment is best used for initial evaluation of
MinIO S3-compatible object storage. Filesystem mode does not support features
such as versioning and replication.
Select the card corresponding to the platform on which you want to deploy MinIO to display instructions for deploying a :ref:`Standalone <minio-installation-comparison>` MinIO server appropriate for early development and evaluation environments.
1\) Create a Data Folder
Create a folder on the local drive for MinIO to use for object storage
operations. For example:
.. grid:: 3
:gutter: 3
.. code-block:: shell
:class: copyable
mkdir /mnt/data
sudo chmod -R 775 /mnt/data
.. grid-item-card:: Linux
:link-type: ref
:link: quickstart-linux
2\) Download MinIO Server and Commandline Tools
Visit `https://min.io/downloads <https://min.io/downloads?ref=docs>`__ and
following the instructions for your host operating system to download and
configure the :mc:`minio` and :mc:`mc` binaries. Consider adding the
``minio`` and ``mc`` binaries to the operating system PATH for simplified
operations.
.. image:: /images/logos/linux.svg
:width: 100px
:height: 100px
:alt: Linux Quickstart
:align: center
:class: noshadow
Follow the instructions on the download site to start the :mc:`minio server`
process. For example, the following command starts the
:mc:`minio server` using the created directory:
.. grid-item-card:: MacOS
:link-type: ref
:link: quickstart-macos
.. image:: /images/logos/macos.svg
:width: 100px
:height: 100px
:alt: MacOS Quickstart
:align: center
:class: noshadow
.. code-block:: shell
:class: copyable
.. grid-item-card:: Windows
:link-type: ref
:link: quickstart-windows
.. image:: /images/logos/windows.svg
:width: 100px
:height: 100px
:alt: Windows Quickstart
:align: center
:class: noshadow
export MINIO_ROOT_USER=myminioaccesskey
export MINIO_ROOT_PASSWORD=myminiosecretkey
.. grid-item-card:: Kubernetes (Generic)
:link-type: ref
:link: quickstart-kubernetes
.. image:: /images/logos/kubernetes.svg
:width: 100px
:height: 100px
:alt: Kubernetes Quickstart
:align: center
:class: noshadow
minio server /mnt/data
.. grid-item-card:: Docker / Podman
:link-type: ref
:link: quickstart-container
.. image:: /images/logos/docker.svg
:width: 100px
:height: 100px
:alt: Docker Quickstart
:align: center
:class: noshadow
.. list-table::
:stub-columns: 1
:widths: 30 60
:width: 100%
* - :envvar:`MINIO_ROOT_USER`
- The :ref:`root user <minio-users-root>` access key. Replace the
sample value with a long, random, and unique string.
* - :envvar:`MINIO_ROOT_PASSWORD`
- The :ref:`root user <minio-users-root>` secret key. Replace the
sample value with a long, random, and unique string.
The output resembles the following:
.. code-block:: shell
API: http://127.0.0.1:9000
RootUser: minioadmin
RootPass: minioadmin
Region: us-east-1
Console: http://127.0.0.1:64518
RootUser: minioadmin
RootPass: minioadmin
Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
$ mc alias set myminio http://127.0.0.1:9000 minioadmin minioadmin
Documentation: https://docs.min.io
Applications should use one of the addresses listed in the :guilabel:`API`
key for connecting to and performing operations on the MinIO Tenant.
For early development and application, applications can authenticate
using the :guilabel:`RootUser` and :guilabel:`RootPass` credentials.
For long-term development and production, create dedicated users.
See :doc:`/security/iam-overview` for more information.
You can also use the :mc:`mc` commandline tool to perform operations on the
MinIO server. Use :mc:`mc alias set` to update the ``myminio`` alias with
the access key and secret key set on the MinIO server.
3\) Open MinIO Console
Open your browser and http://127.0.0.1:9000 to open the
:ref:`MinIO Console <minio-console>` login page.
Log in with the :guilabel:`Root User` and :guilabel:`Root Pass` from the
previous step.
.. image:: /images/minio-console-dashboard.png
:width: 600px
:alt: MinIO Console Dashboard displaying Monitoring Data
:align: center
You can use the MinIO Console for general administration tasks like
Identity and Access Management, Metrics and Log Monitoring, or
Server Configuration. See :ref:`minio-console` for more information.
:subscript:`All trademarks or logos displayed on this page are the property of their respective owners, and constitute neither an endorsement nor a recommendation of those organizations. In addition, such use of trademarks or links to the web sites of third-party organizations is not intended to imply, directly or indirectly, that those organizations endorse or have any affiliation with MinIO.`
Licensing
---------
@ -157,6 +131,7 @@ without validating their usage do so at their own risk.
:hidden:
/introduction/minio-overview
/quickstart/quickstart
/installation/deployment-and-management
/security/iam-overview
/security/encryption-overview

14
source/installation/deployment-and-management.rst
View File

@ -18,20 +18,12 @@ MinIO supports two deployment modes: :guilabel:`Standalone` and
:guilabel:`Distributed`:
Standalone Deployments
A single MinIO server with a single storage volume or folder. Standalone
deployments are best suited for evaluation and initial development of
applications using MinIO for object storage, *or* for providing an S3 access
layer to single storage volume. Standalone deployments do not provide access
to the full set of MinIO's advanced S3 features and functionality.
A single MinIO server with a single storage volume or folder. Standalone deployments are best suited for evaluation and initial development of applications using MinIO for object storage, *or* for providing an S3 access layer to single storage volume. Standalone deployments do not provide access to the full set of MinIO's advanced S3 features and functionality - specifically those dependent on :ref:`Erasure Coding <minio-erasure-coding>`.
Distributed Deployments
One or more MinIO servers with *at least* four total storage volumes across
all servers. Distributed deployments are best for production environments and
workloads and support all of MinIO's core and advanced S3 features and
functionality.
One or more MinIO servers with *at least* four total storage volumes across all servers. Distributed deployments are best for production environments and workloads and support all of MinIO's core and advanced S3 features and functionality.
MinIO recommends a baseline topology of 4 nodes with 4 drives each
for production environments.
MinIO recommends a baseline topology of 4 nodes with 4 drives each for production environments.
.. _minio-installation-comparison:

373
source/quickstart/container.rst Normal file
View File

@ -0,0 +1,373 @@
.. _quickstart-container:
=========================
Quickstart for Containers
=========================
.. default-domain:: minio
.. |OS| replace:: Docker or Podman
This procedure deploys a :ref:`Standalone <minio-installation-comparison>` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and it's S3-compatible API layer.
Standalone deployments (also called "filesystem mode") support a :ref:`subset of MinIO features <minio-installation-comparison>` where redundancy or availability are dependent entirely on the underlying drive or volume.
For instructions on deploying to production environments, see :ref:`deploy-minio-distributed`.
Prerequisites
-------------
- `Podman <https://podman.io/getting-started/installation.html>`_ or `Docker <https://docs.docker.com/get-docker/>`_ installed.
- Read, write, and delete access to the folder or drive used for the persistent volume.
Procedure
---------
#. Start the container
Select a container type to view instructions to create the container.
Instructions are available for either GNU/Linux and MacOS or for Windows.
.. dropdown:: Podman (Rootfull or Rootless)
:name: podman-root-rootless
These steps work for both rootfull and rootless containers.
.. tab-set::
.. tab-item:: GNU/Linux or MacOS
.. code-block:: shell
:class: copyable
podman run \
-p 9000:9000 \
-p 9090:9090 \
-v ~/minio/data:/data \
-e "MINIO_ROOT_USER=ROOTNAME`" \
-e "MINIO_ROOT_PASSWORD=CHANGEME123" \
quay.io/minio/minio server /data --console-address ":9090"
The example above works this way:
- ``podman run`` starts the container.
The process is attached to the terminal session and ends when exiting the terminal.
- ``-p`` binds a local port to a container port.
- ``-v`` sets a file path as a persistent volume location for the container to use.
When MinIO writes data to ``/data``, that data mirrors to the local path ``~/minio/data``, allowing it to persist between container restarts.
You can set any file path to which the user has read, write, and delete permissions to use.
- ``-e`` sets the environment variables :envvar:`MINIO_ROOT_USER` and :envvar:`MINIO_ROOT_PASSWORD`, respectively.
These set the :ref:`root user credentials <minio-users-root>`.
Change the example values to use for your container.
.. tab-item:: Windows
.. code-block:: shell
:class: copyable
podman run \
-p 9000:9000 \
-p 9090:9090 \
-v D:\data:/data \
-e "MINIO_ROOT_USER=ROOTNAME`" \
-e "MINIO_ROOT_PASSWORD=CHANGEME123" \
quay.io/minio/minio server /data --console-address ":9090"
The example above works this way:
- ``podman run`` starts the container.
- ``-p`` binds a local port to a container port.
- ``-v`` sets a file path as a persistent volume location for the container to use.
When MinIO writes data to ``/data``, that data mirrors to the local path ``D:\data``, allowing it to persist between container restarts.
You can set any file path to which the user has read, write, and delete permissions to use.
- ``-e`` sets the environment variables :envvar:`MINIO_ROOT_USER` and :envvar:`MINIO_ROOT_PASSWORD`, respectively.
These set the :ref:`root user credentials <minio-users-root>`.
Change the example values to use for your container.
.. dropdown:: Docker (Rootfull)
:name: docker-rootfull
.. tab-set::
.. tab-item:: GNU/Linux or MacOS
.. code-block:: shell
:class: copyable
mkdir -p ~/minio/data
docker run \
-p 9000:9000 \
-p 9090:9090 \
--name minio \
-v ~/minio/data:/data \
-e "MINIO_ROOT_USER=ROOTNAME`" \
-e "MINIO_ROOT_PASSWORD=CHANGEME123" \
quay.io/minio/minio server /data --console-address ":9090"
The example above works this way:
- ``mkdir`` creates a new local directory at ``~/minio/data`` in your home directory.
- ``docker run`` starts the MinIO container.
- ``-p`` binds a local port to a container port.
- ``-name`` creates a name for the container.
- ``-v`` sets a file path as a persistent volume location for the container to use.
When MinIO writes data to ``/data``, that data mirrors to the local path ``~/minio/data``, allowing it to persist between container restarts.
You can replace ``~/minio/data`` with another local file location to which the user has read, write, and delete access.
- ``-e`` sets the environment variables :envvar:`MINIO_ROOT_USER` and :envvar:`MINIO_ROOT_PASSWORD`, respectively.
These set the :ref:`root user credentials <minio-users-root>`.
Change the example values to use for your container.
.. tab-item:: Windows
.. code-block:: shell
:class: copyable
docker run \
-p 9000:9000 \
-p 9090:9090 \
--name minio1 \
-v D:\data:/data \
-e "MINIO_ROOT_USER=ROOTUSER" \
-e "MINIO_ROOT_PASSWORD=CHANGEME123" \
quay.io/minio/minio server /data --console-address ":9090"
The example above works this way:
- ``docker run`` starts the MinIO container.
- ``-p`` binds a local port to a container port.
- ``-v`` sets a file path as a persistent volume location for the container to use.
When MinIO writes data to ``/data``, that data mirrors to the local path ``D:\data``, allowing it to persist between container restarts.
You can replace ``D:\data`` with another local file location to which the user has read, write, and delete access.
- ``-e`` sets the environment variables :envvar:`MINIO_ROOT_USER` and :envvar:`MINIO_ROOT_PASSWORD`, respectively.
These set the :ref:`root user credentials <minio-users-root>`.
Change the example values to use for your container.
.. dropdown:: Docker (Rootless)
:name: docker-rootless
.. tab-set::
.. tab-item:: GNU/Linux or MacOS
.. code-block:: shell
:class: copyable
mkdir -p ${HOME}/data
docker run \
-p 9000:9000 \
-p 9090:9090 \
--user $(id -u):$(id -g) \
--name minio1 \
-e "MINIO_ROOT_USER=ROOTUSER" \
-e "MINIO_ROOT_PASSWORD=CHANGEME123" \
-v ${HOME}/minio/data:/data \
quay.io/minio/minio server /data --console-address ":9090"
The example above works this way:
- ``mkdir`` creates a new local directory at ``~/minio/data`` in your home directory.
- ``docker run`` starts the MinIO container.
- ``-p`` binds a local port to a container port.
- ``-user`` sets the username for the container to the policies for the current user and user group.
- ``-name`` creates a name for the container.
- ``-v`` sets a file path as a persistent volume location for the container to use.
When MinIO writes data to ``/data``, that data actually writes to the local path ``~/minio/data`` where it can persist between container restarts.
You can replace ``${HOME}/minio/data`` with another location in the user's home directory to which the user has read, write, and delete access.
- ``-e`` sets the environment variables :envvar:`MINIO_ROOT_USER` and :envvar:`MINIO_ROOT_PASSWORD`, respectively.
These set the :ref:`root user credentials <minio-users-root>`.
Change the example values to use for your container.
.. tab-item:: Windows
Prerequisite:
- Windows `Group Managed Service Account <https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/manage-serviceaccounts>`_ already defined.
.. code-block:: shell
:class: copyable
docker run \
-p 9000:9000 \
-p 9090:9090 \
--name minio1 \
--security-opt "credentialspec=file://path/to/file.json"
-e "MINIO_ROOT_USER=ROOTUSER" \
-e "MINIO_ROOT_PASSWORD=CHANGEME123" \
-v D:\data:/data \
quay.io/minio/minio server /data --console-address ":9090"
The example above works this way:
- ``docker run`` starts the MinIO container.
- ``-p`` binds a local port to a container port.
- ``-name`` creates a name for the container.
- ``--security-opt`` grants access to the container via a ``credentialspec`` file for a `Group Managed Service Account (gMSA) <https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/gmsa-run-container>`_
- ``-v`` sets a file path as a persistent volume location for the container to use.
When MinIO writes data to ``/data``, that data actually writes to the local path ``D:\data`` where it can persist between container restarts.
You can replace ``D:\data`` with another local file location to which the user has read, write, and delete access.
- ``-e`` sets the environment variables :envvar:`MINIO_ROOT_USER` and :envvar:`MINIO_ROOT_PASSWORD`, respectively.
These set the :ref:`root user credentials <minio-users-root>`.
Change the example values to use for your container.
#. Connect your Browser to the MinIO Server
Access the :ref:`minio-console` by going to a browser and going to ``http://127.0.0.1:9000`` or one of the Console addresses specified in the :mc:`minio server` command's output.
For example, :guilabel:`Console: http://192.0.2.10:9090 http://127.0.0.1:9090` in the example output indicates two possible addresses to use for connecting to the Console.
While port ``9000`` is used for connecting to the API, MinIO automatically redirects browser access to the MinIO Console.
Log in to the Console with the credentials you defined in the :envvar:`MINIO_ROOT_USER` and :envvar:`MINIO_ROOT_PASSWORD` environment variables.
.. image:: /images/minio-console-login.png
:width: 600px
:alt: MinIO Console displaying login screen
:align: center
You can use the MinIO Console for general administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration.
Each MinIO server includes its own embedded MinIO Console.
.. image:: /images/minio-console-buckets.png
:width: 600px
:alt: MinIO Console displaying bucket start screen
:align: center
For more information, see the :ref:`minio-console` documentation.
#. `(Optional)` Install the MinIO Client
The :ref:`MinIO Client <minio-client>` allows you to work with your MinIO volume from the commandline.
Select your operating system for instructions.
.. dropdown:: GNU/Linux
The :ref:`MinIO Client <minio-client>` allows you to work with your MinIO server from the commandline.
Download the :mc:`mc` client and install it to a location on your system ``PATH`` such as
``/usr/local/bin``. You can alternatively run the binary from the download location.
.. code-block:: shell
:class: copyable
wget https://dl.min.io/client/mc/release/linux-amd64/mc
chmod +x mc
sudo mv mc /usr/local/bin/mc
Use :mc-cmd:`mc alias set` to create a new alias associated to your local deployment.
You can run :mc-cmd:`mc` commands against this alias:
.. code-block:: shell
:class: copyable
mc alias set local http://127.0.0.1:9000 {MINIO_ROOT_USER} {MINIO_ROOT_PASSWORD}
mc admin info local
Replace ``{MINIO_ROOT_USER}`` and ``{MINIO_ROOT_PASSWORD}`` with the credentials you defined for the container with the ``-e`` flags.
The :mc-cmd:`mc alias set` takes four arguments:
- The name of the alias
- The hostname or IP address and port of the MinIO server
- The Access Key for a MinIO :ref:`user <minio-users>`
- The Secret Key for a MinIO :ref:`user <minio-users>`
For additional details about this command, see :ref:`alias`.
.. dropdown:: MacOS
The :ref:`MinIO Client <minio-client>` allows you to work with your MinIO volume from the commandline.
.. tab-set::
.. tab-item:: Homebrew
Run the following command to install the latest stable MinIO Client package using `Homebrew <https://brew.sh>`_.
.. code-block:: shell
:class: copyable
brew install minio/stable/mc
.. tab-item:: Binary (arm64)
Run the following commands to install the latest stable MinIO Client package using a binary package for Apple chips.
.. code-block:: shell
:class: copyable
curl -O https://dl.min.io/client/mc/release/darwin-arm64/mc
chmod +x mc
sudo mv mc /usr/local/bin/mc
.. tab-item:: Binary (amd64)
Run the following commands to install the latest stable MinIO Client package using a binary package for Intel chips.
.. code-block:: shell
:class: copyable
curl -O https://dl.min.io/client/mc/release/darwin-amd64/mc
chmod +x mc
sudo mv mc /usr/local/bin/mc
Use :mc-cmd:`mc alias set` to quickly authenticate and connect to the MinIO deployment.
.. code-block:: shell
:class: copyable
mc alias set local http://127.0.0.1:9000 {MINIO_ROOT_USER} {MINIO_ROOT_PASSWORD}
mc admin info local
Replace ``{MINIO_ROOT_USER}`` and ``{MINIO_ROOT_PASSWORD}`` with the credentials you defined for the container with the ``-e`` flags.
The :mc-cmd:`mc alias set` takes four arguments:
- The name of the alias
- The hostname or IP address and port of the MinIO server
- The Access Key for a MinIO :ref:`user <minio-users>`
- The Secret Key for a MinIO :ref:`user <minio-users>`
For additional details about this command, see :ref:`alias`.
.. dropdown:: Windows
Download the standalone MinIO server for Windows from the following link:
https://dl.min.io/client/mc/release/windows-amd64/mc.exe
Double click on the file to run it.
Or, run the following in the Command Prompt or PowerShell.
.. code-block::
:class: copyable
\path\to\mc.exe --help
Use :mc-cmd:`mc alias set` to quickly authenticate and connect to the MinIO deployment.
.. code-block:: shell
:class: copyable
mc.exe alias set local http://127.0.0.1:9000 {MINIO_ROOT_USER} {MINIO_ROOT_PASSWORD}
mc.exe admin info local
Replace ``{MINIO_ROOT_USER}`` and ``{MINIO_ROOT_PASSWORD}`` with the credentials you defined for the container with the ``-e`` flags.
The :mc-cmd:`mc alias set` takes four arguments:
- The name of the alias
- The hostname or IP address and port of the MinIO server
- The Access Key for a MinIO :ref:`user <minio-users>`
- The Secret Key for a MinIO :ref:`user <minio-users>`
For additional details about this command, see :ref:`alias`.
Next Steps
----------
- :ref:`Connect your applications to MinIO <minio-drivers>`
- :ref:`Configure Object Retention <minio-object-retention>`
- :ref:`Configure Security <minio-authentication-and-identity-management>`
- :ref:`Deploy MinIO in a Distrbuted Environment <deploy-minio-distributed>`

168
source/quickstart/k8s.rst Normal file
View File

@ -0,0 +1,168 @@
.. _quickstart-kubernetes:
=========================
Quickstart for Kubernetes
=========================
.. default-domain:: minio
.. |OS| replace:: Kubernetes
This procedure deploys a :ref:`Standalone <minio-installation-comparison>` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and it's S3-compatible API layer.
Standalone deployments (also called "filesystem mode") support a :ref:`subset of MinIO features <minio-installation-comparison>` where redundancy or availability are dependent entirely on the underlying drive or volume.
For production-ready :ref:`Distributed <minio-installation-comparison>` MinIO deployments on Kubernetes, use the :docs-k8s:`MinIO Kubernetes Operator <>`.
Prerequisites
-------------
- An existing Kubernetes deployment where *at least* one Worker Node has a locally-attached drive.
- A local ``kubectl`` installation configured to create and access resources on the target Kubernetes deployment.
- Familiarity with Kubernetes environments
- Familiarity with using a Terminal or Shell environment
Procedure
---------
#. **Download the MinIO Object**
.. tab-set::
.. tab-item:: Download the MinIO Kubernetes Object Definition
Download `minio-dev.yaml <https://raw.githubusercontent.com/minio/docs/master/source/extra/examples/minio-dev.yaml>`__ to your host machine:
.. code-block:: shell
:class: copyable
curl https://raw.githubusercontent.com/minio/docs/master/source/extra/examples/minio-dev.yaml -O
The file describes two Kubernetes resources:
- A new namespace ``minio-dev``, and
- A MinIO pod using a drive or volume on the Worker Node for serving data
Select the :guilabel:`Overview of the MinIO Object YAML` for a more detailed description of the object.
.. tab-item:: Overview of the MinIO Object YAML
The ``minio-dev.yaml`` contains the following Kubernetes resources:
.. literalinclude:: /extra/examples/minio-dev.yaml
:language: yaml
The object deploys two resources:
- A new namespace ``minio-dev``, and
- A MinIO pod using a drive or volume on the Worker Node for serving data
The MinIO resource definition uses Kubernetes :kube-docs:`Node Selectors and Labels <concepts/scheduling-eviction/assign-pod-node/#built-in-node-labels>` to restrict the pod to a node with matching hostname label.
Use ``kubectl get nodes --show-labels`` to view all labels assigned to each node in the cluster.
The MinIO Pod uses a :kube-docs:`hostPath <concepts/storage/volumes/#hostpath>` volume for storing data. This path *must* correspond to a local drive or folder on the Kubernetes worker node.
Users familiar with Kubernetes scheduling and volume provisioning may modify the ``spec.nodeSelector``, ``volumeMounts.name``, and ``volumes`` fields to meet more specific requirements.
#. **Apply the MinIO Object Definition**
The following command applies the ``minio-dev.yaml`` configuration and deploys the objects to Kubernetes:
.. code-block:: shell
:class: copyable
kubectl apply -f minio-dev.yaml
The command output should resemble the following:
.. code-block:: shell
namespace/minio-dev created
pod/minio created
You can verify the state of the pod by running ``kubectl get pods``:
.. code-block:: shell
:class: copyable
kubectl get pods -n minio-dev
The output should resemble the following:
.. code-block:: shell
NAME READY STATUS RESTARTS AGE
minio 1/1 Running 0 77s
You can also use the following commands to retrieve detailed information on the pod status:
.. code-block:: shell
:class: copyable
kubectl describe pod/minio -n minio-dev
kubectl logs pod/minio -n minio-dev
#. **Temporarily Access the MinIO S3 API and Console**
Use the ``kubectl port-forward`` command to temporarily forward traffic from the MinIO pod to the local machine:
.. code-block:: shell
:class: copyable
kubectl port-forward pod/minio 9000 9090
The command forwards the pod ports ``9000`` and ``9090`` to the matching port on the local machine while active in the shell.
The ``kubectl port-forward`` command only functions while active in the shell session.
Terminating the session closes the ports on the local machine.
.. note::
The following steps of this procedure assume an active ``kubectl port-forward`` command.
To configure long term access to the pod, configure :kube-docs:`Ingress <concepts/services-networking/ingress/>` or similar network control components within Kubernetes to route traffic to and from the pod. Configuring Ingress is out of the scope for this documentation.
#. **Connect your Browser to the MinIO Server**
Access the :ref:`minio-console` by opening a browser on the local machine and navigating to ``http://127.0.0.1:9090``.
Log in to the Console with the credentials ``minioadmin | minioadmin``.
These are the default :ref:`root user <minio-users-root>` credentials.
.. image:: /images/minio-console-login.png
:width: 600px
:alt: MinIO Console displaying login screen
:align: center
You can use the MinIO Console for general administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration.
Each MinIO server includes its own embedded MinIO Console.
.. image:: /images/minio-console-buckets.png
:width: 600px
:alt: MinIO Console displaying bucket start screen
:align: center
For more information, see the :ref:`minio-console` documentation.
#. **(Optional) Connect the MinIO Client**
If your local machine has :mc:`mc` :ref:`installed <mc-install>`, use the :mc-cmd:`mc alias set` command to authenticate and connect to the MinIO deployment:
.. code-block:: shell
:class: copyable
mc alias set k8s-minio-dev http://127.0.0.1:9000 minioadmin minioadmin
mc admin info k8s-minio-dev
- The name of the alias
- The hostname or IP address and port of the MinIO server
- The Access Key for a MinIO :ref:`user <minio-users>`
- The Secret Key for a MinIO :ref:`user <minio-users>`
Next Steps
----------
- :ref:`Connect your applications to MinIO <minio-drivers>`
- :ref:`Configure Object Retention <minio-object-retention>`
- :ref:`Configure Security <minio-authentication-and-identity-management>`
- :ref:`Deploy MinIO for Production Environments <deploy-minio-distributed>`

132
source/quickstart/linux.rst Normal file
View File

@ -0,0 +1,132 @@
.. _quickstart-linux:
====================
Quickstart for Linux
====================
.. default-domain:: minio
.. |OS| replace:: Linux
This procedure deploys a :ref:`Standalone <minio-installation-comparison>` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and it's S3-compatible API layer.
Standalone deployments (also called "filesystem mode") support a :ref:`subset of MinIO features <minio-installation-comparison>` where redundancy or availability are dependent entirely on the underlying drive or volume.
For instructions on deploying to production environments, see :ref:`deploy-minio-distributed`.
Prerequisites
-------------
- Read, Write and Execute permissions on your local user folder (e.g. ``~/minio``).
- Permission to install binaries to the system ``PATH`` (e.g. access to ``/usr/local/bin``).
- Familiarity with the Linux terminal or shell (Bash, ZSH, etc.).
- A 64-bit Linux OS (e.g. RHEL 8, Ubuntu LTS releases).
Procedure
---------
#. **Install the MinIO Server**
.. include:: /includes/common-installation.rst
:start-after: start-install-minio-binary-desc
:end-before: end-install-minio-binary-desc
#. **Launch the MinIO Server**
Run the following command from the system terminal or shell to start a local MinIO instance using the ``~/minio`` folder. You can replace this path with another folder path on the local machine:
.. code-block:: shell
:class: copyable
mkdir ~/minio
minio server ~/minio --console-address :9090
The ``mkdir`` command creates the folder explicitly at the specified path.
The ``minio server`` command starts the MinIO server. The path argument
``~/minio`` identifies the folder in which the server operates.
The :mc:`minio server` process prints its output to the system console, similar to the following:
.. code-block:: shell
API: http://192.0.2.10:9000 http://127.0.0.1:9000
RootUser: minioadmin
RootPass: minioadmin
Console: http://192.0.2.10:9090 http://127.0.0.1:9090
RootUser: minioadmin
RootPass: minioadmin
Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
$ mc alias set myminio http://192.0.2.10:9000 minioadmin minioadmin
Documentation: https://docs.min.io
WARNING: Detected default credentials 'minioadmin:minioadmin', we recommend that you change these values with 'MINIO_ROOT_USER' and 'MINIO_ROOT_PASSWORD' environment variables.
#. **Connect Your Browser to the MinIO Server**
Open http://127.0.0.1:9000 in a web browser to access the :ref:`MinIO Console <minio-console>`.
You can alternatively enter any of the network addresses specified as part of the server command output.
For example, :guilabel:`Console: http://192.0.2.10:9090 http://127.0.0.1:9090` in the example output indicates two possible addresses to use for connecting to the Console.
While the port ``9000`` is used for connecting to the API, MinIO automatically redirects browser access to the MinIO Console.
Log in to the Console with the ``RootUser`` and ``RootPass`` user credentials displayed in the output.
These default to ``minioadmin | minioadmin``.
.. image:: /images/minio-console-login.png
:width: 600px
:alt: MinIO Console displaying login screen
:align: center
You can use the MinIO Console for general administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration.
Each MinIO server includes its own embedded MinIO Console.
.. image:: /images/minio-console-buckets.png
:width: 600px
:alt: MinIO Console displaying bucket start screen
:align: center
For more information, see the :ref:`minio-console` documentation.
#. `(Optional)` **Install the MinIO Client**
The :ref:`MinIO Client <minio-client>` allows you to work with your MinIO server from the commandline.
Download the :mc:`mc` client and install it to a location on your system ``PATH`` such as
``/usr/local/bin``. You can alternatively run the binary from the download location.
.. code-block:: shell
:class: copyable
wget https://dl.min.io/client/mc/release/linux-amd64/mc
chmod +x mc
sudo mv mc /usr/local/bin/mc
Use :mc-cmd:`mc alias set` to create a new alias associated to your local deployment.
You can run :mc-cmd:`mc` commands against this alias:
.. code-block:: shell
:class: copyable
mc alias set local http://127.0.0.1:9000 minioadmin minioadmin
mc admin info local
The :mc-cmd:`mc alias set` takes four arguments:
- The name of the alias
- The hostname or IP address and port of the MinIO server
- The Access Key for a MinIO :ref:`user <minio-users>`
- The Secret Key for a MinIO :ref:`user <minio-users>`
The example above uses the :ref:`root user <minio-users-root>`.
Next Steps
----------
- :ref:`Connect your applications to MinIO <minio-drivers>`
- :ref:`Configure Object Retention <minio-object-retention>`
- :ref:`Configure Security <minio-authentication-and-identity-management>`
- :ref:`Deploy MinIO for Production Environments <deploy-minio-distributed>`

203
source/quickstart/macos.rst Normal file
View File

@ -0,0 +1,203 @@
.. _quickstart-macos:
=======================
Quickstart for Mac OSX
=======================
.. default-domain:: minio
.. |OS| replace:: MacOS
This procedure deploys a :ref:`Standalone <minio-installation-comparison>` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and it's S3-compatible API layer.
Standalone deployments (also called "filesystem mode") support a :ref:`subset of MinIO features <minio-installation-comparison>` where redundancy or availability are dependent entirely on the underlying drive or volume.
For instructions on deploying to production environments, see :ref:`deploy-minio-distributed`.
Prerequisites
-------------
- Read, write, and execute permissions for the user's home directory
- Familiarity with using the Terminal
Procedure
---------
#. Install the MinIO Server
.. tab-set::
.. tab-item:: Homebrew
Open a Terminal and run the following command to install the latest stable MinIO package using `Homebrew <https://brew.sh>`_.
.. code-block:: shell
:class: copyable
brew install minio/stable/minio
.. important::
If you previously installed the MinIO server using ``brew install minio``, then we recommend that you reinstall from ``minio/stable/minio`` instead.
.. code-block:: shell
:class: copyable
brew uninstall minio
brew install minio/stable/minio
.. tab-item:: Binary - arm64
Open a Terminal, then use the following commands to download the standalone MinIO server for MacOS and make it executable.
.. code-block:: shell
:class: copyable
curl -O https://dl.min.io/server/minio/release/darwin-arm64/minio
chmod +x minio
.. tab-item:: Binary - amd64
Open a Terminal, then use the following commands to download the standalone MinIO server for MacOS and make it executable.
.. code-block:: shell
:class: copyable
curl -O https://dl.min.io/server/minio/release/darwin-amd64/minio
chmod +x minio
#. Launch the :mc:`minio server`
From the Terminal, use this command to start a local MinIO instance in the ``~/data`` folder.
If desired, you can replace ``~/data`` with another location to which the user has read, write, and delete access for the MinIO instance.
.. code-block:: shell
:class: copyable
~/minio server ~/data --console-address :9090
If you installed with Homebrew, do not include the ``~/`` at the beginning of the command.
The :mc:`minio server` process prints its output to the system console, similar to the following:
.. code-block:: shell
API: http://192.0.2.10:9000 http://127.0.0.1:9000
RootUser: minioadmin
RootPass: minioadmin
Console: http://192.0.2.10:9090 http://127.0.0.1:9090
RootUser: minioadmin
RootPass: minioadmin
Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
$ mc alias set myminio http://192.0.2.10:9000 minioadmin minioadmin
Documentation: https://docs.min.io
WARNING: Detected default credentials 'minioadmin:minioadmin', we recommend that you change these values with 'MINIO_ROOT_USER' and 'MINIO_ROOT_PASSWORD' environment variables.
#. Connect your Browser to the MinIO Server
Access the :ref:`minio-console` by going to a browser (such as Safari) and going to ``https://127.0.0.1:9000`` or one of the Console addresses specified in the :mc:`minio server` command's output.
For example, :guilabel:`Console: http://192.0.2.10:9090 http://127.0.0.1:9090` in the example output indicates two possible addresses to use for connecting to the Console.
While port ``9000`` is used for connecting to the API, MinIO automatically redirects browser access to the MinIO Console.
Log in to the Console with the ``RootUser`` and ``RootPass`` user credentials displayed in the output.
These default to ``minioadmin | minioadmin``.
.. image:: /images/minio-console-login.png
:width: 600px
:alt: MinIO Console displaying login screen
:align: center
You can use the MinIO Console for general administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration.
Each MinIO server includes its own embedded MinIO Console.
.. image:: /images/minio-console-buckets.png
:width: 600px
:alt: MinIO Console displaying bucket start screen
:align: center
For more information, see the :ref:`minio-console` documentation.
#. `(Optional)` Install the MinIO Client
The :ref:`MinIO Client <minio-client>` allows you to work with your MinIO volume from the commandline.
.. tab-set::
.. tab-item:: Homebrew
Run the following commands to install the latest stable MinIO Client package using `Homebrew <https://brew.sh>`_.
.. code-block:: shell
:class: copyable
brew install minio/stable/mc
To use the command, run
.. code-block::
mc {command} {flag}
.. tab-item:: Binary (arm64)
Download the standalone MinIO server for MacOS and make it executable.
.. code-block:: shell
:class: copyable
curl -O https://dl.min.io/client/mc/release/darwin-arm64/mc
chmod +x mc
sudo mv mc /usr/local/bin/mc
To use the command, run
.. code-block:: shell
mc {command} {flag}
.. tab-item:: Binary (amd64)
Download the standalone MinIO server for MacOS and make it executable.
.. code-block:: shell
:class: copyable
curl -O https://dl.min.io/client/mc/release/darwin-amd64/mc
chmod +x mc
sudo mv mc /usr/local/bin/mc
To use the command, run
.. code-block:: shell
mc {command} {flag}
Use :mc-cmd:`mc alias set` to quickly authenticate and connect to the MinIO deployment.
.. code-block:: shell
:class: copyable
mc alias set local http://127.0.0.1:9000 minioadmin minioadmin
mc admin info local
The :mc-cmd:`mc alias set` takes four arguments:
- The name of the alias
- The hostname or IP address and port of the MinIO server
- The Access Key for a MinIO :ref:`user <minio-users>`
- The Secret Key for a MinIO :ref:`user <minio-users>`
For additional details about this command, see :ref:`alias`.
Next Steps
----------
- :ref:`Connect your applications to MinIO <minio-drivers>`
- :ref:`Configure Object Retention <minio-object-retention>`
- :ref:`Configure Security <minio-authentication-and-identity-management>`
- :ref:`Deploy MinIO for Production Environments <deploy-minio-distributed>`

83
source/quickstart/quickstart.rst Normal file
View File

@ -0,0 +1,83 @@
.. _quickstart-index:
==========
Quickstart
==========
.. default-domain:: minio
MinIO is a high performance object storage solution with native support for Kubernetes deployments. MinIO provides an Amazon Web Services S3-compatible API and supports all core S3 features. MinIO is released under `GNU Affero General Public License v3.0 <https://www.gnu.org/licenses/agpl-3.0.en.html>`__.
Select the card corresponding to the platform on which you want to deploy MinIO to display instructions for deploying a :ref:`Standalone <minio-installation-comparison>` MinIO server appropriate for early development and evaluation environments.
.. grid:: 3
:gutter: 3
.. grid-item-card:: Linux
:link-type: ref
:link: quickstart-linux
.. image:: /images/logos/linux.svg
:width: 100px
:height: 100px
:alt: Linux Quickstart
:align: center
:class: noshadow
.. grid-item-card:: MacOS
:link-type: ref
:link: quickstart-macos
.. image:: /images/logos/macos.svg
:width: 100px
:height: 100px
:alt: MacOS Quickstart
:align: center
:class: noshadow
.. grid-item-card:: Windows
:link-type: ref
:link: quickstart-windows
.. image:: /images/logos/windows.svg
:width: 100px
:height: 100px
:alt: Windows Quickstart
:align: center
:class: noshadow
.. grid-item-card:: Kubernetes (Generic)
:link-type: ref
:link: quickstart-kubernetes
.. image:: /images/logos/kubernetes.svg
:width: 100px
:height: 100px
:alt: Kubernetes Quickstart
:align: center
:class: noshadow
.. grid-item-card:: Docker / Podman
:link-type: ref
:link: quickstart-container
.. image:: /images/logos/docker.svg
:width: 100px
:height: 100px
:alt: Docker Quickstart
:align: center
:class: noshadow
:subscript:`All trademarks or logos displayed on this page are the property of their respective owners, and constitute neither an endorsement nor a recommendation of those organizations. In addition, such use of trademarks or links to the web sites of third-party organizations is not intended to imply, directly or indirectly, that those organizations endorse or have any affiliation with MinIO.`
.. toctree::
:titlesonly:
:hidden:
/quickstart/linux
/quickstart/container
/quickstart/macos
/quickstart/windows
/quickstart/k8s

137
source/quickstart/windows.rst Normal file
View File

@ -0,0 +1,137 @@
.. _quickstart-windows:
======================
Quickstart for Windows
======================
.. default-domain:: minio
.. |OS| replace:: Windows
This procedure deploys a :ref:`Standalone <minio-installation-comparison>` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and it's S3-compatible API layer.
Standalone deployments (also called "filesystem mode") support a :ref:`subset of MinIO features <minio-installation-comparison>` where redundancy or availability are dependent entirely on the underlying drive or volume.
For instructions on deploying to production environments, see :ref:`deploy-minio-distributed`.
Prerequisites
-------------
- Read, write, and execute permissions for the preferred local directory or file path
- Familiarity with using the Command Prompt or PowerShell
Procedure
---------
#. Install the MinIO Server
Download the MinIO executable from the following URL:
.. code-block:: shell
:class: copyable
https://dl.min.io/server/minio/release/windows-amd64/minio.exe
The next step includes instructions for running the executable.
You cannot run the executable from the Explorer or by double clicking the file.
Instead, you call the executable to launch the server.
#. Launch the :mc:`minio server`
In PowerShell or the Command Prompt, navigate to the location of the executable or add the path of the ``minio.exe`` file to the system ``$PATH``.
Use this command to start a local MinIO instance in the ``C:\minio`` folder.
You can replace ``C:\minio`` with another drive or folder path on the local computer.
.. code-block::
:class: copyable
.\minio.exe server C:\minio --console-address :9090
The :mc:`minio server` process prints its output to the system console, similar to the following:
.. code-block:: shell
API: http://192.0.2.10:9000 http://127.0.0.1:9000
RootUser: minioadmin
RootPass: minioadmin
Console: http://192.0.2.10:9090 http://127.0.0.1:9090
RootUser: minioadmin
RootPass: minioadmin
Command-line: https://docs.min.io/docs/minio-client-quickstart-guide
$ mc alias set myminio http://192.0.2.10:9000 minioadmin minioadmin
Documentation: https://docs.min.io
WARNING: Detected default credentials 'minioadmin:minioadmin', we recommend that you change these values with 'MINIO_ROOT_USER' and 'MINIO_ROOT_PASSWORD' environment variables.
The process is tied to the current PowerShell or Command Prompt window.
Closing the window stops the server and ends the process.
#. Connect your Browser to the MinIO Server
Access the :ref:`minio-console` by going to a browser (such as Microsoft Edge) and going to ``http://127.0.0.1:9000`` or one of the Console addresses specified in the :mc:`minio server` command's output.
For example, :guilabel:`Console: http://192.0.2.10:9090 http://127.0.0.1:9090` in the example output indicates two possible addresses to use for connecting to the Console.
While port ``9000`` is used for connecting to the API, MinIO automatically redirects browser access to the MinIO Console.
Log in to the Console with the ``RootUser`` and ``RootPass`` user credentials displayed in the output.
These default to ``minioadmin | minioadmin``.
.. image:: /images/minio-console-login.png
:width: 600px
:alt: MinIO Console displaying login screen
:align: center
You can use the MinIO Console for general administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration.
Each MinIO server includes its own embedded MinIO Console.
.. image:: /images/minio-console-buckets.png
:width: 600px
:alt: MinIO Console displaying bucket start screen
:align: center
For more information, see the :ref:`minio-console` documentation.
#. `(Optional)` Install the MinIO Client
The :ref:`MinIO Client <minio-client>` allows you to work with your MinIO volume from the commandline.
Download the standalone MinIO server for Windows from the following link:
https://dl.min.io/client/mc/release/windows-amd64/mc.exe
Double click on the file to run it.
Or, run the following in the Command Prompt or PowerShell.
.. code-block::
:class: copyable
\path\to\mc.exe --help
Use :mc-cmd:`mc.exe alias set <mc alias set>` to quickly authenticate and connect to the MinIO deployment.
.. code-block:: shell
:class: copyable
mc.exe alias set local http://127.0.0.1:9000 minioadmin minioadmin
mc.exe admin info local
The :mc-cmd:`mc.exe alias set <mc alias set>` takes four arguments:
- The name of the alias
- The hostname or IP address and port of the MinIO server
- The Access Key for a MinIO :ref:`user <minio-users>`
- The Secret Key for a MinIO :ref:`user <minio-users>`
For additional details about this command, see :ref:`alias`.
Next Steps
----------
- :ref:`Connect your applications to MinIO <minio-drivers>`
- :ref:`Configure Object Retention <minio-object-retention>`
- :ref:`Configure Security <minio-authentication-and-identity-management>`
- :ref:`Deploy MinIO for Production Environments <deploy-minio-distributed>`

2
source/reference/minio-mc.rst
View File

@ -1,3 +1,5 @@
.. _minio-client:
=====================
MinIO Client (``mc``)
=====================