- Sort Score
- Num 10 results
- Language All
Results 361 - 370 of 549 for wantSz (0.05 seconds)
The search processing time has exceeded the limit. The displayed results may be partial.
-
helm-releases/minio-5.0.14.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 Sep 30 20:46:10 GMT 2023 - 20.6K bytes - Click Count (0) -
helm-releases/minio-5.0.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: Mon Dec 19 08:53:02 GMT 2022 - 20.3K bytes - Click Count (0) -
helm-releases/minio-5.0.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 23 20:29:40 GMT 2022 - 20.3K bytes - Click Count (0) -
helm-releases/minio-5.0.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: Fri Feb 03 20:54:02 GMT 2023 - 20.3K bytes - Click Count (0) -
helm-releases/minio-4.0.15.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 Sep 21 11:07:01 GMT 2022 - 20K bytes - Click Count (0) -
helm-releases/minio-4.0.11.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 Aug 07 05:41:47 GMT 2022 - 19.2K bytes - Click Count (0) -
helm-releases/minio-4.0.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: Mon May 09 04:25:47 GMT 2022 - 18K bytes - Click Count (0) -
helm-releases/minio-4.0.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: Fri Jul 08 06:16:22 GMT 2022 - 18K bytes - Click Count (0) -
helm-releases/minio-5.0.0.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 Oct 25 10:20:22 GMT 2022 - 19.8K bytes - Click Count (0) -
docs/en/docs/deployment/manually.md
These examples run the server program (e.g Uvicorn), starting **a single process**, listening on all the IPs (`0.0.0.0`) on a predefined port (e.g. `80`). This is the basic idea. But you will probably want to take care of some additional things, like: * Security - HTTPS * Running on startup * Restarts * Replication (the number of processes running) * Memory * Previous steps before starting
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Oct 11 17:48:49 GMT 2025 - 6.9K bytes - Click Count (0)