mirror of
https://github.com/minio/docs.git
synced 2025-11-09 02:22:17 +03:00
##
We are going to make the following changes to the Object Store docs as
part of a larger QC/Content pass:
### Left Navigation
We want to modify the left navigation flow to be a natural progression
from a basic setup to more advanced.
For example:
- Core Concepts
- Deployment Architecture
- Availability and Resiliency
- Erasure Coding and Object Healing
- Object Scanner
- Site Replication and Failover
- Thresholds and Limits
- Installation
- Deployment Checklist
- Deploy MinIO on Kubernetes
- Deploy MinIO on Red Hat Linux
- Deploy MinIO on Ubuntu Linux
- Deploy MinIO for Development (MacOS, Windows, Container)
- Security and Encryption (Conceptual Overview)
- Network Encryption (TLS) (Conceptual overview)
- Enable Network Encryption using Single Domain
- Enable Network Encryption using Multiple Domains
- Enable Network Encryption using certmanager (Kubernetes only)
- Data Encryption (SSE) (Conceptual overview)
- Enable SSE using AIStor Key Management Server
- Enable SSE using KES (Summary page + linkouts)
- External Identity Management (Conceptual Overview)
- Enable External Identity management using OpenID
- Enable External Identity management using AD/LDAP
- Backup and Recovery
- Create a Multi-Site Replication Configuration
- Recovery after Hardware Failure
- Recover after drive failure
- Recover after node failure
- Recover after site failure
- Monitoring and Alerts
- Metrics and Alerting (v3 reference)
- Monitoring and Alerting using Prometheus
- Monitoring and Alerting using InfluxDB
- Monitoring and Alerting using Grafana
- Metrics V2 Reference
- Publish Server and Audit Logs to External Services
- MinIO Healthcheck API
The Administration, Developer, and Reference sections will remain as-is
for now.
http://192.241.195.202:9000/staging/singleplat/mindocs/index.html
# Goals
Maintaining multiple platforms is getting to be too much, and based on
analytics the actual number of users taking advantage of it is minimal.
Furthermore, the majority of traffic is to installation pages.
Therefore we're going to try to collapse back into a single MinIO Object
Storage product, and use simple navigation and on-page selectors to
handle Baremetal vs Kubernetes.
This may also help to eventually stage us to migrate to Hugo + Markdown
---------
Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
Co-authored-by: Rushan <rushenn@minio.io>
Co-authored-by: rushenn <rushenn123@gmail.com>
150 lines
5.3 KiB
ReStructuredText
150 lines
5.3 KiB
ReStructuredText
1. Start MinIO with an FTP and/or SFTP port enabled.
|
|
|
|
.. tab-set::
|
|
|
|
.. tab-item:: FTPS
|
|
:sync: ftps
|
|
|
|
The following example starts MinIO with FTPS enabled.
|
|
|
|
.. code-block:: shell
|
|
:class: copyable
|
|
|
|
minio server http://server{1...4}/disk{1...4} \
|
|
--ftp="address=:8021" \
|
|
--ftp="passive-port-range=30000-40000" \
|
|
--ftp="tls-private-key=path/to/private.key" \
|
|
--ftp="tls-public-cert=path/to/public.crt" \
|
|
...
|
|
|
|
.. note::
|
|
|
|
Omit ``tls-private-key`` and ``tls-public-cert`` to use the MinIO default TLS keys for FTPS.
|
|
For more information, see the :ref:`TLS on MinIO documentation <minio-tls>`.
|
|
|
|
.. tab-item:: SFTP/FTP
|
|
:sync: sftp
|
|
|
|
.. code-block:: shell
|
|
:class: copyable
|
|
|
|
minio server http://server{1...4}/disk{1...4} \
|
|
--ftp="address=:8021" \
|
|
--ftp="passive-port-range=30000-40000" \
|
|
--sftp="address=:8022" \
|
|
--sftp="ssh-private-key=/home/miniouser/.ssh/id_rsa" \
|
|
...
|
|
|
|
See the :mc-cmd:`minio server --ftp` and :mc-cmd:`minio server --sftp` for details on using these flags to start the MinIO service.
|
|
To connect to the an FTP port with TLS (FTPS), pass the ``tls-private-key`` and ``tls-public-cert`` keys and values, as well, unless using the MinIO default TLS keys.
|
|
|
|
The output of the command should return a response that resembles the following:
|
|
|
|
.. code-block:: shell
|
|
|
|
MinIO FTP Server listening on :8021
|
|
MinIO SFTP Server listening on :8022
|
|
|
|
2. Use your preferred FTP client to connect to the MinIO deployment.
|
|
You must connect as a user whose :ref:`policies <minio-policy>` allow access to the desired buckets and objects.
|
|
|
|
The specifics of connecting to the MinIO deployment depend on your FTP client.
|
|
Refer to the documentation for your client.
|
|
|
|
To connect over TLS or through SSH, you must use a client that supports the desired protocol.
|
|
|
|
3. Connect to MinIO
|
|
|
|
.. tab-set::
|
|
|
|
.. tab-item:: SFTP/FTP
|
|
:sync: sftp
|
|
|
|
|
|
The following example connects to an SFTP server, and lists the contents of a bucket named ``runner``.
|
|
|
|
.. code-block:: console
|
|
|
|
> sftp -P 8022 minio@localhost
|
|
minio@localhost's password:
|
|
Connected to localhost.
|
|
sftp> ls runner/
|
|
chunkdocs testdir
|
|
|
|
|
|
.. tab-item:: FTPS
|
|
:sync: ftps
|
|
|
|
The following uses the Linux uses the `FTP CLI client <https://linux.die.net/man/1/ftp>`__ to connect to the MinIO server using ``minio`` credentials to list contents in a bucket named ``runner``
|
|
|
|
.. code-block:: shell
|
|
|
|
> ftp localhost -P 8021
|
|
Connected to localhost.
|
|
220 Welcome to MinIO FTP Server
|
|
Name (localhost:user): minio
|
|
331 User name ok, password required
|
|
Password:
|
|
230 Password ok, continue
|
|
Remote system type is UNIX.
|
|
Using binary mode to transfer files.
|
|
ftp> ls runner/
|
|
229 Entering Extended Passive Mode (|||39155|)
|
|
150 Opening ASCII mode data connection for file list
|
|
drwxrwxrwx 1 nobody nobody 0 Jan 1 00:00 chunkdocs/
|
|
drwxrwxrwx 1 nobody nobody 0 Jan 1 00:00 testdir/
|
|
...
|
|
|
|
|
|
4. Download an Object
|
|
|
|
.. tab-set::
|
|
|
|
.. tab-item:: SFTP/FTP
|
|
:sync: sftp
|
|
|
|
This example lists items in a bucket, then downloads the contents of the bucket.
|
|
|
|
.. code-block:: console
|
|
|
|
> sftp -P 8022 minio@localhost
|
|
minio@localhost's password:
|
|
Connected to localhost.
|
|
sftp> ls runner/
|
|
chunkdocs testdir
|
|
sftp> get runner/chunkdocs/metadata metadata
|
|
Fetching /runner/chunkdocs/metadata to metadata
|
|
metadata 100% 226 16.6KB/s 00:00
|
|
sftp>
|
|
|
|
.. tab-item:: FTPS
|
|
:sync: ftps
|
|
|
|
This example lists items in a bucket, then downloads the contents of the bucket.
|
|
|
|
.. code-block:: console
|
|
|
|
> ftp localhost -P 8021
|
|
Connected to localhost.
|
|
220 Welcome to MinIO FTP Server
|
|
Name (localhost:user): minio
|
|
331 User name ok, password required
|
|
Password:
|
|
230 Password ok, continue
|
|
Remote system type is UNIX.
|
|
Using binary mode to transfer files.ftp> ls runner/chunkdocs/metadata
|
|
229 Entering Extended Passive Mode (|||44269|)
|
|
150 Opening ASCII mode data connection for file list
|
|
-rwxrwxrwx 1 nobody nobody 45 Apr 1 06:13 chunkdocs/metadata
|
|
226 Closing data connection, sent 75 bytes
|
|
ftp> get
|
|
(remote-file) runner/chunkdocs/metadata
|
|
(local-file) test
|
|
local: test remote: runner/chunkdocs/metadata
|
|
229 Entering Extended Passive Mode (|||37785|)
|
|
150 Data transfer starting 45 bytes
|
|
45 3.58 KiB/s
|
|
226 Closing data connection, sent 45 bytes
|
|
45 bytes received in 00:00 (3.55 KiB/s)
|
|
...
|