Expand description
Persistent config in ~/.config/minis-studio-worker/config.toml (Linux/macOS)
or %APPDATA%\minis-studio-worker\config.toml (Windows).
Every load/save emits a structured tracing breadcrumb so operators
can tell from journalctl which file the worker actually consulted
(and whether the file existed, was freshly bootstrapped with
defaults, or failed to read/parse). The events deliberately omit
the secret fields
(auth_token, registration_secret) so logs can be shipped
off-box without leaking credentials. See tests/config_tracing.rs
for the regression contract.
What lives here vs. what’s stripped from the user-editable surface:
- Operator-facing:
api_base_url,vram_threshold_gb,auto_start,auto_update_*,models_root. These are exposed in the desktop UI’s Config tab. - Internal state, persisted but not user-editable:
worker_id,auth_token,install_id,registration_request_id,registration_secret. The auto-register flow owns them; the UI hides them entirely. - Engine selection: removed. The runtime always builds a
MultiEnginecontaining every backend compiled into this binary and routes each job to the right one.
Structs§
Functions§
- default_
models_ root - Resolve
~/modelsfor the user running the worker. Falls back to$TMPDIR/studio-worker-modelson the (extremely unusual) machines wheredirectoriescan’t find a home directory. - load
- resolve_
path - save
- shared
Type Aliases§
- Shared
Config - Wrap a Config in a mutex for use across the runtime.