Configuration & environment

ScaiLog is configured through environment variables, a few command-line flags, and — for the CLI — a config.toml file. Each runtime component reads its own SCAILOG_* variables; there is no shared global config file for the server. This page enumerates every environment variable and config key from the source, grouped by the component that reads it, then describes the CLI config file and the on-disk data-dir layout.

Server (scailog-server)#

The server reads its configuration from ServerConfig.from_env(). Command-line flags to scailog-server are --standalone, --data-dir, --host (default 127.0.0.1), --port (default 8080), and --init (initialize, print the bootstrap key, and exit).

SCAILOG_STANDALONE is truthy for 1, true, yes, or on (case-insensitive).

OIDC is enabled only when both SCAILOG_OIDC_BASE_URL and SCAILOG_OIDC_CLIENT_ID are set and the ScaiKey SDK is installed; otherwise the server accepts only built-in API keys. OIDC tokens are mapped to a role via the scailog_role claim (unknown or missing role defaults to log_reader); the tenant comes from the tenant/tid claim or SCAILOG_OIDC_DEFAULT_TENANT.

A few ServerConfig fields are not wired to environment variables and take their dataclass defaults: keymap_backup_retention_days (7), retention_sweep_seconds (3600), and self_ingest (true).

Agent (scailog-agent)#

The agent reads these (all overridable by command-line flags of the same name).

SDK (emit path)#

The default logger reads its identity from the environment.

CLI (scailog) and CI (scailog-ci)#

Both read the same config file and a small set of variables.

Audit (scailog-audit)#

The offline audit job reads scailog.db directly and calls the ScaiGrid classifier.

The CLI config file (config.toml)#

The scailog CLI and scailog-ci load ~/.config/scailog/config.toml (or $SCAILOG_CONFIG). Top-level keys mirror the environment overrides, and an optional [oidc] section supplies device-flow login settings.

1
2
3
4
5
6
7

server_url = "http://127.0.0.1:8080"
api_key = "slk_read_XXXXXXXXXXXX"
tenant = "default"

[oidc]
base_url = "https://id.example.com"
client_id = "scailog-cli"

Environment variables win over the file: SCAILOG_SERVER, SCAILOG_API_KEY, and SCAILOG_TENANT override server_url, api_key, and tenant respectively. For login, --oidc-url/--client-id win over SCAILOG_OIDC_*, which win over the [oidc] section.

Data-dir layout#

Everything the server persists lives under the data dir (SCAILOG_DATA_DIR). The key-map is a deliberately separate SQLite file so its backups can be held to a short retention window — that retention bound is what makes cryptographic erasure absolute.

The agent, when run separately, keeps its own cache in agent.db (SCAILOG_AGENT_CACHE) on the agent host, not in the server data dir.