Time zones: each person's own, and TZ for the installation

- 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>
This commit is contained in:
rickyandClaude Opus 5.5 committed 2026-11-14 07:49:22 -05:00
1 parent 03b9ad65cb
commit 9662c7ae16
17 files changed
+156 -12

No files matched your search

+5 -1
View File
@@ -36,7 +36,11 @@ module SimpleAircraftManager
# These settings can be overridden in specific environments using the files
# in config/environments, which are processed later.
#
# config.time_zone = "Central Time (US & Canada)"
# The installation's time zone, from Docker's standard TZ (e.g.
# "America/New_York"): for scheduled jobs and for anyone whose device zone
# isn't known yet. Each person's own zone comes from Profile or their
# device (TimeZones). Not a zone name (unset, or e.g. ":/etc/localtime"): UTC.
config.time_zone = ActiveSupport::TimeZone[ENV["TZ"].to_s] ? ENV["TZ"] : "UTC"
# config.eager_load_paths << Rails.root.join("extras")
# Small resized copies of photos (squawk thumbnails), made with libvips.