lighthouse-env-alignment

Align Lighthouse environment loading with API and Web startup validation.

6|5|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/podverse/podverse --skill lighthouse-env-alignment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lighthouse-env-alignment
Source: https://github.com/podverse/podverse/tree/main/.cursor/skills/lighthouse-env-alignment
Command: npx skills add https://github.com/podverse/podverse --skill lighthouse-env-alignment

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about lighthouse-env-alignment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep Lighthouse environment variables in sync with API and web validation?

To align Lighthouse env loading, remove hardcoded defaults from ApiManager and WebAppManager so they pass process.env through directly, then split configurations into separate .env.api and .env.web files.

When do I need to update .env.api and .env.web example files for Lighthouse?

You need to update .env.api and .env.web example files when app/env validation changes in apps/api or apps/web, ensuring Lighthouse examples reflect the new required variables and maintaining consistent formatting with double quotes for non-empty values.

Why should Lighthouse ApiManager and WebAppManager avoid hardcoded env defaults?

Lighthouse ApiManager and WebAppManager must avoid hardcoded env defaults to enforce app validation as the single source of truth. Passing process.env through directly prevents configuration drift between Lighthouse and the API or web apps.

Does Lighthouse environment alignment support separate env files for API and web?

Yes, Lighthouse environment alignment requires splitting env files into .env.api for the API and .env.web for the web app. This separation ensures each service loads only its validated environment variables.

What formatting should I use for Lighthouse env files and docker values?

For Lighthouse env files, keep formatting consistent by using double quotes for non-empty values. Additionally, source Lighthouse docker env values directly from tools/web-perf/lighthouse/docker/env/db.env.