- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 17 for name (0.17 sec)
-
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` - `jwt:profile` - `jwt:picture` - `jwt:website` - `jwt:email` - `jwt:gender` - `jwt:birthdate`
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/batch-jobs/README.md
createdBefore: "date" # match objects created before "date" ## NOTE: tags are not supported when "source" is remote. # tags: # - key: "name" # value: "pick*" # match objects with tag 'name', with all values starting with 'pick' ## NOTE: metadata filter not supported when "source" is non MinIO. # metadata: # - key: "content-type"
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Oct 06 06:00:43 GMT 2022 - 4.8K bytes - Viewed (0) -
docs/bucket/lifecycle/README.md
``` mc admin tier add azure source AZURETIER --endpoint https://blob.core.windows.net --access-key AZURE_ACCOUNT_NAME --secret-key AZURE_ACCOUNT_KEY --bucket azurebucket --prefix testprefix1/ ``` > The admin user running this command needs the "admin:SetTier" and "admin:ListTier" permissions if not running as root.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Aug 26 07:33:25 GMT 2023 - 9K bytes - Viewed (1) -
docs/tls/kubernetes/README.md
path: CAs/public.crt ``` Note that the `secretName` should be same as the secret name created in previous step. Then add the below section under `spec.containers[].volumeMounts[]` ```yaml volumeMounts: - name: secret-volume 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
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/metrics/prometheus/README.md
##### Cluster ```yaml scrape_configs: - job_name: minio-job bearer_token: <secret> metrics_path: /minio/v2/metrics/cluster scheme: http static_configs: - targets: ['localhost:9000'] ``` ##### Bucket centric ```yaml - job_name: minio-job-bucket bearer_token: <secret> metrics_path: /minio/v2/metrics/bucket scheme: http
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/docker/README.md
docker run \ -p 9000:9000 \ -p 9001:9001 \ --name minio1 \ -e "MINIO_ROOT_USER=AKIAIOSFODNN7EXAMPLE" \ -e "MINIO_ROOT_PASSWORD=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY" \ -v /mnt/data:/data \ quay.io/minio/minio server /data --console-address ":9001" ``` #### Windows (custom access and secret keys) ```powershell docker run \ -p 9000:9000 \ -p 9001:9001 \ --name minio1 \
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/kms/README.md
``` ### 2. Set the MinIO-KES configuration ```sh export MINIO_KMS_KES_ENDPOINT=https://play.min.io:7373 export MINIO_KMS_KES_KEY_FILE=root.key export MINIO_KMS_KES_CERT_FILE=root.cert export MINIO_KMS_KES_KEY_NAME=my-minio-key ``` ### 3. Start the MinIO Server ```sh export MINIO_ROOT_USER=minio export MINIO_ROOT_PASSWORD=minio123 minio server ~/export ```
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/ftp/README.md
... ... ``` Following example shows connecting via ftp client using `minioadmin` credentials, and list a bucket named `runner`: ``` ftp localhost -P 8021 Connected to localhost. 220 Welcome to MinIO FTP Server Name (localhost:user): minioadmin 331 User name ok, password required Password: 230 Password ok, continue Remote system type is UNIX. Using binary mode to transfer files. ftp> ls runner/
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Apr 30 15:15:45 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/erasure/README.md
```sh minio server /data{1...12} ``` Example: Start MinIO server in a 8 drives setup, using MinIO Docker image. ```sh podman run \ -p 9000:9000 \ -p 9001:9001 \ --name minio \ -v /mnt/data1:/data1 \ -v /mnt/data2:/data2 \ -v /mnt/data3:/data3 \ -v /mnt/data4:/data4 \ -v /mnt/data5:/data5 \ -v /mnt/data6:/data6 \ -v /mnt/data7:/data7 \ -v /mnt/data8:/data8 \
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 4.1K bytes - Viewed (0) -
docs/federation/lookup/README.md
be same across the federated deployment, i.e. all the MinIO instances within a federated deployment should use same etcd back-end. #### 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
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)