What problem does it solve?
Keeps Lighthouse env handling aligned with apps/api and apps/web startup validation. Use when changing Lighthouse env loading, .env.api/.env.web examples, or app validation requirements.
Core Features & Use Cases
- No defaults in Lighthouse managers: ApiManager and WebAppManager must pass process.env through without hardcoded defaults.
- Env files are split: .env.api for API, .env.web for web.
- App validation is authoritative: if app validation changes, update .env.api.example / .env.web.example and docs.
- Files to Update When Validation Changes: update listed examples and docs to reflect changes.
- Notes: Keep .env formatting consistent (double quotes for non-empty values). Use Lighthouse docker env values from tools/web-perf/lighthouse/docker/env/db.env. When app/env validation changes in apps/api or apps/web, update the Lighthouse examples and re-check the Lighthouse startup flow.
Quick Start
Align Lighthouse env handling by reviewing changes to apps/api and apps/web startup validation and updating the listed Lighthouse environment examples and docs accordingly.