Configuration
Configuration schema for the self-hosted engine.
The engine configuration is provided as YAML and can be overridden by environment variables. Both community and enterprise builds share a common core schema and then diverge with additional sections in enterprise builds.
Environment overrides use the RSTREAM_ENGINE_ prefix. Keys are lowercased and mapped to dot paths. Double underscores represent nested separators.
Community edition sections
The community edition top-level sections are engine, tls, certs, auth, metrics, limits, and timeouts.
The engine section contains host and log_level. Listener sections use enabled and listen_addr. Certificate configuration supports a static provider with cert_file and key_file. Authentication supports the JWT backend with token_jwt_secret.
Enterprise edition sections
Enterprise builds add sections including quic, dtls, idp, events, geoip, and packages.
Limits and timeouts
Limits include bandwidth limits per plan and tunnel count limits per plan. Timeouts include stream request and HTTP idle timeouts.