mirror of
https://github.com/rickbarrette/simple-aircraft-manager-rails.git
synced 2026-11-17 15:50:36 -05:00
Offline
- Flights and squawks saved offline are tagged with their user and only sent
while that user is signed in; storage is made persistent; Background Sync
sends them with the app closed (Chromium); unsent count on the app badge
- Report Squawk works offline (photos included, one-time key like flights)
- The Fleet page and, for each of your aircraft, the Overview, W&B, Log
Flight and Report Squawk pages and photo are saved ahead of time, so the
app opens and works without signal; copies say when they were saved
- Sign-out clears saved forms, pages and photos (asks first if items wait)
- Offline page rendered by Rails (localized, follows the theme, no inline
script); service worker version follows the build
Install and notify
- Web Push (web-push gem, VAPID keys from env or storage/vapid_keys.json):
grounding squawks, newly overdue items (daily, once each), signing
requests; per-device on/off and test in Profile -> This device; only
browser push service endpoints accepted
- Manifest shortcuts (Log Flight, Report Squawk via /go/...), lang and
localized description; install help on Profile; reload notice after a
release
Also
- Dockerfile: libssl-dev in the build stage (openssl gem); lockfile checksums
- Leftover English and %{_} interpolation names from the localization pass
- Guide and README updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
27 lines
1.6 KiB
Markdown
27 lines
1.6 KiB
Markdown
# Squawks
|
|
|
|
A squawk is a problem found with the aircraft. Anyone on the aircraft can report one.
|
|
|
|
## Report a squawk
|
|
|
|
**Report Squawk** asks for the issue, a priority, optionally the component, attachments (photos, PDFs) and notes.
|
|
|
|
Without signal (in the installed app: open it, tap the aircraft and **Report Squawk** as usual), the squawk and its photos are saved on the device and sent when the connection is back, like [flights](flights.md#with-no-signal). Sending twice never reports it twice.
|
|
|
|
A **Ground Aircraft** squawk notifies the aircraft's other owners and pilots who turned on notifications.
|
|
|
|
| Priority | Meaning |
|
|
|---|---|
|
|
| **Ground Aircraft** | The aircraft isn't airworthy until it's resolved. |
|
|
| **Fix Soon** | Fix before it gets worse. |
|
|
| **Fix at Next Inspection** | Can wait for the next inspection. |
|
|
| **Fix Eventually** | Minor. |
|
|
|
|
## Defer an inoperative item (91.213(d))
|
|
|
|
For inoperative equipment that isn't required, **Defer** records the decision. You confirm each condition of 14 CFR 91.213(d): not required by the type certificate, equipment list, 91.205 or another rule, nor by an AD; removed or deactivated and placarded *Inoperative*; and that a pilot or mechanic has determined it isn't a hazard. You record who decided and in which role. A deferred squawk no longer grounds the aircraft. **Undo deferral** (owners) reverses it.
|
|
|
|
## Resolve a squawk
|
|
|
|
Owners choose **Resolve**. You can record the fix as a logbook entry at the same time: the date, logbook, airframe total time, work performed and who signed it off. A resolved squawk can be **Reopen**ed.
|