Skip to content

A missing DATABASE_URL silently falls back to localhost credentials #281

Closed

Description

@Ashborne267

Summary

src/db.ts and prisma.config.ts fall back to
postgresql://streamgive:streamgive@localhost:5432/streamgive when
DATABASE_URL is unset, in production as well. A misconfigured deploy
connects to the wrong place, or fails later with a confusing error.

Acceptance criteria

  • Throw a clear error at startup when DATABASE_URL is missing in production.
  • Keep an explicit default only for local development and add a test.

Getting started

Fork this repository, clone your fork, and add this repo as upstream:

git clone https://github.com/<your-username>/streamgive-backend.git
cd streamgive-backend
git remote add upstream https://github.com/StreamGive/streamgive-backend.git

Create a branch for this issue:

git checkout -b fix/database-url-required

Suggested commit message:

fix(db): require DATABASE_URL in production

Run npm run lint, npm run typecheck, and npm test before pushing, then
open a pull request from your fork against main and link this issue. See
the contributing guide for the full contribution guide.

Activity

  1. mijinummi commented on Oct 18, 2026

    @mijinummi
    Contributor

    @mijinummi 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 review the existing implementation, make the required changes, add appropriate tests, and submit a PR. Thank you!

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

  2. drips-wave commented on Oct 18, 2026

    @drips-wave

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

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

  3. github-actions commented on Oct 18, 2026

    @github-actions
    Contributor

    Closed by #341, which was merged automatically.

  4. drips-wave commented on Oct 18, 2026

    @drips-wave

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

    😎 @mijinummi: 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 programbugSomething isn't workinggood first issueGood for newcomers

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions