2 Commits

Author	SHA1	Message	Date
josh	0dc84c7597	fix: bypass Data Cache on live park/ride pages so navigation shows fresh data ... The ride detail and park pages fetched with `next: { revalidate: 60 }`, which is stale-while-revalidate. After hours of no traffic the Data Cache held a morning snapshot; the first click served that stale value and only the second request (e.g. a browser refresh) got the just-revalidated payload. The endpoint also bundles live state with chart history, so one stale fetch made the whole page wrong. Switch the live-data fetches to `cache: "no-store"`. The calendar-month fetch keeps its 5-min ISR since operating hours change slowly.	2026-06-01 21:06:58 -04:00
josh	5d9daee627	refactor: production-essentials hardening pass ... Backend: structured logger, env-validated config, graceful SIGTERM/SIGINT shutdown, per-IP rate limiter, per-tier scheduler concurrency latch, error context on previously-silent catches, compiled-JS Dockerfile stage. Frontend: lib/api.ts consolidates BACKEND_URL with lazy production-required check, root + per-segment error.tsx / not-found.tsx / loading.tsx, generateMetadata on park and ride pages, graceful fallback when backend is unreachable, Plausible script gated on env vars. Infra: CI runs lint + typecheck + tests on both packages before docker build, compose adds healthchecks, log rotation, and memory limits; .env.example documents every variable. Cleanup: removed empty app/api/parks/ dir and 0-byte root parks.db, moved wait-times-urls.txt into docs/, dropped an `as any` cast. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-30 10:17:52 -04:00