- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 271 for configurations (0.21 sec)
-
docs/orchestration/docker-compose/docker-compose.yaml
version: '3.7' # Settings and configurations that are common for all containers x-minio-common: &minio-common image: quay.io/minio/minio:RELEASE.2024-05-01T01-11-10Z command: server --console-address ":9001" http://minio{1...4}/data{1...2} expose: - "9000" - "9001" # environment: # MINIO_ROOT_USER: minioadmin # MINIO_ROOT_PASSWORD: minioadmin healthcheck: test: ["CMD", "mc", "ready", "local"] interval: 5s
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
version: '3.7' # Settings and configurations that are common for all containers x-minio-common: &minio-common 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:
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
version: '3.7' # Settings and configurations that are common for all containers x-minio-common: &minio-common 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:
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) -
internal/config/identity/openid/openid.go
return val } // In the past, when only one openID provider was allowed, there // was no `enable` parameter - the configuration is turned off // by clearing the values. With multiple providers, we support // individually enabling/disabling provider configurations. If // the enable parameter's value is non-empty, we use that // setting, otherwise we treat it as enabled if some important
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Nov 16 04:42:31 GMT 2023 - 16.5K bytes - Viewed (0) -
.github/workflows/mint/minio-pools.yaml
version: '3.7' # Settings and configurations that are common for all containers x-minio-common: &minio-common image: quay.io/minio/minio:${JOB_NAME} command: server --console-address ":9001" http://minio{1...4}/pdata{1...2} http://minio{5...8}/pdata{1...2} expose: - "9000" - "9001" environment: MINIO_CI_CD: "on" MINIO_ROOT_USER: "minio" MINIO_ROOT_PASSWORD: "minio123"
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) -
docs/metrics/prometheus/README.md
scheme: http static_configs: - targets: ['localhost:9000'] ``` ##### Node (optional) Optionally you can also collect per node metrics. This needs to be done on a per server instance. The scrape configurations should use all the servers under `targets` so that graphing systems like grafana can visualize them for all the nodes ```yaml scrape_configs: - job_name: minio-job metrics_path: /minio/v2/metrics/node
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) -
cmd/api-errors.go
HTTPStatusCode: http.StatusBadRequest, }, ErrOverlappingConfigs: { Code: "InvalidArgument", Description: "Configurations overlap. Configurations on the same bucket cannot share a common event type.", HTTPStatusCode: http.StatusBadRequest, }, ErrUnsupportedNotification: { Code: "UnsupportedNotification",
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun May 05 16:56:21 GMT 2024 - 91.4K bytes - Viewed (7) -
cmd/iam.go
// are multiple openid provider configurations with the same ID // provider. We lookup the provider associated with some one of // the roleARNs to check if the user still exists. If they don't // we can safely remove credentials for this parent user // associated with any of the provider configurations. // // If there is no roleARN mapped to the user, the user may be
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 25 21:28:16 GMT 2024 - 71.1K bytes - Viewed (1) -
docs/multi-tenancy/README.md
This topic provides commands to set up different configurations of hosts, nodes, and drives. The examples provided here can be used as a starting point for other configurations. 1. [Standalone Deployment](#standalone-deployment) 2. [Distributed Deployment](#distributed-deployment) 3. [Cloud Scale Deployment](#cloud-scale-deployment)
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 3K bytes - Viewed (0) -
.github/workflows/mint/minio-erasure.yaml
version: '3.7' # Settings and configurations that are common for all containers x-minio-common: &minio-common image: quay.io/minio/minio:${JOB_NAME} command: server --console-address ":9001" edata{1...4} expose: - "9000" - "9001" environment: MINIO_CI_CD: "on" MINIO_ROOT_USER: "minio" MINIO_ROOT_PASSWORD: "minio123" MINIO_KMS_SECRET_KEY: "my-minio-key:OSMM+vkKUTCvQs9YL/CVMIMt43HFhkUpqJxTmGl6rYw=" healthcheck:
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Nov 03 21:18:18 GMT 2023 - 1.2K bytes - Viewed (0)