Configuration System
TEMU has a small YAML based configuration system for process-wide settings.
Configuration File Location
By default, TEMU reads its configuration from:
~/.config/temu/config.yaml
The ~/.config/temu/ directory is created automatically during startup if it does not already exist.
The configuration file can be overridden on the command line:
temu --config-file /path/to/config.yaml
File Format
Configuration values are looked up by slash-separated paths such as logging/stderr.
Each path component maps to one YAML level.
For example, the following YAML sets three TEMU configuration values:
logging:
stderr: true
license:
checkout-script: /home/user/.config/temu/license-checkout.temu
python:
lib3_13: /opt/python3.13/lib/libpython3.13.so
Only scalar YAML values are read by the configuration API. If a key is missing, has the wrong type, or the configuration file cannot be loaded, TEMU falls back to the default value supplied by the caller.
Access Patterns
The configuration API provides these lookup functions:
-
temu_configGetBool() -
temu_configGetString() -
temu_configGetSigned() -
temu_configGetUnsigned() -
temu_configGetDouble()
The TEMU command line also exposes helper commands for inspecting values:
-
config-bool <path> -
config-str <path> -
config-int <path> -
config-uint <path> -
config-float <path>
Queried Configuration Variables
The following table lists every configuration variable currently queried through temu_configGet*().
| Path | Type | Default | Description | Related override |
|---|---|---|---|---|
|
|
|
Enables extra logging of GDB remote protocol commands in the built-in GDB server. |
|
|
|
not set |
If set, TEMU executes the referenced command file with immediately after successful license initialization. |
none |
|
|
|
Selects stderr instead of stdout for the standard text logging backend. |
|
|
|
|
Enables extra debug behavior for the MEC model and emits an informational message when the device is created. |
|
|
|
|
Enables debug tracing in the plugin loader, for example when searching plugin paths and resolving library names. |
|
|
|
not set |
Overrides the shared-library path used when TEMU loads Python 3.13 support with |
none |
|
|
|
Enables debug logging while deserializing JSON snapshots, including object creation and property restore progress. |
|
At the time of writing, all live configuration queries are for bool and string values.
The signed, unsigned, and floating-point accessors exist in the configuration system and can be inspected with the matching CLI commands, but no currently shipped code paths query named configuration variables through those accessors.
|