Feature/allow testing of different branches with docker - #102
Merged
Conversation
…-multiple-branches,-PRs-through-docker
prasad-sawantdesai
requested review from
SimonPinches,
Yannicked,
maarten-ic and
olivhoenen
as code owners
July 1, 2026 08:36
olivhoenen
approved these changes
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For isolated branch and pull-request deployments backed by separate PostgreSQL and Redis volumes
The standard allocation is
mainon port 5000,developon port 5100, and pull requests on ports 5101-5999.These instances use the development-only Docker and Compose files and expose their branch identity at
/__simdb_instance.http://10.154.84.240:5101/v1.2/docs
http://10.154.84.240:5101/__simdb_instance