Skip to content

Add .env.example and document the frontend environment variables #1628

Closed

Description

@yusuftomilola

Problem

The frontend reads NEXT_PUBLIC_API_URL, NEXT_PUBLIC_WS_URL and NEXT_PUBLIC_STELLAR_NETWORK, each with a different hard-coded fallback (6003 / 8000 / testnet), and there is no frontend/.env.example or README section. CI sets yet another API URL (4000).

Proposed change

Add .env.example with all variables and sensible local defaults, document them in a README table, and validate them once at startup with a small Zod schema in lib/env.ts that the rest of the code imports.

Acceptance criteria

  • A new contributor can run the app from the README alone.
  • Missing/invalid values fail fast with a readable message.

Activity

  1. Cynthiaoma commented on Oct 18, 2026

    @Cynthiaoma

    @Cynthiaoma has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello Maintainer, I’m Cynthiaoma, a software engineer experienced in decentralised applications and open-source contributions. I understand the task and would be grateful for the assignment.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Cynthiaoma to this issue.

  2. Morenike20 commented on Oct 18, 2026

    @Morenike20

    @Morenike20 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello, I’ve gone through the issue requirements in detail and am confident I can deliver a well-structured solution that meets the expected acceptance criteria. Kindly assign this issue to me.
    

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Morenike20 to this issue.

  3. mxllv commented on Oct 18, 2026

    @mxllv
    Contributor

    @mxllv has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi, I'd like to work on this issue.

    I'll update the documentation to accurately reflect current behavior, keeping the style consistent with the rest of the docs.

    Planned approach, based on the acceptance criteria:

    • A new contributor can run the app from the README alone.
    • Missing/invalid values fail fast with a readable message.

    Please assign this issue to me, I'd be happy to contribute.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @mxllv to this issue.

  4. drips-wave commented on Oct 18, 2026

    @drips-wave

    Congratulations, @mxllv! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @mxllv: 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 🌊

  5. added a commit that references this issue on Oct 19, 2026
    9b04d00
  6. grantfox-oss commented on Oct 19, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @mxllv's PR #1694 was approved and merged by @yusuftomilola.

    🏆 @mxllv: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,292 total points). Track your full progress on GrantFox.

    👏 Great work, @mxllv! Keep contributing to DistinctCodes.

  7. drips-wave commented on Oct 19, 2026

    @drips-wave

    This issue has been completed by @mxllv as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @mxllv: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions