Files
ProdDash/modules/prodcom-transcript/module.json
T
Waters ChurchandClaude Opus 5 a3e1282354 No campus's address ships in the repo
prodcom-transcript's endpoint defaulted to 10.3.11.152:24480 — Apollo
Beach's ProdCom. A fresh install anywhere therefore came up reading AB's
comms and reported itself healthy doing it: that is exactly what the new
North Attleboro install did. The default is now blank, so a new install
says "No ProdCom server configured" (in red, as the ProPresenter modules
already do for a missing host) until someone points it at the ProdCom for
that location. Setting a host still connects as before.

The same address is out of SPEC.md's worked example, CLAUDE.md's note
about the reference app, and the prodcom-listener snapshot's config,
README and fallback — that fallback now exits with a line telling the
operator what to set, rather than throwing on an empty URL.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-16 10:37:56 -04:00

48 lines
1.0 KiB
JSON

{
"id": "prodcom-transcript",
"name": "ProdCom",
"version": "1.3.1",
"proddash": ">=1.1.0",
"description": "Live ProdCom transcript",
"permissions": [
{
"kind": "local-network",
"reason": "Reaching the ProdCom API on this network"
}
],
"client": "client.js",
"server": "server.js",
"style": "style.css",
"minSize": {
"w": 3,
"h": 2
},
"defaultSize": {
"w": 4,
"h": 4
},
"configSchema": {
"prodcom": {
"type": "endpoint",
"label": "ProdCom server",
"default": {
"host": "",
"port": 24480
},
"help": "The ProdCom server at THIS location — every campus has its own. Blank until you set it, so a new install never reads another campus's comms."
},
"apiKey": {
"type": "password",
"label": "API key (only if PSK auth is enabled in ProdCom)",
"default": ""
}
},
"instanceSchema": {
"showAvatars": {
"type": "boolean",
"label": "Show channel icons",
"default": true
}
}
}