jschoubben
1bc6daf31b
Each declares a web endpoint — 4001, 4012, 4013 — and published a bare 80, which the mesh has nothing to assign for, so 80 reached the machine and collided with the reverse proxy. Written the long way, the software's 80 is published at the port the module declares and the mesh rewrites the outer half to whatever it assigned. photos is the one that failed on the control node; the other two are the same fault waiting for a machine that runs a proxy.
56 lines
1.3 KiB
JSON
56 lines
1.3 KiB
JSON
{
|
|
"module": "photos-filip",
|
|
"version": "1",
|
|
"slug": "filip",
|
|
"capabilities": [
|
|
"container-runtime"
|
|
],
|
|
"requires": [
|
|
"route"
|
|
],
|
|
"contributes": {
|
|
"route": {
|
|
"label": "filip",
|
|
"endpoint": "web"
|
|
}
|
|
},
|
|
"binds": {
|
|
"route": "${dir:state}/route.json"
|
|
},
|
|
"listens": [
|
|
{
|
|
"name": "web",
|
|
"port": 4013,
|
|
"protocol": "tcp",
|
|
"from": "mesh",
|
|
"why": "the filip photos client site over http; its public name is a route grant, and route-proxy reaches it on this published port"
|
|
}
|
|
],
|
|
"resources": [
|
|
{
|
|
"id": "state",
|
|
"type": "directory",
|
|
"mode": "0700",
|
|
"place": "."
|
|
},
|
|
{
|
|
"id": "net",
|
|
"type": "network",
|
|
"name": "photos-filip"
|
|
},
|
|
{
|
|
"id": "client",
|
|
"type": "container",
|
|
"name": "photos-filip",
|
|
"image": "registry-api.novox.be/novox/photos-client@sha256:f87d63ee7bfb44c9f9748b99be6ba6dc0daf955a1d463699e9e7e3009693c0ab",
|
|
"network": "photos-filip",
|
|
"ports": [
|
|
"4013:80"
|
|
],
|
|
"names-on-purpose": {
|
|
"registry-api.novox.be": "built outside the mesh, from the application's own repository, and pulled from the registry that built it; moves when that repository is a build source on the git seat (novox/hq ADR 0155, issue 122)"
|
|
}
|
|
}
|
|
]
|
|
}
|