Configuration
Explains how probod loads its JSON/YAML config file at startup, the role of probod-bootstrap, and which secrets must stay persistent across restarts.
probod loads a JSON or YAML configuration file passed with -cfg-file.
Configuration is read at startup and is not hot-reloaded. After changing the
file, restart every application instance for the new settings to take effect.
Configuration sources
Section titled “Configuration sources”You can write and manage the configuration file directly. For container-based
deployments, the official image can instead use probod-bootstrap to generate
a YAML file from PROBOD_* environment variables before starting probod.
flowchart LR
managed["JSON or YAML configuration"] --> probod["probod<br/>-cfg-file config"]
environment["PROBOD_* environment variables"] --> bootstrap["probod-bootstrap"]
bootstrap --> generated["Generated YAML configuration"]
generated --> probod
probod-bootstrap is a one-time configuration generator. It exits after
writing the file; it does not run beside probod, watch the environment, or
reload configuration.
Set persistent secrets before first boot
Section titled “Set persistent secrets before first boot”Some configuration keys protect persisted data or authentication state. Generate them before the first production start, use the same values on every application instance, and keep recoverable backups of them.
| Setting | Purpose | Effect of replacing or losing it |
|---|---|---|
| Encryption key | Encrypts sensitive application data | Existing encrypted data becomes unreadable |
| Session cookie secret | Signs authentication cookies | Existing user sessions become invalid |
| Password pepper | Protects stored password hashes | Existing passwords can no longer be verified |
| OAuth 2.0 server signing key | Signs tokens issued by the platform | Previously issued tokens can no longer be verified |