Home · Docs
Docs
Every site is one computer on the LAN (the box). TVs and kiosks talk only to that machine. Cloud, if you use it, is a control plane the box calls. It never reaches into the building.
/player on the box. Do not run the kiosk installer and expect a site manager.Pick the OS of the machine that will stay on and keep a stable LAN IP.
x86_64 mini-PC, NUC, or VM. Docker Engine + Compose. Strongest path for cameras (host networking).
Docker Desktop, Linux containers (WSL2). Same appliance image. Use the PowerShell helper, not the Edge kiosk.
The Pi is the site manager (Docker). 4 GB+ RAM. This is not the HDMI kiosk agent.
Docker Desktop. Same overlay as Windows (MediaMTX cannot use Linux host networking). Fine for a lab; Linux is better in a plant.
Box overview: hardware, .env, panel URLs, air-gap, backup →
Standalone is complete with no account. For multi-site, create a site in the cloud panel, copy the env block, paste it on the box, restart. Cloud attach steps.
After the panel answers at http://<LAN-IP>:8090/, add displays. Every client’s master URL is the box, never dutywall.com.
Yes, awkwardly: Docker Desktop for the box, then a browser or the Edge kiosk pointing at this PC’s LAN IP. Most sites use a quiet NUC/Pi as the box and put kiosks on the TVs.
Not at once. Either Docker (site manager) or the HDMI kiosk agent (a screen). Use two Pis, or a Linux/Windows box plus Pi screens.
No. Leave CLOUD_URL blank. Create a site in the cloud panel only if you want desired state from dutywall.com.