Skip to content

[Repo] Align the documented PostgreSQL version with docker-compose (15 vs 16) #1457

New issue
New issue
Closed
#1528
Closed
[Repo] Align the documented PostgreSQL version with docker-compose (15 vs 16)#1457
#1528
Assignees
kike-alt
Labels
Stellar WaveIssues in the Stellar wave programdockerDocker containersdocumentationImprovements or additions to documentationgood first issueGood for newcomers

Description

@BigBen-7
BigBen-7
opened on Oct 12, 2026

Found in a repository audit of main (b472e6b). The facts below were checked against that commit.

Problem

docker-compose.yml runs postgis/postgis:16-3.4-alpine, while the Backend README states PostgreSQL 15 and the manual setup uses postgis/postgis:15-3.3. Contributors test against different versions.

Fix

Pick one version (16 is what compose uses), update the README and any CI or script that pins the other.

Acceptance criteria

  • README, compose and CI agree on one major version

Notes

Scope: Light (about half a day or less). Location: docker-compose.yml, Backend/README.md.

Activity

  1. BigBen-7
    added
    documentationImprovements or additions to documentation
    good first issueGood for newcomers
    dockerDocker containers
    on Oct 12, 2026

  2. rupesh-kumar-sah commented on Oct 13, 2026

    @rupesh-kumar-sah
    rupesh-kumar-sah
    on Oct 13, 2026

    Hi maintainers,

    I reviewed "[Repo] Align the documented PostgreSQL version with docker-compose (15 vs 16)" and have a structured approach ready for implementation:

    Technical Implementation Outline:

    1. Investigate workflow execution logs, environment secrets, and failure exit triggers.
    2. Fix pipeline step sequencing, runner/container configuration, and build artifact caching.
    3. Perform local validation of CI/CD configuration to confirm deterministic behavior.
    4. Ensure automated pipeline triggers and deployment workflows run 100% green without failures.

    Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!

  3. drips-wave
    added
    Stellar WaveIssues in the Stellar wave program
    on Oct 17, 2026

  4. kike-alt commented on Oct 17, 2026

    @kike-alt
    kike-alt
    on Oct 17, 2026 – with Drips Wave
    Contributor

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

    Hello, I'm interested in taking this issue on.

    This touches PostgreSQL and Docker, which I have hands-on experience with. I'll rewrite the relevant docs to be accurate and clear, matching the existing documentation conventions.

    Planned approach, based on the acceptance criteria:

    • README, compose and CI agree on one major version

    Happy to get started right away if assigned — looking forward to contributing.

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

  5. BigBen-7
    assigned
    kike-alt
    on Oct 17, 2026

  6. drips-wave commented on Oct 17, 2026

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

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

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

  7. BigBen-7
    added a commit that references this issue on Oct 17, 2026

    fix: align PG version, update README/ROADMAP, add lint step to backen…

    34589e5
  8. BigBen-7
    closed this as completedin #1528on Oct 17, 2026

  9. grantfox-oss commented on Oct 17, 2026

    @grantfox-oss
    grantfox-ossBot
    on Oct 17, 2026 – with GrantFox OSS

    🎉 This issue has been marked as completed on GrantFox!

    @kike-alt's PR #1528 was approved and merged by @BigBen-7.

    🏆 @kike-alt: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,185 total points). Track your full progress on GrantFox.

    👏 Great work, @kike-alt! Keep contributing to PinSpace-Org.

  10. drips-wave commented on Oct 17, 2026

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

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

    😎 @kike-alt: 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 programdockerDocker containersdocumentationImprovements or additions to documentationgood first issueGood for newcomers

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions