Modern env management approach #21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Environment configuration uses .env files. These work but have downsides: easy to misconfigure, not versioned, easy to accidentally commit secrets, no type checking.
What to do
Evaluate and adopt a more robust env management approach.
Options to evaluate
dotenvx— encrypted .env files that can be committed safelyinfisical— self-hosted secrets manager@t3-oss/env-core— Zod-validated env schemas (type-safe, catches missing vars at startup)Acceptance criteria
documentation/decisions.mdNotes
Current env vars are documented in
documentation/deployment.mdunder 'Environment Variables'. Both the API and Docker Compose stack read from .env files.VITE_API_URLis a build-time var (Docker build arg), not runtime.