Multiple fridges and remote scanners

Multiple fridges and remote scanners

One server can manage multiple locations and physical scanner devices. Each booking retains its scanner and location, stock can be transferred, and minimum and target stock can be maintained separately.

Local scanner discovery

Scanner containers sharing fridge-data are discovered automatically. Give each scanner a stable SCANNER_ID and optional SCANNER_NAME. Administrators can rename, assign or disable it under Settings → Locations and scanners.

Remote scanner configuration

Create the scanner in the web interface and copy its one-time token:

SCANNER_SERVER_URL=https://fridge.example.net
SCANNER_ID=kitchen-1
SCANNER_NAME=Kitchen scanner
SCANNER_TOKEN=copy-the-one-time-token-here

Run hardware clients without a second server or database:

docker compose -f docker-compose.edge.yml up -d

Automatic LAN pairing

Set SCANNER_AUTO_DISCOVERY=true and leave SCANNER_SERVER_URL and SCANNER_TOKEN empty. The scanner discovers the server with mDNS and appears as pending. It cannot book until an administrator approves it and assigns a location. UDP 5353 multicast must work; routed VLANs usually need an mDNS reflector.

Offline operation

When the server is temporarily unreachable, scanner events are queued in the persistent edge data volume and synchronized in order after reconnection. Do not delete that volume during an outage.

Security

• Give every scanner its own token.
• Treat tokens like passwords and never commit them.
• Use HTTPS outside a trusted LAN.
• Revoke lost or replaced scanners in the web interface.