Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for Sentry (0.18 sec)

  1. 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 Apr 28 19:28:10 GMT 2024
    - Last Modified: Thu Sep 29 04:28:45 GMT 2022
    - 4K bytes
    - Viewed (0)
  2. 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 Apr 28 19:28:10 GMT 2024
    - Last Modified: Thu Jan 18 07:03:17 GMT 2024
    - 84K bytes
    - Viewed (2)
  3. .teamcity/README.md

    ## Open & import the project
    
    In your IDEA, `File` - `Open`, select `.teamcity/pom.xml`, `import as project`, and you'll have a Maven project.
    
    ## Project structure
    
    Mostly a standard Maven project structure. The entry point `settings.kts` defines the TeamCity project.
    
    There are 3 subprojects in the TeamCity project hierarchy: `Check` for Gradle builds, `Promotion` for releasing Gradle versions, `Util` for miscellaneous utilities.
    
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Wed Mar 06 23:02:25 GMT 2024
    - 4K bytes
    - Viewed (0)
  4. ci/official/requirements_updater/README.md

    3) In the `BUILD.bazel` file, add a load statement for the new version, e.g.
    
       ```
          load("@python//3.11:defs.bzl",
               compile_pip_requirements_3_11 = "compile_pip_requirements")
       ```
    
       Add a new entry for the loaded `compile_pip_requirements`, e.g.
    
       ```
          compile_pip_requirements_3_11(
              name = "requirements_3_11",
              extra_args = ["--allow-unsafe"],
              requirements_in = "requirements.in",
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Tue Jan 23 02:14:00 GMT 2024
    - 3.9K bytes
    - Viewed (0)
Back to top