fix(dashboard): proxy API in Traefik image#131
Open
aqilaziz 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
1 participant
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
Adds same-origin proxying for dashboard API and Socket.IO traffic in the Traefik dashboard image.
dashboard/Dockerfile.traefikpreviously generated an nginx config that only served the SPA. The dashboard calls/api/...from the browser, so deployments behind an external reverse proxy would send API validation requests back to the dashboard container and show Invalid API Key even when the key was valid.This forwards:
/api/toopenwa-api:2785/socket.io/toopenwa-api:2785Type of Change
Checklist
Screenshots (if applicable)
N/A
Related Issues
Closes #116
Testing
git diff --check