Skip to content

docs(config): note that the node feeds publish a host port either way (#760)#763

Merged
VijitSingh97 merged 1 commit into
developfrom
docs/760-port-publish-note
Jul 24, 2026
Merged

docs(config): note that the node feeds publish a host port either way (#760)#763
VijitSingh97 merged 1 commit into
developfrom
docs/760-port-publish-note

Conversation

@VijitSingh97

Copy link
Copy Markdown
Collaborator

Found by the pre-release e2e on the bench, not by reading the diff.

monerod's 18083 and the Tari node's 18142 are published on the host from this release — on 127.0.0.1 unless monero.zmq_lan_access / tari.grpc_lan_access is on. Gouda was running two hand-rolled socat forwards on those exact ports (the arrangement these switches replace), so docker compose up refused to start monerod:

failed to bind host port 127.0.0.1:18083/tcp: address already in use
[ERROR] Upgrade failed during 'docker compose up'

The behaviour is right and matches the existing 18081/18143 publishes — but nothing told an operator their upgrade would stop on a port they'd already taken. This adds a CHANGELOG upgrade note and a sentence beside each config key.

No code change: within a single compose file a port entry can't be conditionally omitted, and making the publish conditional would need a rendered override file — new machinery for a case a sentence covers.

Ponytail review: docs only, nothing to cut. markdownlint + docs-voice green.

🤖 Generated with Claude Code

…#760)

The e2e caught this on the bench: monerod's 18083 and the Tari node's 18142 are
published from this release, loopback unless the LAN switch is on, so anything
already holding either port stops the upgrade at 'docker compose up'. Say so in
the CHANGELOG upgrade note and beside both config keys.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@VijitSingh97
VijitSingh97 merged commit 4285d37 into develop Jul 24, 2026
15 checks passed
@VijitSingh97 VijitSingh97 mentioned this pull request Jul 24, 2026
@VijitSingh97
VijitSingh97 deleted the docs/760-port-publish-note branch July 24, 2026 18:55
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.

1 participant