Where Is the Dire Wolf Config File?
Dire Wolf reads config from working dir or home with flags overriding. No /etc defaults exist upstream.
Last updated
Dire Wolf resolves config by launch context with working dir first and home second. Flags override everything per run with service files imposing their own homes. No system defaults exist upstream.
Logs stay silent without configuration while telemetry reads opt-in outputs. Udev rules handle hardware PTT apart from configs. Quote launch-relative paths with flag overrides.
Where Dire Wolf stores this, by platform
~/direwolf.conf
Launch-relative config with home fallback plus flag overrides per run. Service examples impose log homes outside defaults. No system paths exist upstream.
Frequently asked questions
How do I back up Dire Wolf config?
Copy direwolf.conf with sdr companions from the launch folder or home tree. Flags override paths per invocation with service examples showing log splits. Udev rules live apart for hardware PTT.
Why do Dire Wolf guides disagree on paths?
They follow launch context rather than system conventions. Working dir wins, then home, then explicit flags. Service files impose their own log homes outside upstream defaults.
Where are Dire Wolf logs?
It stays silent unless configured with log dirs or files. Telemetry tools read configured outputs rather than defaults. Systemd examples provide the only fixed log pattern.
Notice an outdated path? Let us know.