SAM_VIEWER=true (set only by the records package's
viewer/docker-compose.yml) makes the app a read-only copy of an archive,
for whoever receives the records: `docker compose up`, then open
http://localhost:3000.
- At start (bin/docker-entrypoint → sam:viewer:prepare) the package's
.sam.zip, mounted read-only, is imported once.
- No sign-in: everyone browses as a built-in account. Nothing can be
changed: any request but GET/HEAD is refused, no role permission
applies (so no edit buttons), and there's no sign-out or profile. A
banner names the archive and when it was exported.
- It refuses to start, and every page answers 503, when the database
has any other account, so turning it on for a real installation stops
the app instead of exposing its records.
- The viewer listens on 127.0.0.1 only, and skips scheduled jobs
(reminders, backups, AD searches).
- Docs: the package README (three steps now), Access & sharing, README
settings and features, the suggested recordkeeping procedures.
Checked end to end with a built image and a real records package: the
archive imported at start, pages browsed without an account, a change
refused, and the container refusing to start once an account existed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The viewer/docker-compose.yml in the records package (and the package's
README) said to just create an account, but first-run setup asks for a
one-time code from the log since 2026.11.5; both now say how to get it,
and the right menu for importing. The viewer runs the published image at
the release that made the package (each release is published under its
version), so whoever opens it later gets that version, not whatever
:latest is then. APP_IMAGE, for a fork, is used as it is.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Setup checklist on a new aircraft's Overview (owners): components,
standard inspections, DRS AD import, registration/airworthiness
certificate, weight and balance; hideable per device
- Log Flight: "Save and log next leg" reopens the form on the same date,
starting where the leg ended
- Component form: limits in two collapsible groups (replacement and expiry;
overhaul and TBO), open when in use
- Squawk form warns what "Ground Aircraft" does
- Logbook entry form: inspection result only for inspection entries
(show-when controller); document names default from the file
- Dates in pickers, the activity log, airworthiness lines, search, audits
and transcription notes use the app format
- No duplicate Report Squawk button on Squawks; "Record service" label
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The viewer compose uses the published image (from docker-compose.image.yml)
and a throwaway secret key, plain HTTP on localhost.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Packaged HTML opened from disk had no charset, so browsers guessed
Windows-1252 and em dashes showed as mojibake; Excel does the same with
CSVs that lack a BOM.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Inlining CSS used String#sub with a replacement string, so "\&" in
escaped selectors became "</head>"; use block replacements
- Packaged status report and procedures omit the Back link, the print
button and the favicon link (they don't work outside the app)
- Status report: "On condition (Part 91)" as Tracked as, with remaining
hours shown for reference; on condition clears the hard-limit flag
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AC 120-78B chapter 3:
- Every change to logbook entries, sub-components, signatures, inspection
records, AD compliance, major records, W&B, components, squawks and
documents is kept as a RecordVersion (who, IP, when, field changes),
hash-chained per aircraft; versions can't be edited or deleted. Shown on
each logbook entry and in Activity -> Record history
- Nightly job: SQLite online-backup copy to storage/backups, verified
(integrity_check + record counts), pruned to the configured number; then
an integrity check of the history chains and every signature's seal and
fingerprint. Results on Admin -> About ("Back up and check now"); admins
are emailed on failure
- Software versions recorded (first/last seen) on Admin -> About
- Records package (Access & Sharing): logbook entries PDF with signatures,
signatures.csv, record-history.csv, self-contained status report HTML,
the .sam.zip, and a README, for the FAA/NTSB or a buyer
- Legacy (paper) records: documents can be marked as legacy records;
aircraft have an "electronic records since" date (status report, package)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>