Start the LAN App

Work Through The Task

Use this guide when event work may happen on local devices, offline files, or LAN-only tools instead of the live online dashboard. In this guide, Start the LAN App narrows that work to how to start FPH LAN EMS, sign in, import an event, and give operators the correct local URLs. Because this is a basics page, read it as part of the EMS LAN learning path rather than as an isolated checklist.

EMS LAN keeps an event moving when internet access is unreliable, but it also creates a second place where event records can change. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What This Task Changes

This is a practical workflow. Read it from top to bottom the first time: the early checks set scope, the middle steps make the change, and the final checks prove the result. The intended readers are Server operators, Event leads, and LAN admins. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /login, /control-room, /admin/:eventId/:surface, and /workspace/:eventId/:surface.
• Records or contracts involved: Local SQLite database, Bootstrap credentials, Imported events, and Local sessions.
• Main care point: Watch for losing track of which file, device, person, or import is trusted while attendee, staff, inventory, POS, or check-in records change offline.
• Proof worth keeping: event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note.

Follow The Work In Order

1. Confirm the exact scope before opening the tool: Begin by naming the EMS LAN situation, the owner, and the exact item involved in Start the LAN App.
2. Read the visible state before editing anything: Use /login, /control-room, /admin/:eventId/:surface, and /workspace/:eventId/:surface to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Make only the change this guide describes: Keep Local SQLite database, Bootstrap credentials, Imported events, and Local sessions in view so the work stays tied to the records or contracts it can affect.
4. Verify the result where another operator would look: Before handing off, save proof such as event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note so the next lead can tell which file and device state are trusted.

Finish With Proof

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on offline files, check-in access, staff rosters, inventory counts, POS totals, and import history.
3. Proof is findable: The handoff points to evidence that the next lead can tell which file and device state are trusted.

End-to-end operator runbook

Use this numbered runbook to bring the actual fph-lan-ems app online.

1. Step 1 - Start from the live event record. Start from the LAN host machine and confirm it is the machine intended to hold .lan-data/. This makes one host the source of local truth.
2. Step 2 - Gather prerequisites before touching files or devices. Choose the launch mode: pnpm start, pnpm start:lan, packaged executable, or Android wrapper connecting to an already-running host. This prevents starting the wrong runtime.
3. Step 3 - Carry out the operator action slowly. Start the runtime, open /login, use the bootstrap or local account credentials, and import the event snapshot or live link. This creates the local operating event.
4. Step 4 - Watch for side effects on people and records. Confirm operators use the advertised admin, workspace, and API URLs, preferably HTTPS with the local root certificate installed when media features are needed. This prevents broken scanner, mic, camera, notification, and LiveKit workflows.
5. Step 5 - Verify the result in the right place. Open /control-room, check imported events, native capability state, HTTPS status, and communications media status. This proves the app is ready for operators.
6. Step 6 - Hand off the result with context. Give staff the correct admin or workspace URL and their local account or machine-token flow. This starts event operation with known access.

Startup choices

Startup path	Use when
pnpm start	Development or direct local runtime testing.
pnpm start:lan	Built LAN runtime with public LAN serving behavior.
Packaged executable	Event production host where Node commands should be hidden.
Android APK wrapper	Staff phone or tablet connects to the central LAN host.

First-login notes

1. Action 1. Find bootstrap credentials in .lan-data/bootstrap-credentials.json on first startup. Confirm the event ID, file, or device state before continuing.
2. Action 2. Sign in as admin and create named local users for operators. Check the offline proof before moving on.
3. Action 3. Import an event snapshot or use live-link import before opening event surfaces. Keep the sync history or import summary visible.
4. Action 4. Confirm workspace and admin routes load for the imported event. Confirm the event ID, file, or device state before continuing.