Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 8 of 8 for So (0.13 sec)

  1. docs/metrics/prometheus/README.md

    ```
    
    ##### Node (optional)
    
    Optionally you can also collect per node metrics. This needs to be done on a per server instance.
    The scrape configurations should use all the servers under `targets` so that graphing systems like
    grafana can visualize them for all the nodes
    
    ```yaml
    scrape_configs:
    - job_name: minio-job
      metrics_path: /minio/v2/metrics/node
      scheme: http
      static_configs:
    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)
  2. docs/kms/README.md

    ```
    export MINIO_KMS_AUTO_ENCRYPTION=on
    ```
    
    ### Verify auto-encryption
    
    > Note that auto-encryption only affects requests without S3 encryption headers. So, if a S3 client sends
    > e.g. SSE-C headers, MinIO will encrypt the object with the key sent by the client and won't reach out to
    > the configured KMS.
    
    To verify auto-encryption, use the following `mc` command:
    
    ```
    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)
  3. internal/grid/README.md

    Handlers have a predefined Handler ID. 
    In addition, there can be several *static* subroutes used to differentiate between different handlers of the same ID.
    A subroute on a client must match a subroute on the server. So routes cannot be used for dynamic routing, unlike HTTP.
    
    Handlers should remain backwards compatible. If a breaking API change is required, a new handler ID should be created.
    
    ## Setup & Configuration
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Jan 18 07:03:17 GMT 2024
    - 9.4K bytes
    - Viewed (0)
  4. docs/ftp/README.md

      use basic "readwrite" canned policy to test all the operations before you finalize on what level
      of restrictions are needed for a user.
    
    - No "admin:*" operations are needed for FTP/SFTP access to the bucket(s) and object(s), so you may
      skip them for restrictions.
    
    ## Usage
    
    Start MinIO in a distributed setup, with 'ftp/sftp' enabled.
    
    ```
    minio server http://server{1...4}/disk{1...4}
    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)
  5. docs/bucket/notifications/README.md

    ### Step 1: Ensure minimum requirements are met
    
    MinIO requires Kafka version 0.10 or 0.9. Internally MinIO uses the [Shopify/sarama](https://github.com/Shopify/sarama/) library and so has the same version compatibility as provided by this library.
    
    ### Step 2: Add Kafka endpoint to MinIO
    
    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)
  6. README.md

    ## Upgrading MinIO
    
    Upgrades require zero downtime in MinIO, all upgrades are non-disruptive, all transactions on MinIO are atomic. So upgrading all the servers simultaneously is the recommended way to upgrade MinIO.
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Wed Feb 14 17:51:34 GMT 2024
    - 18.7K bytes
    - Viewed (0)
  7. docs/compression/README.md

    > export MINIO_COMPRESSION_EXTENSIONS="*"
    > export MINIO_COMPRESSION_MIME_TYPES="*"
    > ```
    
    ### 3. Compression + Encryption
    
    Combining encryption and compression is not safe in all setups.
    This is particularly so if the compression ratio of your content reveals information about it.
    See [CRIME TLS](https://en.wikipedia.org/wiki/CRIME) as an example of this.
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Mon Mar 11 11:55:34 GMT 2024
    - 5.1K bytes
    - Viewed (0)
  8. docs/distributed/README.md

    storage by _(newly_added_servers\*m)_ more drives, taking the total count to _(existing_servers\*m)+(newly_added_servers\*m)_ drives. New object upload requests automatically start using the least used cluster. This expansion strategy works endlessly, so you can perpetually expand your clusters as needed.  When you restart, it is immediate and non-disruptive to the applications. Each group of servers in the command-line is called a pool. There are 2 server pools in this example. New objects are placed...
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Jan 18 07:03:17 GMT 2024
    - 8.8K bytes
    - Viewed (0)
Back to top