Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for Top (0.14 sec)

  1. README.md

        See the License for the specific language governing permissions and
        limitations under the License.
     -->
    
    # Apache Lucene and Solr have separate repositories now!
    
    Solr has become a top-level Apache project and main line 
    development for Lucene and Solr is happening in each 
    project's git repository now:
    
    - Lucene: <https://gitbox.apache.org/repos/asf/lucene.git>
    Plain Text
    - Registered: Wed May 08 00:11:12 GMT 2024
    - Last Modified: Wed Mar 10 10:02:23 GMT 2021
    - 1.5K bytes
    - Viewed (0)
  2. docs/federation/lookup/README.md

    be same across the federated deployment, i.e. all the MinIO instances within a federated deployment should use same
    etcd back-end.
    
    #### MINIO_DOMAIN
    
    This is the top level domain name used for the federated setup. This domain name should ideally resolve to a load-balancer
    running in front of all the federated MinIO instances. The domain name is used to create sub domain entries to etcd. For
    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)
  3. manifests/charts/README.md

    certificate provisioning tool, or use components that are centrally managed and running in a different cluster.
    
    This is a work in progress - building on top of the multi-cluster installer.
    
    As an extreme, the goal is to be possible to run Istio workloads in a cluster without installing any Istio component
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Wed Feb 07 17:53:24 GMT 2024
    - 6.7K bytes
    - Viewed (0)
  4. ci/official/README.md

    ### Brief System Overview
    
    The top-level scripts and utility scripts should be fairly well-documented. Here
    is a brief explanation of how they tie together:
    
    1.  `envs/*` are lists of variables made with bash syntax. A user must set a
        `TFCI` env param pointing to a list of `env` files.
    2.  `utilities/setup.sh`, initialized by all top-level scripts, reads and sets
        values from those `TFCI` paths.
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Thu Feb 01 03:21:19 GMT 2024
    - 8K bytes
    - Viewed (0)
Back to top