Allowing path prefixes in web_listen_uri so web interface is accessible via path != "/" #2440
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
Export web app prefix in generated `config.js`
|
Extensively rebuilt everything at least 5 times: works fine now 👍 |
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.
We are now utilizing webpack's runtime path resolution for chunks which are loaded on demand to allow configuring a
web_listen_uriin the config file which includes a path.This is useful where setups where the web interface is supposed to be accessible via something like
http://example.org/graylog.Fixes #2271
Caution: The way it works right now, it seems that the changes made to URLUtils.js require plugins to be rebuilt to work.