Server configuration
config/server.toml defines the gateway listener, features, logging, devices, scan groups, databases, authentication, and topology. Node settings and notifications use additional files.
A server.toml with devices and history.
# config/server.toml [server] name = "plant-a" bind_address = "0.0.0.0" http_port = 8400 [features] historian = true hmi_serving = true [logging] level = "info" format = "pretty" [logging.file] enabled = true rotation = "daily" [[scan_groups]] name = "fast" rate_ms = 100 [[scan_groups]] name = "normal" rate_ms = 250 [[devices]] name = "s7-plc" driver = "s7" [devices.config] host = "192.168.0.1" rack = 0 slot = 1 poll_rate_ms = 500 [[databases]] name = "historian" driver = "postgresql" [databases.config] host = "localhost" database = "thermite" username = "thermite" password_env = "THERMITE_DB_PASSWORD"
Identity and listener.
Subsystem switches.
Console and file logging.
file.* keys live in a [logging.file] sub-table.
Named polling intervals for OPC UA tags.
OPC UA tags select an interval with scan_group = "<name>". S7, CIP, Modbus, and BACnet use the device's poll_rate_ms; the simulator uses update_rate_ms.
PostgreSQL connections.
config.* keys live in a [databases.config] sub-table. An unbound historian needs one eligible PostgreSQL connection to bind; it does not choose between multiple candidates.
Config that lives on other pages.
Per-driver connection settings for all seven drivers.
Gateway users, sessions, and project-level roles.
Multi-gateway topologies — redundant pairs, hub-and-edge — are Commercial features configured with your deployment engineer.