fix(hirag): use container DNS for Supabase realtime

[POWERFULMOVES]

Summary

• Fixes Hi-RAG failing to connect to Supabase realtime after Docker restarts
• Changes default SUPABASE_REALTIME_URL from host.docker.internal:65421 to supabase_kong_PMOVES.AI:8000
• Direct container-to-container DNS resolution is more reliable in WSL2 environments

Problem

The host.docker.internal hostname resolves to Docker Desktop's gateway IP (192.168.65.254) in WSL2, which doesn't properly route to host-bound ports. This caused connection failures:

websockets.exceptions.InvalidMessage: did not receive a valid HTTP response
ERROR:hirag.gateway.v2:Supabase realtime listener error; retrying in 60.0s

Solution

Since both Hi-RAG and Supabase Kong containers are on pmoves-net, use direct container DNS:

Before	After
ws://host.docker.internal:65421/realtime/v1	ws://supabase_kong_PMOVES.AI:8000/realtime/v1

Test plan

• Verified container-to-container DNS resolves correctly
• Tested connection with new URL returns {"message":"Success"}
• Recreate Hi-RAG containers and verify realtime connection works

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated real-time service connection endpoint configuration across multiple application services for proper connectivity infrastructure alignment.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The Supabase real-time WebSocket endpoint URL is updated from ws://host.docker.internal:65421/realtime/v1 to ws://supabase_kong_PMOVES.AI:8000/realtime/v1 across Docker Compose configurations and a service initialization script. This changes the runtime connection point for Supabase real-time services without altering logic or control flow.

Changes

Cohort / File(s)	Summary
Docker Compose Configuration pmoves/docker-compose.yml, pmoves/docker-compose.gpu-image.yml	Updated SUPABASE_REALTIME_URL environment variable across three service blocks (hi-rag-gateway, hi-rag-gateway-v2, hi-rag-gateway-v2-gpu) to point to the new Supabase Kong endpoint.
Service Initialization Script pmoves/services/hi-rag-gateway-v2/scripts/wait-for-deps.sh	Updated default Supabase realtime WebSocket URL to align with Docker Compose configuration changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

These are straightforward, repetitive configuration changes affecting only environment variables across a small number of files with no functional logic modifications.

Possibly related PRs

• fix(hirag): Docker restart stability - Supabase realtime connection resilience #333: Originally introduced the Docker Compose files and wait-for-deps.sh script that are now being updated with the new Supabase real-time endpoint URL.

Poem

🐰 A hop, a skip, from docker's den,
New URLs guide us once again,
From localhost to Kong we spring,
Real-time whispers on the wing! 🌐✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description provides a clear summary, explains the problem and solution with evidence, but omits required sections like Testing commands and Required Checks checkboxes.	Add a Testing section with actual commands run, and include the Required Checks checklist from the template to fully comply with repository standards.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: using container DNS instead of host.docker.internal for Supabase realtime connections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/hirag-realtime-container-dns

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a4c1f48 and b371a12.

📒 Files selected for processing (3)

