stores

The stores clause defines named, persistent on‑disk data stores used by the server to retain state across restarts (for example session metadata, counters, or other internal artifacts that require durability beyond process lifetime). Each store block maps a logical store name to a filesystem directory. The runtime is responsible for creating internal files/subdirectories inside the configured directory as needed.

Currently the configuration surface is intentionally minimal: only the storage directory is specified. Additional tuning (retention, quotas, compression, compaction policies, etc.) may be introduced later; those are not available unless explicitly documented.

Syntax

stores {
    store "SESSION_STORE" {
        directory "/var/lib/radiator/stores/session";
    }

    store "STATE_CACHE" {
        directory "/var/lib/radiator/stores/state";
    }
}

Elements

Naming

Use clear, purpose‑driven names (e.g. SESSION_STORE, ACCOUNTING_STATE, TOKEN_CACHE). Names are case sensitive. Defining the same name twice causes a configuration error.

Directory

• Must be writable by the Radiator process user.
• If it does not exist, ensure the service unit / deployment creates it with correct permissions before startup.
• Should be on a filesystem with sufficient I/O durability (avoid tmpfs or ephemeral containers unless the data is disposable).
• Avoid sharing a single directory across multiple different stores; isolate for clarity and easier maintenance.

Example

stores {
    store "SESSION_STORE" {
        directory "/var/lib/radiator/stores/session";
    }

    store "ACCOUNTING_STATE" {
        directory "/var/lib/radiator/stores/accounting";
    }
}