- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 101 for using (0.58 sec)
-
internal/grid/README.md
* Large payloads. Only a single connection is ever made between two servers. Likely this means that this connection will not be able to saturate network bandwidth. Therefore, using this for large payloads will likely be slower than using a separate connection, and other connections will be blocked while the large payload is being sent. ## Handlers & Routes Handlers have a predefined Handler ID.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 9.4K bytes - Viewed (0) -
docs/tls/kubernetes/README.md
``` Cross check if the secret is created successfully using ```sh kubectl get secrets ``` You should see a secret named `tls-ssl-minio`. ## 3. Update deployment yaml file Whether you are planning to use Kubernetes StatefulSet or Kubernetes Deployment, the steps remain the same. If you're using certificates provided by a CA, add the below section in your yaml file under `spec.volumes[]`
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) -
docs/docker/README.md
#### GNU/Linux and macOS (regular user) On Linux and macOS you can use `--user` to run the container as regular user. > NOTE: make sure --user has write permission to *${HOME}/data* prior to using `--user`. ```sh mkdir -p ${HOME}/data docker run \ -p 9000:9000 \ -p 9001:9001 \ --user $(id -u):$(id -g) \ --name minio1 \ -e "MINIO_ROOT_USER=AKIAIOSFODNN7EXAMPLE" \
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 8.2K bytes - Viewed (0) -
docs/bucket/retention/README.md
``` ### Set object lock PutObject API allows setting per object retention mode and retention duration using `x-amz-object-lock-mode` and `x-amz-object-lock-retain-until-date` headers. This takes precedence over any bucket object lock configuration w.r.t retention. ```sh
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 3.9K bytes - Viewed (0) -
docs/kms/README.md
## Auto Encryption Auto-Encryption is useful when MinIO administrator wants to ensure that all data stored on MinIO is encrypted at rest. ### Using `mc encrypt` (recommended) MinIO automatically encrypts all objects on buckets if KMS is successfully configured and bucket encryption configuration is enabled for each bucket as shown below: ```
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) -
internal/http/server.go
w.Write([]byte(http.ErrServerClosed.Error())) return } atomic.AddInt32(&srv.requestCount, 1) defer atomic.AddInt32(&srv.requestCount, -1) // Handle request using passed handler. handler.ServeHTTP(w, r) }) srv.listenerMutex.Lock() srv.Handler = wrappedHandler srv.listener = listener srv.listenerMutex.Unlock() var l net.Listener = listener
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Feb 09 21:25:16 GMT 2024 - 7.7K bytes - Viewed (0) -
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
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
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) -
docs/metrics/prometheus/README.md
## Prerequisites To get started with MinIO, refer [MinIO QuickStart Document](https://min.io/docs/minio/linux/index.html#quickstart-for-linux). Follow below steps to get started with MinIO monitoring using Prometheus. ### 1. Download Prometheus [Download the latest release](https://prometheus.io/download) of Prometheus for your platform, then extract it ```sh tar xvfz prometheus-*.tar.gz cd prometheus-* ```
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)