Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for Entry (0.13 sec)

  1. docs/bucket/versioning/DESIGN.md

    allowing the unmarshaller's to automatically use the right data structures to parse the subsequent content in the stream.
    
    ### v1.0
    
    | Entry     | Encoding    | Content
    | ----------|-------------|----------------------------------------
    | xlHeader  | [4]byte     | `'X', 'L', '2', ' '`
    | xlVersion | [4]byte     | `'1', ' ', ' ', ' '`
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Sun Jul 17 15:43:14 GMT 2022
    - 5.8K bytes
    - Viewed (1)
  2. docs/sts/wso2.md

    - Open the `<IS_HOME>/repository/conf/identity/identity.xml` file and uncomment the following entry under `<OAuth>` element.
    
    ```
    <IdentityOAuthTokenGenerator>org.wso2.carbon.identity.oauth2.token.JWTTokenIssuer</IdentityOAuthTokenGenerator>
    ```
    
    - Restart the server.
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Sep 29 04:28:45 GMT 2022
    - 8.7K bytes
    - Viewed (0)
  3. docs/federation/lookup/README.md

    This is comma separated list of IP addresses to which buckets created on this MinIO instance will resolve to. For example,
    a bucket `bucket1` created on current MinIO instance will be accessible as `bucket1.domain.com`, and the DNS entry for
    `bucket1.domain.com` will point to IP address set in `MINIO_PUBLIC_IPS`.
    
    - This field is mandatory for standalone and erasure code MinIO server deployments, to enable federated mode.
    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)
  4. docs/metrics/prometheus/alerts.md

    4. Wait for 5 mins (as alert is configured to be firing after 5 mins), and verify that you see an entry in webhook for the alert as well as in Prometheus console as shown below
    
    ```json
    {
      "receiver": "web\\.hook",
      "status": "firing",
      "alerts": [
        {
          "status": "firing",
          "labels": {
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Sun Jan 28 20:53:59 GMT 2024
    - 4.4K bytes
    - Viewed (0)
  5. docs/distributed/DECOMMISSION.md

    - On Operator based MinIO deployments, you need to modify the `tenant.yaml` specification and modify the `pools:` section from two entries to a single entry. After making relevant changes, proceed to execute `kubectl apply -f tenant.yaml`.
    
    > Without a 'Complete' status any 'Active' or 'Draining' pool(s) are not allowed to be removed once configured.
    
    ## NOTE
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Mon Jul 11 14:59:49 GMT 2022
    - 8.3K bytes
    - Viewed (0)
  6. docs/bucket/notifications/README.md

    When the _namespace_ format is used, MinIO synchronizes objects in the bucket with entries in a hash. For each entry, the key is formatted as "bucketName/objectName" for an object that exists in the bucket, and the value is the JSON-encoded event data about the operation that created/replaced the object in MinIO. When objects are updated or deleted, the corresponding entry in the hash is also updated or deleted.
    
    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)
Back to top