Skip to content

Conversation

@YutongGu
Copy link
Contributor

Description

Adds support for using an existing avahi-daemon for mDNS service registration instead of the built-in mDNS responder. This is useful for:

  • Embedded systems where a single mDNS daemon is preferred
  • Avoiding port conflicts with other mDNS services
  • Integration with system service management

Configuration:

zeroconf_backend: avahi  # Options: "builtin" (default), "avahi"

Or via command line:

go-librespot -c zeroconf_backend=avahi

Compatibility:

  • Avahi 0.6.x and later (uses stable D-Bus API)
  • Tested with Avahi 0.7 and 0.8

…in backend

This update introduces a new configuration option for selecting the mDNS backend in the Zeroconf service. Users can now choose between the built-in mDNS responder and the avahi-daemon for service registration. The configuration schema has been updated accordingly, and the necessary backend implementations have been added.
@YutongGu
Copy link
Contributor Author

Oops looks like this duplicates #224. Happy to close this as duplicate if we prefer those changes over this one.

"description": "The port to use for the Zeroconf service (empty for random)",
"default": 0
},
"zeroconf_backend": {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps add something to the README to explain the two backens and why to use one over the other?

@devgianlu
Copy link
Owner

This looks better than my attempt because it doesn't add a runtime dependency on Avahi. Looking forward to merge this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants