Skip to content

Web build, runtime configuration, and environment variables #629

Closed
Closed
Web build, runtime configuration, and environment variables#629
Assignees
bandanadivya
Labels
Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentationdxfrontend

Description

@codebestia
codebestia
opened on Oct 19, 2026

Branch: Open your PR against dev. PRs targeting main are closed automatically.

Description:
Write apps/web/docs/build-and-config.md: next.config.ts, how NEXT_PUBLIC_* variables are inlined at build time, how the search Web Worker and any WASM dependencies are bundled, and scripts/start-web.sh.

Acceptance criteria:

  • Every NEXT_PUBLIC_* variable the code reads — API_URL, BACKEND_URL, SOCKET_URL, AUTH_TOKEN, NETWORK, NETWORK_PASSPHRASE, SOROBAN_RPC_URL, TOKEN_TRANSFER_CONTRACT — with its consumer and default
  • Documents the inconsistencies found while writing it: lib/api.ts defaults to port 4000 while NewConversationModal.tsx defaults to 3001, and REST uses NEXT_PUBLIC_API_URL while sockets use NEXT_PUBLIC_BACKEND_URL
  • Explains that these values are baked in at build time and cannot be changed per environment without a rebuild
  • Cross-linked from the repo-wide environment variable reference (feat: migrate message insert paths to ciphertext + envelopes  #312)

Activity

  1. codebestia
    added
    documentationImprovements or additions to documentation
    frontend
    dx
    on Oct 19, 2026
  2. drips-wave
    added
    Stellar WaveIssues in the Stellar wave program
    on Oct 19, 2026

  3. Mawuli-tech commented on Oct 20, 2026

    @Mawuli-tech
    Mawuli-tech
    on Oct 20, 2026 – with Drips Wave

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

    I would like to work on this issue

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

  4. codebestia
    added a commit that references this issue on Oct 22, 2026

    docs: X3DH/Double Ratchet implementation notes, device-linking flow, …

    b4eb9f8

  5. aemmanueloke commented on Oct 22, 2026

    @aemmanueloke
    aemmanueloke
    on Oct 22, 2026 – with Drips Wave

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

    I'd like to take this issue. It covers an important part of the project, and I want to contribute something that fits the existing architecture and development standards and holds up over time.

    I've worked across backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I'm comfortable reading an unfamiliar codebase, tracking an issue down to its root cause, and writing clean fixes with tests that guard against regressions.

    My plan is to start by reading the existing implementation and project conventions, then build the solution in small, focused steps. I'll test the changes, document them where needed, and keep the code simple so nothing existing breaks. I'll also respond quickly to review feedback so the PR is easy to merge.

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

  6. bandanadivya commented on Oct 22, 2026

    @bandanadivya
    bandanadivya
    on Oct 22, 2026 – with Drips Wave

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

    Hi Maintainer, I’ve reviewed this issue and understand what needs to be done. I’m confident I can handle it. Please assign it to me. Thank you!

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

  7. codebestia
    assigned
    bandanadivya
    on Oct 22, 2026

  8. drips-wave commented on Oct 22, 2026

    @drips-wave
    drips-waveBot
    on Oct 22, 2026 – with Drips Wave

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

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

  9. github-actions commented on Oct 22, 2026

    @github-actions
    github-actionsBot
    on Oct 22, 2026 – with GitHub Actions

    Closed by #686, merged into dev.

  10. github-actions
    closed this as completedon Oct 22, 2026

  11. drips-wave commented on Oct 22, 2026

    @drips-wave
    drips-waveBot
    on Oct 22, 2026 – with Drips Wave

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

    😎 @bandanadivya: 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

Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentationdxfrontend

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions