- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 186 for instances (0.19 sec)
-
docs/orchestration/docker-compose/docker-compose.yaml
# MINIO_ROOT_PASSWORD: minioadmin healthcheck: test: ["CMD", "mc", "ready", "local"] interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - data1-1:/data1 - data1-2:/data2
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed May 01 02:45:52 GMT 2024 - 1.5K bytes - Viewed (1) -
.github/workflows/multipart/docker-compose-site1.yaml
image: quay.io/minio/minio:${RELEASE} command: server http://site1-minio{1...4}/data{1...2} environment: - MINIO_PROMETHEUS_AUTH_TYPE=public - CI=true # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: site1-minio1: <<: *minio-common hostname: site1-minio1 volumes: - site1-data1-1:/data1
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Sep 30 10:13:56 GMT 2023 - 1.5K bytes - Viewed (0) -
.github/workflows/multipart/docker-compose-site2.yaml
image: quay.io/minio/minio:${RELEASE} command: server http://site2-minio{1...4}/data{1...2} environment: - MINIO_PROMETHEUS_AUTH_TYPE=public - CI=true # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: site2-minio1: <<: *minio-common hostname: site2-minio1 volumes: - site2-data1-1:/data1
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Sep 30 10:13:56 GMT 2023 - 1.5K bytes - Viewed (0) -
.github/workflows/mint/minio-pools.yaml
healthcheck: test: ["CMD", "mc", "ready", "local"] interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - pdata1-1:/pdata1
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Nov 03 21:18:18 GMT 2023 - 2.3K bytes - Viewed (0) -
internal/config/api/help.go
Optional: true, Type: "csv", }, config.HelpKV{ Key: apiRemoteTransportDeadline, Description: `set the deadline for API requests on remote transports while proxying between federated instances e.g. "2h"` + defaultHelpPostfix(apiRemoteTransportDeadline), Optional: true, Type: "duration", }, config.HelpKV{ Key: apiListQuorum,
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Mar 15 01:07:19 GMT 2024 - 4.7K bytes - Viewed (0) -
docs/metrics/prometheus/README.md
- MinIO exports Prometheus compatible data by default as an authorized endpoint at `/minio/v2/metrics/cluster`.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 12 15:49:30 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/kms/README.md
```sh export MINIO_ROOT_USER=minio export MINIO_ROOT_PASSWORD=minio123 minio server ~/export ``` > The KES instance at `https://play.min.io:7373` is meant to experiment and provides a way to get started quickly. > Note that anyone can access or delete master keys at `https://play.min.io:7373`. You should run your own KES > instance in production. ## Configuration Guides A typical MinIO deployment that uses a KMS for SSE-S3 looks like this:
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/config/README.md
cors_allow_origin (csv) set comma separated list of origins allowed for CORS requests (default: '*') remote_transport_deadline (duration) set the deadline for API requests on remote transports while proxying between federated instances e.g. "2h" (default: '2h') list_quorum (string) set the acceptable quorum expected for list operations e.g. "optimal", "reduced", "disk", "strict" (default: 'strict')
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Sep 11 21:48:54 GMT 2023 - 17.7K bytes - Viewed (0) -
code_of_conduct.md
professional setting ## Our Responsibilities Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior, in compliance with the licensing terms applying to the Project developments. Project maintainers have the right and responsibility to remove, edit, or
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Jan 20 18:38:58 GMT 2020 - 3.5K bytes - Viewed (0) -
internal/jwt/parser.go
// Expects key type of []byte for both signing and validation type SigningMethodHMAC struct { Name string Hash crypto.Hash HasherPool sync.Pool } // Specific instances for HS256, HS384, HS512 var ( SigningMethodHS256 *SigningMethodHMAC SigningMethodHS384 *SigningMethodHMAC SigningMethodHS512 *SigningMethodHMAC ) const base64BufferSize = 64 * humanize.KiByte var (
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue May 09 07:53:08 GMT 2023 - 13.9K bytes - Viewed (0)