To learn about the configuration options, have a look at the full configuration reference.
Configuration file
The Restate Server accepts a TOML configuration file that can be specified either providing the command-line option--config-file=<PATH>
or setting the environment variable RESTATE_CONFIG=<PATH>
. If not set, the default configuration will be applied.
Overrides
Restate server accepts a sub-set of the configuration through command-line arguments, you can see all available options by adding--help
to restate-server
.
The order of applying configuration layers follows the following order:
- Built-in defaults
- Configuration file (
--config-file
or viaRESTATE_CONFIG
) - Environment variables
- Command line arguments (
--cluster-name=<VALUE>
)
Environment variables
You can override any configuration entry with an environment variable, this overrides values loaded from the configuration file. To do that, the following rule applies:- Prefix the configuration entry key with
RESTATE_
- Separate every nested struct with
__
(double underscore) and all hyphens-
with a_
(single underscore).
admin.bind-address
, the corresponding environment variable is RESTATE_ADMIN__BIND_ADDRESS
.
Configuration introspection
If you want to generate a configuration file that includes values loaded from your environment variables or overrides applied torestate-server
command-line, you can add --dump-config
to dump the default TOML config with overrides applied:
SIGUSR1
to the server process. This prints a dump of the live configuration to standard error.
For instance on Mac/Linux, you can find the PID of restate-server by running:
pgrep
’s output: