Configuration

RAT is configured through a combination of a YAML configuration file (rat.yaml), environment variables, and Docker Compose settings. This page covers every configuration option across all services.

rat.yaml

The rat.yaml file is the primary configuration file for the ratd platform service. It defines plugin configurations, feature flags, and platform-level settings. The file location is controlled by the RAT_CONFIG environment variable (default: rat.yaml in the working directory).

# RAT Platform Configuration
# This file configures plugins and platform behavior.
 
# Plugin configuration — Pro Edition only
plugins: []
  # - name: auth-keycloak
  #   path: /plugins/auth-keycloak
  #   config:
  #     issuer_url: https://keycloak.example.com/realms/rat
  #     client_id: rat-platform
  #     audience: rat-api
 
  # - name: acl
  #   path: /plugins/acl
  #   config:
  #     default_policy: deny
  #     admin_users:
  #       - admin@example.com

Plugin Configuration Fields

Each plugin entry in the plugins array supports these fields:

Path Resolution

Paths in rat.yaml are resolved relative to the rat.yaml file location. If RAT_CONFIG=/etc/rat/rat.yaml and a plugin path is ./plugins/auth, it resolves to /etc/rat/plugins/auth.

Environment Variables

RAT services are configured primarily through environment variables. Each service has its own set of variables. In Docker Compose, these are set in the environment section of each service.

ratd (Go Platform)

The ratd service is the central API server, scheduler, and plugin host.

Server

Authentication

Database

S3 (MinIO)

Service Discovery

Scheduler

TLS

runner (Python Pipeline Executor)

The runner service executes pipelines, writes to Iceberg, and runs quality tests.

S3 (MinIO)

DuckDB

Nessie

gRPC

Execution

ratq (Python Query Service)

The ratq service handles interactive DuckDB queries (read-only) and schema introspection.

S3 (MinIO)

Same as the runner service:

DuckDB

Nessie

gRPC

portal (Next.js Web IDE)

The portal is the web-based user interface for RAT.

Docker Compose Configuration

The default Docker Compose file is located at infra/docker-compose.yml. It defines all 7 services plus the minio-init bootstrap container.

Shared Configuration Anchors

The compose file uses YAML anchors to avoid repeating S3 credentials:

x-s3-credentials: &s3-credentials
  S3_ENDPOINT: minio:9000
  S3_ACCESS_KEY: ${S3_ACCESS_KEY:-minioadmin}
  S3_SECRET_KEY: ${S3_SECRET_KEY:-minioadmin}
  S3_BUCKET: rat
  S3_USE_SSL: "false"
  S3_REGION: us-east-1
 
x-logging: &default-logging
  driver: json-file
  options:
    max-size: "10m"
    max-file: "3"

Overriding Defaults

Environment variables in docker-compose.yml use the ${VAR:-default} syntax. You can override them in three ways:

# Export variables before running compose
export S3_ACCESS_KEY=my-production-key
export S3_SECRET_KEY=my-production-secret
export POSTGRES_USER=ratprod
export POSTGRES_PASSWORD=strong-password-here
make up

S3_ACCESS_KEY=my-production-key
S3_SECRET_KEY=my-production-secret
POSTGRES_USER=ratprod
POSTGRES_PASSWORD=strong-password-here

services:
  ratd:
    environment:
      RATE_LIMIT: "0"  # disable rate limiting for local dev
      CORS_ORIGINS: "http://localhost:3000,http://localhost:3001"

Resource Limits

Each service has CPU and memory limits defined in the compose file:

Networks

Volumes

Default Values Summary

Here is a quick reference of all default values across the platform: