You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+30-6Lines changed: 30 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,16 +70,40 @@ The default directory for configuration files is `~/.config/go-librespot`. On ma
70
70
71
71
The full configuration schema is available [here](/config_schema.json), only the main options are detailed below.
72
72
73
-
### Zeroconf mode
73
+
### Zeroconf Mode and mDNS Backend Selection
74
74
75
-
This is the default mode. It uses mDNS auto discovery to allow Spotify clients inside the same network to connect to
76
-
go-librespot. This is also known as Spotify Connect.
75
+
Zeroconf mode enables mDNS auto discovery, allowing Spotify clients inside the same network to connect to go-librespot. This is also known as Spotify Connect.
77
76
78
-
An example configuration (not required) looks like this:
77
+
**Backend selection:**
78
+
go-librespot supports two different backends for mDNS service registration:
79
+
80
+
-**builtin**: (default) Uses the built-in mDNS responder provided by go-librespot itself.
81
+
-**avahi**: Uses the system's avahi-daemon (via D-Bus) for mDNS service registration.
82
+
83
+
You can configure which backend to use via the `zeroconf_backend` setting in your configuration file:
- Use **avahi** if you want to integrate with an existing Avahi daemon, e.g. on embedded systems, to avoid port conflicts, or to centralize mDNS advertisements with system service management (e.g., using `systemd`).
98
+
- Compatible with Avahi 0.6.x and later (tested with 0.7 and 0.8).
99
+
- Use **builtin** if you do **not** have Avahi running and want go-librespot to manage its own mDNS advertisements (no extra dependencies required).
100
+
101
+
#### Example minimal Zeroconf configuration
79
102
80
103
```yaml
81
-
zeroconf_enabled: false # Whether to keep the device discoverable at all times, even if authenticated via other means
82
-
zeroconf_port: 0# The port to use for Zeroconf, 0 for random
104
+
zeroconf_enabled: true # Whether to keep the device discoverable at all times, even if authenticated via other means
105
+
zeroconf_port: 0# The port to use for Zeroconf, 0 for random
0 commit comments