Add reverse-proxy subpath support via BASE_PATH env var - #63
Open
drjaska wants to merge 1 commit into
Open
Conversation
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.
Added support for running subsyncarr under a reverse-proxy subpath by adding a new BASE_PATH env var for configuration.
/api/*routes, static assets, and WebSocketwindow.__BASE_PATH__intoindex.htmlas a prerequisite for stuff to work.I didn't catch any regressions for those users who do not set the BASE_PATH env var but I didn't test that thoroughly.
The following Caddyfile for https://example.com/subsyncarr/ should now just work without the need to strip the subpath while proxying.
In the case that I missed something, feel free to let me know!