* in the Gradle build.
 *
 * Each project may require a set of "target runtimes" that it must be able to run on.
 * Each target runtime reflects a runtime environment where code is executed. For one
 * project to be able to run in a given runtime, all of its dependencies must also
 * support running in that runtime.
 *

* the Advanced User Guide: das Handbuch für fortgeschrittene Benutzer
* the SQLModel docs: die SQLModel-Dokumentation
* the docs: die Dokumentation (use singular case)
* the env var: die Umgebungsvariable
* the `PATH` environment variable: die `PATH`-Umgebungsvariable
* the `PATH`: der `PATH`
* the `requirements.txt`: die `requirements.txt`
* the API Router: der API-Router
* the Authorization-Header: der Autorisierungsheader

  // Distributed runtime related functions.
  //===--------------------------------------------------------------------===//
#if !defined(IS_MOBILE_PLATFORM)
  // Set up a multi-client distributed execution environment. Must be called on
  // all tasks in the cluster.
  // This call internally coordinates with other tasks to initialize the eager
  // context and TF server for multi-client execution.

MinIO supports two authentication modes for Prometheus either `jwt` or `public`, by default MinIO runs in `jwt` mode. To allow public access without authentication for prometheus metrics set environment as follows.

```
export MINIO_PROMETHEUS_AUTH_TYPE="public"
minio server ~/test
```

### 3. Configuring Prometheus

#### 3.1 Authenticated Prometheus config

  }

  /*
   * Under Android, MyError propagates up and fails the test?
   *
   * TODO(b/218700094): Does this matter to prod users, or is it just a feature of our testing
   * environment? If the latter, maybe write a custom Executor that avoids failing the test when it
   * sees an Error?
   */
  @AndroidIncompatible
  public void testTaskThrowsError() throws Exception {

                  <project path="$PROJECT_DIR$/build-logic-settings" />
                  <project path="$PROJECT_DIR$/build-logic-settings/architecture-docs" />
                  <project path="$PROJECT_DIR$/build-logic-settings/build-environment" />
                  <project path="$PROJECT_DIR$/build-logic-settings/configuration-cache-compatibility" />
                  <project path="$PROJECT_DIR$/build-logic-settings/default-settings-plugins" />

          show_symbol_type_toc: true
nav:
- FastAPI: index.md
- features.md
- Learn:
  - learn/index.md
  - python-types.md
  - async.md
  - environment-variables.md
  - virtual-environments.md
  - Tutorial - User Guide:
    - tutorial/index.md
    - tutorial/first-steps.md
    - tutorial/path-params.md
    - tutorial/query-params.md
    - tutorial/body.md

        </field>
      </fields>
    </class>
    <class>
      <name>Activation</name>
      <version>1.0.0</version>
      <description><![CDATA[
        The conditions within the build runtime environment which will trigger
        the automatic inclusion of the parent build profile.
      ]]></description>
      <fields>
        <field>
          <name>activeByDefault</name>
          <version>1.0.0</version>

![GitHub Release](https://img.shields.io/github/v/release/codelibs/fess)

## 개요

Fess는 매우 강력하고 쉽게 배포 가능한 엔터프라이즈 검색 서버입니다. 자바 런타임 환경(Java Runtime Environment)을 실행할 수 있는 모든 플랫폼에서 Fess를 빠르게 설치하고 실행할 수 있습니다. Fess는 [Apache License 2.0](LICENSE)에 따라 제공됩니다.

    }

    @Test
    public void test_getAppType() {
        // Test default empty when no env var is set
        String originalAppType = System.getenv("FESS_APP_TYPE");

        // Since we can't modify environment variables directly,
        // we test the current behavior
        String appType = ResourceUtil.getAppType();
        assertNotNull(appType);
        // appType should be either empty string or the actual env value