supporting proxies #607
Open
supporting proxies #607
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
gaal-dev
force-pushed
the
support-proxies
branch
2 times, most recently
from
9bd1c82
to
1764226
Compare
gaal-dev
force-pushed
the
support-proxies
branch
from
1764226
to
541e693
Compare
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.
Hello. We deploy backends in Kubernetes and flasgger does not work in this case. Flasgger specs, favicon, swagger_ui_bundle_js, swagger_ui_standalone_preset_js, jquery_js and swagger_ui_css parameters are relative URLs by default. I used this configuration https://github.com/flasgger/flasgger?tab=readme-ov-file#externally-loading-swagger-ui-and-jquery-jscss, but ... specs are relative anyway.