hero_biz cannot connect to hero_osis in container (no HTTP API bridge) #6

New issue

Closed

opened 2026-03-04 21:18:03 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-03-04 21:18:03 +00:00

Owner

Problem

hero_biz uses reqwest HTTP client to connect to HERO0_BASE_URL (default http://127.0.0.1:3377/api/{context}/{domain}/rpc).

In the hero_services container, hero_osis_server only listens on Unix domain sockets with raw stream JSON-RPC (not HTTP). There is no HTTP endpoint that serves the /api/{context}/{domain}/rpc URL pattern.

Current workaround

hero_biz is included in the container and starts, but cannot reach the backend. HERO0_BASE_URL is set to http://127.0.0.1:6666 (hero_proxy), but hero_proxy doesn't serve the /api/{context}/{domain}/rpc pattern either.

Options to fix

Add Unix socket support to hero_biz — use hyper-unix-connector or similar to talk directly to hero_osis_server.sock
Add HTTP bridge in hero_osis — expose an HTTP endpoint that wraps the raw JSON-RPC protocol
Add the /api/{context}/{domain}/rpc route to hero_proxy — route API calls to the appropriate hero_osis_server socket

Option 2 or 3 would be the least invasive.

Context

Part of lhumina_code/home#3 (Demo Readiness).

## Problem hero_biz uses `reqwest` HTTP client to connect to `HERO0_BASE_URL` (default `http://127.0.0.1:3377/api/{context}/{domain}/rpc`). In the hero_services container, hero_osis_server only listens on Unix domain sockets with raw stream JSON-RPC (not HTTP). There is no HTTP endpoint that serves the `/api/{context}/{domain}/rpc` URL pattern. ## Current workaround hero_biz is included in the container and starts, but cannot reach the backend. `HERO0_BASE_URL` is set to `http://127.0.0.1:6666` (hero_proxy), but hero_proxy doesn't serve the `/api/{context}/{domain}/rpc` pattern either. ## Options to fix 1. **Add Unix socket support to hero_biz** — use `hyper-unix-connector` or similar to talk directly to hero_osis_server.sock 2. **Add HTTP bridge in hero_osis** — expose an HTTP endpoint that wraps the raw JSON-RPC protocol 3. **Add the `/api/{context}/{domain}/rpc` route to hero_proxy** — route API calls to the appropriate hero_osis_server socket Option 2 or 3 would be the least invasive. ## Context Part of lhumina_code/home#3 (Demo Readiness).