Enable running Graylog REST API on different context path #2634
Motivation and Context
Users might (rightfully) want to run the Graylog REST API and the web interface on the same network listener with the web interface being served on the root context path (
This PR merges
How Has This Been Tested?
Things that might still be broken and might only be working on my machine™:
Types of changes
StreamAlertReceiverResource had the same @path annotation as StreamAlertResource which ultimately led to duplicate Resource models and Jersey throwing exceptions.
I've tested the following combinations with 2 nodes:
The only thing that currently does not work is to put the web listener on a separate IP/Port. The assets then all end up in a 404.
* Update dev config.js to new default since merging #2634 the default config.js isn't working with npm start anymore * Serve assets from "/" when running in development mode - Introduce `AppConfig.gl2DevMode()` - Use the function in Navigation.jsx instead of checking for the global variable directly