Skip to main content
The top-level keys are models (required, at least one entry), deployment, fileSources and promotion. Unknown top-level keys are rejected. Provider requirements and cross-field validation still apply to optional fields. Start with Configuration for examples.

Deployment

Transfer limits use bytes. Parsing selections and allowedProviders contain model IDs.

Language models

Assign model roles explicitly. The first entry for a role is its default. Credential fields may reference environment variables.

OCR models

Use kind: ocr and the ocr role. Credentials and connection requirements depend on the provider.

Promotion

Use the same repositories and environment order across installations; only environment differs. Each environment names the repository it is kept in. Artifact storage must be shared unless it is git.

File sources

fileSources maps connection names to provider settings. Each accepts type and enabled (default true). Studio lists these connections with a Config badge and keeps them read-only. When a name is defined here and in Studio, the entry here wins even if it is disabled or invalid, and the Studio connection is marked Overridden. Every supported type (S3, Azure Blob, GPFS/GFR, VUB Document Archive) is available on single-tenant deployments without an extra switch. FILE_SOURCE_INTEGRATIONS is no longer read; remove it from app and worker.

GPFS file registry

Run reference: stackId/fileId. Set TLS verification on for production connections.

Amazon S3

Run reference: bucket/key. Set TLS verification on for production connections.

Azure Blob Storage

Run reference: container/blobName. Set TLS verification on for production connections.