Home · Docs · Cloud attach

Cloud attach

The box calls the cloud. The cloud never dials you.

Create a site in the cloud panel, paste three lines into the box .env, restart. Displays still talk only to the box.

Open cloud panel Install the box first

On dutywall.com

  1. Log in at /app.
  2. Add a site (one facility, one box).
  3. Open the site → Copy env. You get something like:
DUTYWALL_CLOUD_URL=https://dutywall.com
DUTYWALL_SITE_ID=site_…
DUTYWALL_SITE_TOKEN=…

On the box

  1. Put those three lines in .env (leave them blank for air-gap).
  2. Restart: docker compose up -d (Windows: re-run standalone-up.ps1).
  3. curl http://127.0.0.1:8090/healthz should show "mode":"managed".

Within about a minute the site badge in the cloud panel turns online and screen inventory appears as the box reports it. Roku Wi-Fi strength (dBm) shows on each screen after the channel has heartbeated.

One site token, one box. Do not reuse a token already bound to another appliance. Unassign or mint a new site first. Never set a display’s MASTER_URL to dutywall.com.

Remote reboot / stack restart (Cloud Pro)

From the site page you can queue Restart stack (Dutywall + MediaMTX containers) or Reboot box. The container writes a flag; a small host timer must be installed once so it can act:

cd /path/to/dutywall   # or copy deploy/dutywall-reboot-watch.* onto the box
sudo ./deploy/install-reboot-watch.sh

After that, queued commands take effect within about 30 seconds of the box’s next cloud sync.

What still stays on the LAN

Questions

Can two buildings share one site?

No. One box, one site token. Add a second site for the second facility.

Does Copy env rotate the token?

No. You can copy it any time; it is not a one-shot secret. Treat it like a password anyway.