DIAL Admin configuration
DIAL Admin is configured in three places: the Admin Frontend's environment variables, DIAL Core's static settings, and, when it is deployed, the optional Admin Backend. This page maps each setting to its place and compares the two setups. It is for platform engineers who add DIAL Admin to a DIAL deployment.
Where each setting lives
| Place | What it sets | Reference |
|---|---|---|
| Admin Frontend environment variables | The DIAL Core URL, sign-in, the optional service URLs and switches, appearance, import limits, and telemetry | Admin Frontend |
| DIAL Core static settings | Who is an administrator (access.admin.rules) and which identity providers' tokens Core accepts | Access, Identity providers |
| Admin Backend environment variables | The backend's database, configuration export to DIAL Core, token validation, and metrics | Admin Backend |
The frontend only needs the URLs of the optional services; see Optional services. The backend references are in DIAL Evaluations configuration and DIAL Deployment Manager configuration. Analytics has its own references: DIAL Analytics configuration and Enrichment Runner configuration.
Choose a setup
| Direct to DIAL Core | With Admin Backend | |
|---|---|---|
| Frontend settings | DIAL_CORE_API_URL; DIAL_ADMIN_API_URL unset | DIAL_CORE_API_URL and DIAL_ADMIN_API_URL |
| Where configuration is stored | Core's blob storage, through Core's Configuration API [Preview] | Core's blob storage for the Core-direct screens; the backend's database for its own screens, exported for Core to read |
| Extra screens | — | Entities, Builders, Access Management, and Audit, with whole-configuration import and export |
| Administrator roles | Core's access.admin.rules | Core's rules, plus the backend's FULL_ADMIN and READ_ONLY_ADMIN |
The current advanced setup sample runs Admin directly against Core. The Docker Compose example is adapted from it; for Kubernetes, see DIAL Admin installation.