Skip to content

feat: onboard to dotenvx for env loading#61

Open
CaseyHoover wants to merge 1 commit intomainfrom
onboard-dotenvx
Open

feat: onboard to dotenvx for env loading#61
CaseyHoover wants to merge 1 commit intomainfrom
onboard-dotenvx

Conversation

@CaseyHoover
Copy link
Copy Markdown
Owner

Summary

  • Swap tsx --env-file and bare Prisma/vitest-ui invocations for dotenvx run, letting a single root .env.local feed every workspace task.
  • Add .env.example as a checked-in template; update .gitignore so .env.keys and .env.local stay ignored while .env.example and future encrypted .env.* files are committable.
  • Document the dotenvx workflow (including dotenvx set for encrypted values and the DOTENV_PRIVATE_KEY_* production pattern) in README and root CLAUDE.md.

Closes #58.

Test plan

  • pnpm build — all 3 tasks green
  • pnpm lint — all 5 tasks green
  • pnpm test — 20/20 tests pass
  • pnpm format:check — clean
  • Verified dotenvx run --convention=nextjs injects .env.local at root and dotenvx run -f ../../.env.local works from apps/api / packages/db

🤖 Generated with Claude Code

Replace `tsx --env-file` and raw Prisma invocations with `dotenvx run`, so
every workspace task pulls from the single root `.env.local`. This unlocks
encrypted env files (`dotenvx set` / `DOTENV_PRIVATE_KEY_*`) and removes
the need for per-package `.env.local` duplicates.

Closes #58

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Onboard to dotenvx

1 participant