BE-398: Remove hardcoded database names from environment files

[TimDiekmann]

🌟 What is the purpose of this PR?

Remove hardcoded database name environment variables from configuration files

🔍 What does this change?

• Removes database name environment variables from .env.development and .env.test
• Removes database name overrides from GitHub workflow files

Pre-Merge Checklist 🚀

🚢 Has this modified a publishable library?

This PR:

• does not modify any publishable blocks or libraries, or modifications do not need publishing

📜 Does this require a change to the docs?

The changes in this PR:

• are internal and do not require a docs change

🕸️ Does this require a change to the Turbo Graph?

The changes in this PR:

• do not affect the execution graph

🛡 What tests cover this?

• Existing CI workflows will validate the changes

❓ How to test this?

1. Checkout the branch
2. Run the application in development mode
3. Confirm that database connections work correctly without the hardcoded database names

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hash	Ready	Preview, Comment	Feb 13, 2026 4:19pm
hashdotdesign	Ready	Preview, Comment	Feb 13, 2026 4:19pm
hashdotdesign-tokens	Ready	Preview, Comment	Feb 13, 2026 4:19pm
petrinaut	Ready	Preview	Feb 13, 2026 4:19pm

[cursor]

PR Summary

Low Risk
Config-only changes that remove overrides; risk is limited to dev/CI breaking if any environment still implicitly relied on the old database names.

Overview
Removes hardcoded Postgres database name env vars from .env.development and .env.test, relying on defaults/overrides instead.

Updates CI workflows (test.yml, bench.yml) to stop injecting HASH_GRAPH_PG_DATABASE into .env.local/job env when bringing up external services.

^{Written by Cursor Bugbot for commit 7b5761c. This will update automatically on new commits. Configure here.}

[TimDiekmann]

• BE-398: Remove hardcoded database names from environment files #8418 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[augmentcode]

🤖 Augment PR Summary

Summary: Removes environment-specific Postgres database name overrides from development/test env files and CI workflows.

Changes:

• Deleted hardcoded `*_PG_DATABASE` values from .env.development and .env.test so defaults come from the base .env / app defaults.
• Removed HASH_GRAPH_PG_DATABASE overrides in GitHub Actions bench/test workflows when launching external services.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

Removing the test_* DB name overrides means external-services:test will now use the same Postgres database names as development (via .env defaults), which may no longer match the README claim that test mode avoids polluting the dev DB. If that isolation is still required, it’s worth double-checking there’s another separation mechanism (different DB names/ports/project/volume) after this change.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[codspeed-hq]

Merging this PR will not alter performance

✅ 21 untouched benchmarks
🗄️ 12 archived benchmarks run¹

---

_{Comparing t/be-398-remove-envdevelopment-custom-db-identifier (7b5761c) with main (c8e4ac9)²}

Footnotes

1. 12 benchmarks were run, but are now archived. If they were deleted in another branch, consider rebasing to remove them from the report. Instead if they were added back, click here to restore them. ↩

2. No successful run was found on main (c5edd55) during the generation of this report, so c8e4ac9 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[indietyp]

@indietyp approved this PR from Slack with Graphite

[indietyp]

@indietyp approved this PR from Slack with Graphite