Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 761 - 770 of 827 for chang (0.03 seconds)

  1. helm-releases/minio-1.0.2.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO 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....
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Tue Aug 24 18:58:05 GMT 2021
    - 13.6K bytes
    - Click Count (0)
  2. cmd/api-errors.go

    		HTTPStatusCode: http.StatusNotFound,
    	},
    	ErrAdminPolicyChangeAlreadyApplied: {
    		Code:           "XMinioAdminPolicyChangeAlreadyApplied",
    		Description:    "The specified policy change is already in effect.",
    		HTTPStatusCode: http.StatusBadRequest,
    	},
    
    	ErrAdminInvalidArgument: {
    		Code:           "XMinioAdminInvalidArgument",
    		Description:    "Invalid arguments specified.",
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Wed Apr 16 07:34:24 GMT 2025
    - 93K bytes
    - Click Count (3)
  3. cmd/testdata/xl-meta-merge.zip

    https://dl.min.io/server/minio/release/windows-amd64/minio.exe ``` Use the following command to run a standalone MinIO server on the Windows host. Replace ``D:\`` with the path to the drive or directory in which you want MinIO to store data. You must change the terminal or powershell directory to the location of the ``minio.exe`` executable, *or* add the path to that directory to the system ``$PATH``: ```sh minio.exe server D:\ ``` The MinIO deployment starts using default root credentials `minioadmin:minioadmin`....
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Fri Mar 08 17:50:48 GMT 2024
    - 30.2K bytes
    - Click Count (0)
  4. helm-releases/minio-1.0.0.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO 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....
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Fri Aug 20 22:30:54 GMT 2021
    - 13.5K bytes
    - Click Count (0)
  5. helm-releases/minio-1.0.1.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO 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....
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Fri Aug 20 22:32:29 GMT 2021
    - 13.5K bytes
    - Click Count (0)
  6. helm-releases/minio-1.0.3.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO 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....
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Tue Aug 24 19:04:07 GMT 2021
    - 13.6K bytes
    - Click Count (0)
  7. helm-releases/minio-1.0.4.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO 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....
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Wed Aug 25 02:12:51 GMT 2021
    - 13.6K bytes
    - Click Count (0)
  8. helm-releases/minio-1.0.5.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO 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....
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Wed Aug 25 19:53:57 GMT 2021
    - 13.6K bytes
    - Click Count (0)
  9. helm-releases/minio-2.0.0.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO 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....
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Thu Aug 26 07:36:46 GMT 2021
    - 13.6K bytes
    - Click Count (0)
  10. doc/asm.html

    and the assembly must confirm this fact by executing the
    pseudo-instruction <code>NO_LOCAL_POINTERS</code>.
    Because stack resizing is implemented by moving the stack,
    the stack pointer may change during any function call:
    even pointers to stack data must not be kept in local variables.
    </p>
    
    <p>
    Assembly functions should always be given Go prototypes,
    Created: Tue Dec 30 11:13:12 GMT 2025
    - Last Modified: Fri Nov 14 19:09:46 GMT 2025
    - 36.5K bytes
    - Click Count (0)
Back to Top