🐛 bug: Nginx does not route correctly using the docker image#96
Open
Paul2803k wants to merge 5 commits intodevelopmentfrom
Open
🐛 bug: Nginx does not route correctly using the docker image#96Paul2803k wants to merge 5 commits intodevelopmentfrom
Paul2803k wants to merge 5 commits intodevelopmentfrom
Conversation
e7b17d1 to
8cfc844
Compare
Paul2803k
commented
Feb 12, 2026
- we also allow the user to set backend url and listening ports
8cfc844 to
304ab22
Compare
Paul2803k
commented
Feb 12, 2026
304ab22 to
ea4447e
Compare
MaartendeKruijf
requested changes
Feb 19, 2026
ea4447e to
304ab22
Compare
…tly-using-the-docker-image
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
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.
Description
In this PR we fix the reported issue. We also add the possibility for the user to point to SOARCA backend and to set the listening port of the GUI, for both the non docker and the docker builds.
Implementation
BrowserRouterdirectly in the browser. We then fixed the issue by configuring NGINX to always point to the application entry point for every route so that the application can handle it.api/foorequests from the app to the SOARCA backend to an IP address set by the user while stripping theapipart. When the app is served byVitewe configured theViteserver to do the same.docker-composefiles to set the listening port of the application and the SOARCA backend.