mirror of
https://github.com/rickbarrette/simple-aircraft-manager-rails.git
synced 2026-11-17 23:50:36 -05:00
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>
8 lines
382 B
Ruby
8 lines
382 B
Ruby
# Record the running software version (Admin → About) once the app is up.
|
|
Rails.application.config.after_initialize do
|
|
next unless defined?(Rails::Server) || ENV["SOLID_QUEUE_IN_PUMA"]
|
|
AppRevision.touch_current! if ActiveRecord::Base.connection.data_source_exists?("app_revisions")
|
|
rescue StandardError => e
|
|
Rails.logger.warn("[app revisions] #{e.class}: #{e.message}")
|
|
end
|