Documentation
Event-day operations
A start-to-finish runbook for the day of the event, including backups.
This runbook covers the day of the event: a dry run to catch surprises early, the operating routine while the event runs, and the backups that protect your data afterward.
Dry run (before doors open)
- Test a normal participant end to end.
- Test a participant with a hold.
- Test a VIP participant, if the event uses VIP handling.
- Test a duplicate scan or an already-completed participant.
- Test one supervisor override.
- Confirm live reports and exports look right.
- Back up the database after final setup.
Event-day operation
- Start the host computer first and launch Memoria.
- Confirm the station URL has not changed. If it has, copy the new URL to the station laptops.
- Start the station laptops and sign staff in.
- Keep the event lead or a supervisor on the Admin Dashboard.
- Resolve holds through the app instead of editing source files during the event.
- Export final reports before closing the app.
- Back up the database immediately after the event.
Resolve exceptions in the app, not in spreadsheets. Editing source files mid-event creates drift between what staff see and what's recorded. Route every hold and override through Memoria so the ledger stays the single source of truth.
Backups
On the on-site profile, the database lives at ~/.memoria/memoria.db on the host. Back
it up after final setup and again immediately after the event, and store the copy with your other
delivery notes. On the hosted profile, backups are managed for you in the cloud.
Handoff package
When wrapping up an implementation, hand the school these items:
- Installer version and release link.
- License key and expiration/edition details.
- Admin account handoff instructions.
- Station URL and network notes used during the dry run.
- Source import file or export query description.
- Final setup backup and its location.
- The event quick-start for the selected event type.