Add OS-level vs app-level mDNS disclaimer to tutorial#314
Merged
Conversation
Adds a section recommending Avahi (OS-level) over JmDNS (app-level) for Linux servers and containers, while noting JmDNS is appropriate for portable cross-platform applications. Closes #313
Copilot
AI
changed the title
[WIP] Fix mdns tutorial by adding disclaimer for configurations
Add OS-level vs app-level mDNS disclaimer to tutorial
Jun 22, 2026
Member
|
LGTM! |
zugazagoitia
approved these changes
Jun 22, 2026
❌ Delete Preview for javalin.io failed.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Per community feedback, the mDNS tutorial lacked guidance on when to use OS-level daemons (Avahi) vs the in-app JmDNS approach shown in the tutorial — particularly relevant for Linux servers and containerized deployments where JmDNS can advertise wrong IPs or conflict with other services.