Skip to content

feat(docker): make the core NATS bind host configurable - #1411

Merged
FelixTJDietrich merged 2 commits into
mainfrom
feat/configurable-nats-bind
Jul 21, 2026
Merged

feat(docker): make the core NATS bind host configurable#1411
FelixTJDietrich merged 2 commits into
mainfrom
feat/configurable-nats-bind

Conversation

@FelixTJDietrich

Copy link
Copy Markdown
Collaborator

Motivation

core-nats-server was published only on 127.0.0.1:4222, so nothing off-box could reach the bus. But the integration/sync consumers in other environments are meant to consume events from an upstream environment's JetStream (see docker/preview/compose.app.yamlHEPHAESTUS_SYNC_NATS_SERVER may point at an upstream NATS). With a hardcoded loopback bind that's impossible, and those consumers fail to start.

Change

Bind the port via ${NATS_BIND_HOST:-127.0.0.1}:

  • Default unchanged — loopback-only, so existing single-host deployments keep the safe posture.
  • Operators can set NATS_BIND_HOST=0.0.0.0 (or a specific interface address) to expose the bus to other hosts.

The bus is unauthenticated, so the changeset and the inline comment both spell out that exposure belongs only on a trusted or firewalled network.

Testing

  • docker compose config validates.
  • No application code changed; Java/TS gates N/A (docker/ + changeset only).

🤖 Generated with Claude Code

The NATS port was hardcoded to 127.0.0.1, so only same-host containers could
reach the bus. Bind it via ${NATS_BIND_HOST:-127.0.0.1}: the default stays
loopback-only, and an operator can set 0.0.0.0 (or a specific interface) to let
another environment consume events from this one's JetStream.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012stCYrymLyX9VZ8PrPUs88
@FelixTJDietrich
FelixTJDietrich requested a review from a team as a code owner July 20, 2026 16:09
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@FelixTJDietrich, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d6d5393d-35be-4f37-8f60-d2a7fe3930ea

📥 Commits

Reviewing files that changed from the base of the PR and between 6faed3b and 3f19275.

📒 Files selected for processing (2)
  • .changeset/configurable-nats-bind.md
  • docker/compose.core.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/configurable-nats-bind

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added feature New feature or enhancement ci GitHub Actions, workflows, build pipeline changes infrastructure Docker, containers, and deployment infrastructure size:S labels Jul 20, 2026
@FelixTJDietrich
FelixTJDietrich merged commit 2234ad0 into main Jul 21, 2026
11 checks passed
@FelixTJDietrich
FelixTJDietrich deleted the feat/configurable-nats-bind branch July 21, 2026 08:11
@github-actions

Copy link
Copy Markdown
Contributor

📚 Documentation Preview

Preview has been removed (PR closed)

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

Labels

ci GitHub Actions, workflows, build pipeline changes feature New feature or enhancement infrastructure Docker, containers, and deployment infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant