feat(docker): make the core NATS bind host configurable - #1411
Conversation
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
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
📚 Documentation Preview
|
Motivation
core-nats-serverwas published only on127.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 (seedocker/preview/compose.app.yaml—HEPHAESTUS_SYNC_NATS_SERVERmay 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}: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 configvalidates.🤖 Generated with Claude Code