This is the recommended first deployment mode for TruePresence.
conda run -n dl uvicorn app.main:app --app-dir apps/api --host 0.0.0.0 --port 8000http://127.0.0.1:8000/teacher/
- connect the iPhone and authority host to the same Wi-Fi
- grant camera, location, and local network permissions
- use the authority-generated QR code to bind the mobile device
This reference setup is currently presented through a teacher/student workflow, but the same deployment shape also works for supervisor/worker, dispatcher/driver, or manager/field-rep products.
docker build -t truepresence .
docker run --rm -p 8000:8000 truepresenceThis is the easiest way to move from a single developer Mac to an edge or pilot deployment.
- keep the authority console and backend together
- expose one canonical LAN URL to the mobile app
- prefer fixed local IPv4 over
.localfor reliability - treat USB as an install/debug tool, not a runtime requirement
If the mobile iPhone cannot reach the authority backend:
- make sure the backend is listening on
0.0.0.0 - confirm both devices are on the same Wi-Fi
- confirm the authority host firewall allows inbound connections
- confirm the mobile app has Local Network permission
The recommended commercial rollout path is:
- one-operator pilot on a Mac
- small edge box, branch mini-server, or classroom appliance
- optional cloud synchronization for reporting or analytics
This progression keeps the product operationally simple while preserving a clean path to multi-site deployments.
The same deployment pattern can be reused as:
- education -> teacher console + student app + classroom site
- field workforce -> supervisor console + worker app + worksite geofence
- retail operations -> manager console + rep app + store visit site
- route logistics -> dispatcher console + driver app + checkpoint site
The public codebase ships the education-first UI today, but the deployment model is intentionally broader.