Dial a route at the machine port its module's placement assigned, from the mesh-sdk whose plans carry it (issue 774, research 072 row 34)
route-proxy from plans dialled every route at the software's own port: gitea at 127.0.0.1:3000 (published at 20000) and grafana on ace at 3000 (published at 20012), and public sites answered 502. The proxy already reaches a module beside it over loopback and one elsewhere at the plan's address; the plan now carries the assigned port, and a test composes the plan with the SDK and reads it as the proxy does, so the two cannot drift again. The controller, NATS-native: no piece moves; route-proxy only.
This commit is contained in:
@@ -3,7 +3,7 @@ module route-proxy
|
||||
go 1.26.0
|
||||
|
||||
require (
|
||||
git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261031084708-acbf80ad910a
|
||||
git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261031120835-b61102245706
|
||||
github.com/nats-io/nats.go v1.54.0
|
||||
golang.org/x/crypto v0.57.0
|
||||
)
|
||||
|
||||
Reference in New Issue
Block a user