- The compose files' steps say where the first-run setup code is (it's
asked for since 2026.11.5), that new accounts come from the admin, and
who adds aircraft; the published image's release tags are mentioned.
- docker-compose.yml passes APP_REVISION/APP_BUILT_AT to the build when
set, so a locally built image shows its build on Admin → About.
- .env.example lists the optional push notification keys, APP_LOCALE and
APP_IMAGE, which the README documented but it didn't.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Anyone can add an aircraft and so manage its people, so invitations from
non-administrators could bring in new accounts without an administrator.
- An invitation makes a new account only if whoever made it is still an
administrator when it's used; an aircraft's Access page invitations are
for people who already have an account (its welcome page says so).
- Signing invitations no longer make accounts: the mechanic needs one
first, and the owner is told when they don't have one.
- With SSO, "Continue with <provider>" on an administrator's invitation
makes the account and accepts the invitation (only for its address when
it has one), so invitations work without OIDC_AUTO_CREATE_USERS. That
setting stays, documented as giving accounts without an invitation; the
Authentik example now leaves it off.
- Docs: who makes accounts (guide, README, Authentik, .env.example, API).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Refuse to start with a placeholder or short SECRET_KEY_BASE (under 32
characters); warn and fail sam:doctor under 64. .env.example no longer
ships a placeholder.
- First-run setup needs a one-time code printed only in the server log, so
only whoever runs the server can create the admin account.
- AirTrail: the server resolves the address and connects to exactly that;
never the server itself or link-local addresses (cloud metadata);
private-network addresses only for admins or hosts in
AIRTRAIL_ALLOWED_HOSTS.
- Host authorization when APP_HOST is set: APP_HOST, the APP_URL host,
ALLOWED_HOSTS, localhost and IP addresses; /up exempt. A blocked name
gets a short explanation instead of a blank 403.
- docker-compose.direct.yml: HTTPS without a proxy via Thruster's built-in
Let's Encrypt (TLS_DOMAIN).
- Notes' Markdown no longer allows the unused class attribute.
- README, .env.example and the user guide updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Requests run in the viewer's zone: Profile -> Time zone, else their
device's (a tz cookie set from the browser), else the installation's;
times show in it and "today" is the local date (a new flight's date)
- Docker's TZ sets the installation zone (default UTC): scheduled jobs run
on its clock (recurring.yml), and it's used before a device's zone is known
- The weekly reminder email is worked out in the recipient's zone
- Signatures, record history and exports keep exact UTC timestamps
- users.time_zone; README, .env.example and guide updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Oil analysis: Blackstone PDF import (20 elements, oil properties, universal
averages), results stored per element, oil type, "leave out of trends",
the original app's statuses; AvLab fixes (multi-line comments, unrelated
labels no longer steal values). Existing records migrate.
- Aircraft archives in the original app's .sam.zip format (schema v2): export
from Access & Sharing, background import from the Fleet page, rake tasks.
Archives move both ways between this app and the original.
- Scanned logbook pages (images or PDFs) upload as a document; with
ANTHROPIC_API_KEY set, Claude transcribes them into logbook entries.
- Fix: deleting a component or aircraft failed when AD compliances or
inspection records pointed at a component.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Rails 8.1 + SQLite rewrite of marbindrakon/simple-aircraft-manager,
designed to self-host as a single container (Solid Queue/Cache/Cable,
Active Storage on disk, Hotwire + importmap, Tailwind).
- Airworthiness engine ported from health/services.py (ADs, grounding
squawks, inspection recurrency, component replacement)
- Hours updates and flight logs cascading to in-service components,
optional airworthiness enforcement
- Components, squawks, ADs, inspections, logbook, documents, major
records, oil/fuel consumption stats and charts, activity log
- Admin/owner/pilot RBAC and public share links (status/maintenance)
- Docker Compose and Kamal deployment, env-driven production config
- Service and integration tests
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>