- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 24 for instance (0.17 sec)
-
docs/federation/lookup/README.md
and `bucket2.domain.com`. #### MINIO_PUBLIC_IPS This is comma separated list of IP addresses to which buckets created on this MinIO instance will resolve to. For example, a bucket `bucket1` created on current MinIO instance will be accessible as `bucket1.domain.com`, and the DNS entry for `bucket1.domain.com` will point to IP address set in `MINIO_PUBLIC_IPS`.
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 4K bytes - Viewed (0) -
internal/grid/README.md
instance := grid.NewStream[*Payload, *Req, *Resp](h, newPayload, newReq, newResp) // Tweakable options instance.WithPayload = true // default true when newPayload != nil instance.OutCapacity = 1 // default instance.InCapacity = 1 // default true when newReq != nil // Register the handler on the manager instance.Register(manager, handler, "asubroute")
Plain Text - Registered: Sun Apr 21 19:28:08 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 9.4K bytes - Viewed (0) -
docs/chroot/README.md
Endpoint: http://192.168.1.92:9000 http://65.19.167.92:9000 AccessKey: MVPSPBW4NP2CMV1W3TXD SecretKey: X3RKxEeFOI8InuNWoPsbG+XEVoaJVCqbvxe+PTOa ... ... ``` Instance is now accessible on the host at port 9000, proceed to access the Web browser at <http://127.0.0.1:9000/> ## Explore Further
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 1.7K bytes - Viewed (0) -
docs/bucket/notifications/README.md
``` Note that, you can add as many MySQL server endpoint configurations as needed by providing an identifier (like "myinstance" in the example above) for each MySQL instance desired. Restart the MinIO server to put the changes into effect. The server will print a line like `SQS ARNs: arn:minio:sqs::myinstance:mysql` at start-up, if there are no errors. ### Step 3: Enable MySQL bucket notification using MinIO client
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 84K bytes - Viewed (2) -
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 Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 7.1K bytes - Viewed (0) -
ci/official/wheel_test/README.md
the local wheel file specified in the `requirements_lock_<python_version>.txt`. Packages are imported one by one in alphabetical order during runtime. The test doesn't identify package's order-dependent issues; for instance, importing "tf.foo" followed by "tf.bar" won't reveal that "tf.bar" depends on "tf.foo" being imported first. The `_api/v2/api_packages.txt` file is generated during the TensorFlow API v2
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Aug 31 18:17:57 GMT 2023 - 3.3K bytes - Viewed (0) -
okhttp-tls/README.md
``` [`HandshakeCertificates`][handshake_certificates] keeps the certificates for a TLS handshake. Use its [builder][handshake_certificates_builder] to define which certificates the HTTPS server returns to its clients. The returned instance can create an `SSLSocketFactory` that implements this policy: ```java HandshakeCertificates serverCertificates = new HandshakeCertificates.Builder() .heldCertificate(localhostCertificate) .build();
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Sun Dec 17 15:34:10 GMT 2023 - 9.1K bytes - Viewed (1) -
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
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Fri Apr 12 15:49:30 GMT 2024 - 7.1K bytes - Viewed (0) -
helm/minio/README.md
For instance, given that TLS is enabled and you need to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ```
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Wed Jan 24 07:27:57 GMT 2024 - 10.9K bytes - Viewed (0) -
docs/metrics/README.md
## Prometheus Probe MinIO allows reading metrics for the entire cluster from any single node. This allows for metrics collection for a MinIO instance across all servers. Thus, metrics collection for instances behind a load balancer can be done without any knowledge of the individual node addresses. The cluster wide metrics can be read at `<Address for MinIO Service>/minio/v2/metrics/cluster`.
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Feb 29 18:35:20 GMT 2024 - 1.9K bytes - Viewed (0)