You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Write docs/environment-variables.md: one table of every environment variable across all four apps — name, which app reads it, required vs optional, default, and what breaks if it is wrong. Source it from apps/backend/src/config.ts, .env.example, apps/backend/src/config/rateLimits.ts, the NEXT_PUBLIC_* vars in apps/web, and the AI agent's settings.
Acceptance criteria:
Every variable in .env.example appears, plus any read directly via process.env that .env.example omits
Marks which variables are validated at boot by config.ts (crash on start) vs. read lazily (silent misbehaviour)
Flags secrets explicitly and states they must never be committed
Notes which NEXT_PUBLIC_* values are compiled into the client bundle and therefore public
@fathiaoyinloye has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
Hi, I'd like to work on this issue. I have relevant experience with the technologies and concepts involved, and I'm confident I can make the necessary implementation to ensure the it meets the acceptance criteria. I'd be happy to contribute to this task.
@KodeSage has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
please assign this issue to me.
I’d like to work on this issue because environment variables are one of those parts of a system that can look simple but have a major impact on whether an application actually works correctly.
Congratulations, @KodeSage! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @KodeSage: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
😎 @KodeSage: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
Activity
fathiaoyinloye commentedon Aug 29, 2026
@fathiaoyinloye has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @fathiaoyinloye to this issue.
KodeSage commentedon Sep 28, 2026
@KodeSage has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @KodeSage to this issue.
drips-wave commentedon Sep 28, 2026
Congratulations, @KodeSage! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @KodeSage: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
github-actions commentedon Sep 29, 2026
Closed by #613, merged into
dev.drips-wave commentedon Sep 29, 2026
This issue has been completed by @KodeSage as part of the Stellar Wave Program's 9th Wave 🥳
😎 @KodeSage: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.