jschoubben
f118344246
75 endpoints across 50 modules, named from what each one is for rather than by a rule: mail's seven protocol ports are smtp, imaps, submission and the rest; unifi's nine are inform, stun, discovery, the two portal ports and syslog; minio's two are s3 and console; the resolver's two are dns-udp and dns-tcp. And 35 route contributions name the endpoint they serve instead of repeating its port. A route and a listen both carried a port and nothing said they were the same thing; now one of them does. gitea's path-level deny rule names neither, because it is a rule about a name rather than an endpoint. novox/hq ADR 0138. The words shipped a release ahead in mesh-controller #138 and #139, and the control plane running today is built from that merge — checked before this was written, because an unknown manifest key is refused and a catalogue using one against an older control plane would stop resolving.
52 lines
1.0 KiB
JSON
52 lines
1.0 KiB
JSON
{
|
|
"module": "novox.be",
|
|
"version": "1",
|
|
"capabilities": [
|
|
"container-runtime"
|
|
],
|
|
"requires": [
|
|
"route"
|
|
],
|
|
"contributes": {
|
|
"route": {
|
|
"label": "@",
|
|
"endpoint": "web"
|
|
}
|
|
},
|
|
"binds": {
|
|
"route": "/var/lib/novox.be/route.json"
|
|
},
|
|
"listens": [
|
|
{
|
|
"name": "web",
|
|
"port": 4000,
|
|
"protocol": "tcp",
|
|
"from": "mesh",
|
|
"why": "the public website over http; the public name novox.be is a route grant, and route-proxy reaches it on this published port"
|
|
}
|
|
],
|
|
"resources": [
|
|
{
|
|
"id": "state",
|
|
"type": "directory",
|
|
"path": "/var/lib/novox.be",
|
|
"mode": "0700"
|
|
},
|
|
{
|
|
"id": "net",
|
|
"type": "network",
|
|
"name": "novox-be"
|
|
},
|
|
{
|
|
"id": "server",
|
|
"type": "container",
|
|
"name": "novox-be",
|
|
"image": "registry-api.novox.be/novox/www@sha256:aa7ed20a293e1d7444c5c5d59b6d8bdb382bad159559a22e006810e379cae69c",
|
|
"network": "novox-be",
|
|
"ports": [
|
|
"8080"
|
|
]
|
|
}
|
|
]
|
|
}
|