Move static content to oauth2-proxy-static to avoid name collisions (#2223) #2358
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
Renamed the static folder to oauth2-proxy-static, so that content hosted by underlying application on /static can still be accessed.
Motivation and Context
Jupyter hosts resources on /static
Closes #2223
How Has This Been Tested?
Tested locally against the configuration that I use in production. Basically like this:
Built it like this:
ran it like this:
And for my local testing I had to add some more settings:
"--tls-cert-file=mycert.crt"
"--tls-key-file=mycert.key" \
Checklist: