Join our community: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
backend/.env.example is the canonical reference new contributors copy to .env. If variables consumed in backend/src/config/, backend/src/lib/pg-pool.ts, backend/src/lib/redis.ts, or backend/src/services/sorobanService.ts (e.g. pool size, Redis URL, RPC URL) aren't all listed there, first-time setup fails with unclear "undefined is not a valid config" errors instead of a clear missing-env message.
Acceptance criteria
Files to touch
Out of scope
- Adding runtime env validation (e.g. zod schema) — that's a separate feature
- Changing default values used in code
Why this matters
backend/.env.exampleis the canonical reference new contributors copy to.env. If variables consumed inbackend/src/config/,backend/src/lib/pg-pool.ts,backend/src/lib/redis.ts, orbackend/src/services/sorobanService.ts(e.g. pool size, Redis URL, RPC URL) aren't all listed there, first-time setup fails with unclear "undefined is not a valid config" errors instead of a clear missing-env message.Acceptance criteria
backend/srcfor allprocess.env.*readsbackend/.env.examplewith a sensible placeholder/default and commentFiles to touch
backend/.env.exampleOut of scope