[Docs] README states Postgres on port 5432 but docker-compose maps 5433

[ogazboiz]

Telegram: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

README.md (Docker section) says docker compose up starts "Postgres database on port `5432`". But docker-compose.yml maps the Postgres container with ports: ["5433:5432"], i.e. it's reachable on host port 5433, not 5432. A contributor following the README who tries to connect a local client to localhost:5432 (or sets DATABASE_URL accordingly) will fail or hit a different/unrelated Postgres.

Acceptance criteria

• Update the README to state host port 5433 (or change the compose mapping to 5432:5432 and keep the README), so doc and compose agree
• Mention the host port in the manual DATABASE_URL example if relevant

Files to touch

• README.md
• (or) docker-compose.yml

Out of scope

• The backend compose env gaps (separate issue).

[Stephan-Thomas]

@Stephan-Thomas has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

hi, i would like to work on this.

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

[Sughter99]

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

Can this be assigned to me? I'd like to work on this

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

[SharifIbrahimDev]

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

Hi @ogazboiz, I’d like to work on this issue.

I can update the documentation and configuration to ensure the README and Docker setup remain fully consistent. I’ll verify the exposed Postgres host port configuration, update the README instructions and DATABASE_URL examples where necessary, and ensure contributors can connect without confusion during local setup.

I’ll also confirm the final setup works correctly with the documented development flow before submitting the PR.

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

[somotochukwu-dev]

@somotochukwu-dev has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Good day maintainer,
Please assign this issue to me
Thanks.

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

[drips-wave]

Congratulations, @SharifIbrahimDev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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

[drips-wave]

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

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