Since invitations from an aircraft's Access page only worked for existing
accounts, they did almost what "Add by email" does. The Access page keeps
adding people by email; new people come through the administrator (Admin
→ Users or Admin → Invitations), and outside mechanics through an Owner's
signing invitation.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ported from the original (InvitationCode), adapted to configurable roles.
- Admin → Invitations: a label, optionally one email address (only it can
use the link, and it's emailed) and a name, how many uses (or
unlimited), an expiry (or never), and a role on any aircraft (or none,
for an account only).
- An aircraft's Access page: whoever manages its people invites to that
aircraft, with only the roles they can give; they see and revoke its
invitations.
- /join/<code>: shows what it gives; create an account (when password
sign-in is on) or sign in, then accept. Existing accounts and SSO users
accept too. A role someone already has on an aircraft stays.
- Roles are given as the invitation's creator (AircraftAccess), and only
while they can still manage that aircraft's people. Codes are kept as
digests and shown once; uses are counted under a lock; account creation
and accepting are rate-limited; any invalid link gets the same answer.
- Docs: guide (Administration, Access & sharing), README, and why /join
isn't on the Authentik bypass list. The README's not-yet-ported list
now names Prometheus metrics, and no longer claims oil analysis import
as new.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What people can do on an aircraft now comes from their role there, and
administrators set what each role allows (Admin → Roles).
- Roles are installation-wide sets of permissions (31, grouped as flying,
squawks and notes, maintenance records, imports and exports, the
aircraft, notifications). Seeing an aircraft's records needs none.
- Built in: Owner (always every permission, so an aircraft can always be
managed), Mechanic (shop maintenance: logbook, signing, components,
inspections, ADs, squawks, reminders), Pilot (what pilots could do
before) and Viewer (view only). Administrators can change all but
Owner's, and add their own; a role can be deleted once nobody has it.
- Existing owners and pilots keep exactly what they could do.
- Admin → Users → a user lists their role on every aircraft, to change,
remove or add. On the aircraft's Access page, anyone who manages people
hands out roles, but only an Owner can give or take away Owner, nobody
changes their own (except administrators), and an aircraft always
keeps an Owner (AircraftAccess).
- Controllers declare the permission each action needs; a request that
changes something with none declared is refused (and raises in
development and tests), and a test walks every route to check.
- Weekly reminders and overdue alerts go to roles that get reminders;
the DRS reminder also needs Manage ADs. The API follows the person's
role; its owners_only error is now not_permitted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Views use lazy t(".key") lookups; sentences with values or links stay
whole (interpolation, _html keys); counts use one/other plurals
- Stored-value labels (statuses, types, priorities...) are LabelSets read
from labels: in the current locale; field names and validation messages
under activerecord:; flash and activity text under flash:
- Services, models, helpers, mailer subjects, the logbook PDF, procedures
templates, records package README and transcription warnings localized;
the PDF reuses LogbookEntry#certification_statement instead of a copy
- Scripts read js: strings from a JSON tag via app/javascript/i18n.js
- Dates through I18n.l (app, weekday, month_year, long formats); html lang
follows the locale
- APP_LOCALE picks the language (falls back to English); missing
translations raise in development and tests
- README: Translating section and APP_LOCALE
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>