added publicPath to Vue config that sets all public assets to be relative #14
Conversation
This file contains 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
…tive instead of absolute.
|
To replicate this issue we put Kuma in front of a Kong Ingress on AKS (Azure) by exposing only the GUI port (not the API port). When connecting to the GUI, the GUI was not able to fetch the static assets. |
subnetmarco
approved these changes
Mar 31, 2020
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.
This addresses a use case where a user proxies the GUI to a folder, e.g. something like
/kuma-cp/, inside of a Kubernetes container. By default, Vue's asset path is absolute, which makes all assets 404 in this context. This would resolve that.