MerginMaps / MerginMaps/server
All server Releases pinned to 2025.7.3 Tag
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 179
- Forks
- 71
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Hello Mergin Team, first of all thank you for providing such a great piece of software.
I have a question though: How do Docker Tags and the tags e.g. in Github relate?
For example on master the docker-compose.yml points to 2025.7.3 while the latest tag on Github is 2026.6.3.
I found this issue (https://github.com/MerginMaps/server/issues/540) saying that the docker compose might sometimes not be up-to-date, but 2025.7.3 seems to be also the latest tag on Dockerhub.
The main reason I am asking: I want to build the docker images with PUBLIC_PATH so I can host behind a path. So I need to know which source code corresponds to the correct version.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the image tag in docker-compose.yml with the GitHub releases and DockerHub tags mentioned in the issue. Trace how server releases and Docker image tags are produced, then clarify or correct the version mapping so the compose configuration identifies the intended source version and PUBLIC_PATH builds are reproducible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100