- Sort Score
- Result 10 results
- Languages All
Results 1 - 9 of 9 for qsub (0.13 sec)
-
docs/tls/kubernetes/README.md
mountPath: /<user-running-minio>/.minio/certs ``` Here the name of `volumeMount` should match the name of `volume` created previously. Also `mountPath` must be set to the path of the MinIO server's config sub-directory that is used to store certificates. By default, the location is `/<user-running-minio>/.minio/certs`.
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/config/README.md
``` This behavior is consistent across all keys; each key self-documents itself with valid examples. ## Dynamic systems without restarting server The following sub-systems are dynamic i.e., configuration parameters for each sub-systems can be changed while the server is running without any restarts. ``` api manage global HTTP API call specific features, such as throttling, authentication types, etc.
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) -
docs/iam/identity-management-plugin.md
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri May 27 00:58:09 GMT 2022 - 4.2K bytes - Viewed (0) -
docs/distributed/CONFIG.md
> NOTE: MinIO environmental variables still take precedence over the `config.yaml` file, however `config.yaml` is preferred over MinIO internal config KV settings via `mc admin config set alias/ <sub-system>`. ### TODO In subsequent releases we are planning to extend this to provide things like - Reload() of MinIO server arguments without fully restarting the process.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri May 03 15:54:03 GMT 2024 - 4.2K bytes - Viewed (0) -
docs/multi-user/README.md
- `jwt:sub` - `jwt:iss` - `jwt:aud` - `jwt:jti` - `jwt:upn` - `jwt:name` - `jwt:groups` - `jwt:given_name` - `jwt:family_name` - `jwt:middle_name` - `jwt:nickname` - `jwt:preferred_username`
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Mar 21 06:38:06 GMT 2023 - 8K bytes - Viewed (0) -
docs/metrics/v3.md
## Request, System and Cluster Metrics At a high level metrics are grouped into three categories, listed in the following sub-sections. The path in each of the tables is relative to the top-level endpoint. ### Request metrics These are metrics about requests served by the (current) node.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu May 02 17:37:57 GMT 2024 - 28.5K bytes - Viewed (0) -
docs/federation/lookup/README.md
#### MINIO_DOMAIN This is the top level domain name used for the federated setup. This domain name should ideally resolve to a load-balancer running in front of all the federated MinIO instances. The domain name is used to create sub domain entries to etcd. For example, if the domain is set to `domain.com`, the buckets `bucket1`, `bucket2` will be accessible as `bucket1.domain.com` and `bucket2.domain.com`. #### MINIO_PUBLIC_IPS
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 4K bytes - Viewed (0) -
docs/bucket/notifications/README.md
| `s3:BucketRemoved` |
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 84K bytes - Viewed (2) -
docs/distributed/README.md
- MinIO distributed mode requires **fresh directories**. If required, the drives can be shared with other applications. You can do this by using a sub-directory exclusive to MinIO. For example, if you have mounted your volume under `/export`, pass `/export/data` as arguments to MinIO server.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 8.8K bytes - Viewed (0)