• pmoves/docker-compose.gpu-image.yml (1 hunks)
• pmoves/docker-compose.yml (2 hunks)
• pmoves/services/hi-rag-gateway-v2/scripts/wait-for-deps.sh (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

pmoves/**/docker-compose.yml

📄 CodeRabbit inference engine (pmoves/AGENTS.md)

Use Compose profiles (data, workers) to scope what runs locally in docker-compose.yml

Files:

• pmoves/docker-compose.yml

🧠 Learnings (3)

📚 Learning: 2025-12-15T12:03:17.291Z

Learnt from: CR
Repo: POWERFULMOVES/PMOVES.AI PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-15T12:03:17.291Z
Learning: UI updates: run make -C pmoves notebook-workbench-smoke ARGS='--thread=<uuid>' to lint the Next.js bundle and validate Supabase connectivity; reference pmoves/docs/UI_NOTEBOOK_WORKBENCH.md

Applied to files:

• pmoves/services/hi-rag-gateway-v2/scripts/wait-for-deps.sh

📚 Learning: 2025-12-07T11:03:53.415Z

Learnt from: CR
Repo: POWERFULMOVES/PMOVES.AI PR: 0
File: pmoves/AGENTS.md:0-0
Timestamp: 2025-12-07T11:03:53.415Z
Learning: Applies to pmoves/ui/**/*.{js,jsx,ts,tsx} : UI updates: run `make -C pmoves notebook-workbench-smoke ARGS="--thread=<uuid>"` to lint the Next.js bundle and validate Supabase connectivity; reference `pmoves/docs/UI_NOTEBOOK_WORKBENCH.md`

Applied to files:

• pmoves/services/hi-rag-gateway-v2/scripts/wait-for-deps.sh

📚 Learning: 2025-12-15T12:02:18.878Z

Learnt from: CR
Repo: POWERFULMOVES/PMOVES.AI PR: 0
File: pmoves/docs/ARTSTUFF/realtime/GEMINI.md:0-0
Timestamp: 2025-12-15T12:02:18.878Z
Learning: Applies to pmoves/docs/ARTSTUFF/realtime/**/*{pinokio,install,start,update,reset}.{js,json} : Preserve existing functionality and only modify necessary parts when working with existing launcher scripts

Applied to files:

• pmoves/services/hi-rag-gateway-v2/scripts/wait-for-deps.sh

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Analyze (python)

🔇 Additional comments (4)

pmoves/docker-compose.yml (2)

572-572: Updated realtime URL uses container DNS for improved WSL2 compatibility.

The change from host.docker.internal:65421 to supabase_kong_PMOVES.AI:8000 addresses the PR objective to use container-to-container DNS. The service is correctly connected to the supabase_net (pmoves-net) network at line 583, which should enable direct communication with the Supabase Kong container.

Please verify the container name and connectivity as noted in the wait-for-deps.sh review comment.

---

677-677: Consistent URL update for GPU variant.

The change mirrors the update made to hi-rag-gateway-v2 at line 572. The service is properly connected to supabase_net at line 701.

Verification of container name and network connectivity (see wait-for-deps.sh comment) applies here as well.

pmoves/docker-compose.gpu-image.yml (1)

27-27: Consistent URL update across GPU image compose file.

The change aligns with updates in the main docker-compose.yml. The service is connected to the external pmoves-net network (defined as pmoves at lines 49-51), enabling container-to-container DNS resolution.

Verification of the container name and network connectivity (see wait-for-deps.sh comment) applies to this configuration as well.

pmoves/services/hi-rag-gateway-v2/scripts/wait-for-deps.sh (1)

16-16: Verify container name and confirm correct Supabase network assignment.

The default URL uses supabase_kong_PMOVES.AI:8000/realtime/v1, which has an unusual .AI suffix not found in standard Supabase documentation. Port 8000 is correct for Kong, and /realtime/v1 is the correct Supabase Realtime path. However, verify:

• The actual container name matches supabase_kong_PMOVES.AI (or confirm the correct name if running via Supabase CLI)
• Services are connecting to the supabase_net network (not pmoves-net)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Realtime default uses non-existent Supabase host

The new fallback SUPABASE_REALTIME_URL points at ws://supabase_kong_PMOVES.AI:8000/realtime/v1, but the Supabase CLI stack we join on pmoves-net exposes Kong as supabase-kong (see the botz-gateway defaults in pmoves/docker-compose.yml lines 832-839). There is no container registering the _PMOVES.AI hostname, so on a stock make -C pmoves supa-start run the wait-for-deps probe will DNS fail and Hi-RAG’s realtime listener will never come up unless users override the variable. This regresses the out-of-the-box configuration you were trying to fix for WSL.

Useful? React with 👍 / 👎.