docker-compose.yml hardcoded credentials

[DeFiVC]

Problem

In docker-compose.yml lines 8-10, database credentials are hardcoded:

environment:
  POSTGRES_USER: chainlearn
  POSTGRES_PASSWORD: chainlearn_dev
  POSTGRES_DB: chainlearn

Even for development, this should reference an .env file via env_file or ${POSTGRES_PASSWORD} variable substitution.

Fix

Use environment variables:

environment:
  POSTGRES_USER: ${POSTGRES_USER:-chainlearn}
  POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-chainlearn_dev}
  POSTGRES_DB: ${POSTGRES_DB:-chainlearn}

Scope

• docker-compose.yml -- use environment variables

Acceptance Criteria

1. Credentials are configurable via environment
2. Default values work for development
3. Existing functionality is not affected

Technical Context

• docker-compose.yml:8-10 -- hardcoded credentials

[Ashborne267]

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

please give me this issue

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

[Samaro1]

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

Gm gm boss. I would like to take this one on. I can replace the hardcoded Postgres credentials in docker-compose.yml with environment variable substitution and sensible dev defaults, and confirm existing functionality still works unaffected. Please assign it to me.

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

[unlimitedengineer]

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

I’d like to work on this issue. I can refactor the config loading to remove the unsafe Proxy approach and preserve full TypeScript type safety, so invalid config property names fail at compile time while keeping the existing test-mode behavior intact.

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

[nwosum113-ui]

@nwosum113-ui has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello maintainer I want to work on this

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

[drips-wave]

Congratulations, @nwosum113-ui! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@nwosum113-ui's PR #423 was approved and merged by @DeFiVC.

🏆 @nwosum113-ui: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (331 total points). Track your full progress on GrantFox.

👏 Great work, @nwosum113-ui! Keep contributing to ChainLearnOfficial.

[drips-wave]

This issue has been completed by @nwosum113-ui as part of the Stellar Wave Program's 8th Wave 🥳

😎 @nwosum113-ui: 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.