service_manager: cascade --split mother variant (hero_aibroker) #95

New issue

Open

opened 2026-05-07 19:12:36 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-05-07 19:12:36 +00:00

Owner

Tracked from #90.

The upstream service_aibroker.nu supports a --split flag that registers a SECOND service hero_aibroker_mother alongside the regular hero_aibroker. The mother runs on a fixed TCP port (33850) and child brokers forward chat requests to it.

Sockets:

child: $HERO_SOCKET_DIR/hero_aibroker/{rpc,rest,ui}.sock
mother: $HERO_SOCKET_DIR/hero_aibroker_mother/{rpc,rest,ui}.sock

The v2 port covers child / single-instance only.

Fix: add a second HeroService impl HeroAibrokerMother that shares the same binaries[] (the binary picks aibroker_config vs aibroker_config_mother based on a --mother flag) but registers as a different hero_proc service.

Limitation: in hero_aibroker.rs.

Tracked from #90. The upstream `service_aibroker.nu` supports a `--split` flag that registers a SECOND service `hero_aibroker_mother` alongside the regular `hero_aibroker`. The mother runs on a fixed TCP port (33850) and child brokers forward chat requests to it. Sockets: - child: $HERO_SOCKET_DIR/hero_aibroker/{rpc,rest,ui}.sock - mother: $HERO_SOCKET_DIR/hero_aibroker_mother/{rpc,rest,ui}.sock The v2 port covers child / single-instance only. **Fix**: add a second `HeroService` impl `HeroAibrokerMother` that shares the same `binaries[]` (the binary picks `aibroker_config` vs `aibroker_config_mother` based on a `--mother` flag) but registers as a different hero_proc service. `Limitation:` in hero_aibroker.rs.