- Sort Score
- Num 10 results
- Language All
Results 361 - 370 of 440 for Want (0.02 seconds)
-
helm-releases/minio-3.3.2.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Dec 11 17:26:01 GMT 2021 - 14.6K bytes - Click Count (0) -
helm-releases/minio-3.3.4.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Dec 11 17:59:34 GMT 2021 - 14.6K bytes - Click Count (0) -
helm-releases/minio-3.4.2.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Dec 21 02:58:25 GMT 2021 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.4.4.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Dec 31 04:21:24 GMT 2021 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.4.5.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Jan 05 19:32:55 GMT 2022 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.5.3.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Feb 13 23:43:44 GMT 2022 - 15.4K bytes - Click Count (0) -
cmd/bucket-policy-handlers_test.go
errs++ mu.Unlock() return } mu.Lock() ok++ mu.Unlock() }() } close(start) wg.Wait() if ok != 1 { t.Fatalf("want 1 ok, got %d", ok) } if errs != n-1 { t.Fatalf("want %d errors, got %d", n-1, errs) } } // Wrapper for calling Put Bucket Policy HTTP handler tests for both Erasure multiple disks and single node setup.
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Aug 29 02:39:48 GMT 2025 - 32.9K bytes - Click Count (0) -
docs/en/docs/tutorial/security/first-steps.md
Let's imagine that you have your **backend** API in some domain. And you have a **frontend** in another domain or in a different path of the same domain (or in a mobile application). And you want to have a way for the frontend to authenticate with the backend, using a **username** and **password**. We can use **OAuth2** to build that with **FastAPI**.
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sun Aug 31 09:15:41 GMT 2025 - 8.4K bytes - Click Count (0) -
docs/en/docs/_llm-test.md
/// note The LLM will probably translate this wrong. Interesting is only if it keeps the fixed translation when retranslating. /// //// //// tab | Info The prompt designer may choose if they want to convert neutral quotes to typographic quotes. It is okay to leave them as is. See for example section `### Quotes` in `docs/de/llm-prompt.md`. //// ## Quotes in code snippets { #quotes-in-code-snippets }Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Thu Dec 11 14:48:47 GMT 2025 - 11.4K bytes - Click Count (0) -
docs/en/docs/tutorial/security/oauth2-jwt.md
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Mon Sep 29 02:57:38 GMT 2025 - 10.6K bytes - Click Count (0)