DIAL Core

    <a href="https://dialx.ai/">
      <img src="https://dialx.ai/logo/dialx_logo.svg" alt="About DIALX">
    </a>

• Overview
• Build
• Run
• Helm Deployment
• Configuration
  • Static settings
  • Storage requirements
  • Dynamic settings
• Claude Code commands
• License

Overview

[!NOTE] HTTP Proxy provides unified API to different chat completion and embedding models and applications. Written in Java 21 and built on top of Eclipse Vert.x.

Read more about the DIAL Core

Build 🏗

DIAL Core has a dependency on GitHub packages of JClouds. Github doesn't provide anonymous access to packages.

That requires to pass credentials GitHub for access to published JClouds packages. See the code snippet below:

repositories {
        maven {
            url = uri("https://maven.pkg.github.com/epam/jclouds")
            credentials {
                username = project.findProperty("gpr.user") ?: System.getenv("GPR_USERNAME")
                password = project.findProperty("gpr.key") ?: System.getenv("GPR_PASSWORD")
            }
        }
        mavenCentral()
    }

[!IMPORTANT] You should set env variables GPR_USERNAME and GPR_PASSWORD to valid values, where GPR_USERNAME - GitHub username and GPR_PASSWORD - GitHub personal access token.

[!IMPORTANT] The access token requires the permission read:packages.

See more details here to generate personal access token in GitHub.

Build the project with Gradle and Java 21:

./gradlew build

Run ▶️

Run the project with Gradle:

./gradlew :server:run

Or run com.epam.aidial.core.server.AiDial class from your favorite IDE.

Helm Deployment

You have the option to deploy the DIAL Core on the Kubernetes cluster by utilizing an umbrella dial Helm chart, which also deploys other DIAL components. Alternatively, you can use dial-core Helm chart to deploy just Core.

[!NOTE] Refer to Examples for guidelines.

In any case, in your Helm values file, it is necessary to provide application's configurations described in the Configuration section.

Configuration ⚙️

• Static settings
• Dynamic settings

Static settings

[!NOTE] Static settings are used on startup and cannot be changed while application is running. Refer to example to view the example configuration file.

Priority order:

1. Environment variables with extra "aidial." prefix. E.g. "aidial.server.port", "aidial.config.files".
2. File specified in "AIDIAL_SETTINGS" environment variable.
3. Default resource file: src/main/resources/aidial.settings.json.

Identity Providers Configurations