Environment Variables

ValGuide uses three env sources:

Local Development

This public repo does not ship real secrets. For local work, copy .env.local.example to .env.local and edit the values you need.

The public repo does not include a built-in secret loader. Provide local env values via your shell, direnv, your preferred dotenv tool, or CI/platform configuration.

Runtime vs Build-Time

• VITE_* variables are build-time values baked into the browser bundle.
• non-VITE_* variables are server/runtime values read through process.env.
• sensitive values such as DATABASE_URL, BETTER_AUTH_SECRET, ADMIN_ALLOWED_EMAILS, and raw admin bootstrap passwords should come from provider-side secret stores or one-shot shell input, not from tracked files.

Wrangler Config

The checked-in wrangler.jsonc files are public-safe examples plus app structure. They may still contain placeholder binding IDs that you must replace with your own Cloudflare resources before deploying.

Adding a Variable

1. Add it to packages/core/env/schema.ts.
2. Decide whether it is build-time (VITE_*) or runtime.
3. Document a local example value in .env.local.example or .env.selfhost.example if contributors need it.
4. Add CI or provider-side secret configuration for deploys.