added proxy port

src/apps/signage/README.md

@@ -9,7 +9,8 @@ service itself is not chosen/installed yet.
 | VM | 1 core · 1024 MB · 16 G disk · `tanka1` · `lan` bridge |
 | Image | `debian-13-generic-amd64.qcow2` (cloud-init) |
 | vmid | 816 |
-| Depends on | `cluster:vm`, `templates:debian`, `backup:vm` |
+| Depends on | `cluster:vm`, `templates:debian`, `backup:vm`, `network:proxy` |
+| Published at | `https://signage.makerfloss.eu` → port 80 on the VM |
 | Target env | `omStaging` (installs as `signage-omStaging`) |
 
 ## Files
@@ -21,6 +22,8 @@ service itself is not chosen/installed yet.
 
 ## Next steps
 
-Pick the signage software and extend `update.sh`/`test.sh` accordingly. If it
-exposes a web UI, add `network:proxy` (and `identity:identity` for OIDC login)
-to `dependsOn` and a matching `config` block.
+Pick the signage software and extend `update.sh`/`test.sh` accordingly. The
+reverse proxy already publishes the VM at `signage.makerfloss.eu`; confirm
+`proxyPort` (currently `80`, and `proxyUpstreamTls` if the UI is HTTPS) once the
+software is chosen, and list its listening ports in `ports`. Add
+`identity:identity` to `dependsOn` if it can take an OIDC login.

src/apps/signage/signage.json

@@ -9,7 +9,7 @@
   "vmid": 816,
   "vmtag": "TAPPaaS,MakerFLOSS",
   "ports": [],
-  "dependsOn": ["cluster:vm", "templates:debian", "backup:vm"],
+  "dependsOn": ["cluster:vm", "templates:debian", "backup:vm", "network:proxy"],
   "provides": [],
   "config": {
     "cluster:vm": {
@@ -24,6 +24,10 @@
       "imageLocation": "https://cdimage.debian.org/cdimage/cloud/trixie/latest",
       "cloudInit": "true",
       "bridge0": "lan"
+    },
+    "network:proxy": {
+      "proxyDomain": "signage.makerfloss.eu",
+      "proxyPort": 80
     }
   }
 }