Hi!
Current State
Assume the following setup:
- Snapweb is exposed under a sub-path by an ingress controller:
https://example.com/snapcast
- Snapcast server's JSON-RPC is exposed as
https://example.com/snapcast/json-rpc by the same ingress-controller
Currently snapweb tries to call wss://example.com/json-rpc to establish a connection and there is no way to modify this behavior without recompiling for every setup.
Proposal
Make the paths for the assets and for the accessed endpoints configurable, e.g. using a config.json or config.js file which is loaded on startup and which can override the defaults.
Using a config.js would allow to generate the paths using variables available at runtime, maybe even headers provided by the reverse-proxy or ingress-controller like X-Ingress-Path.
Thanks!
Jörn
Hi!
Current State
Assume the following setup:
https://example.com/snapcasthttps://example.com/snapcast/json-rpcby the same ingress-controllerCurrently snapweb tries to call
wss://example.com/json-rpcto establish a connection and there is no way to modify this behavior without recompiling for every setup.Proposal
Make the paths for the assets and for the accessed endpoints configurable, e.g. using a
config.jsonorconfig.jsfile which is loaded on startup and which can override the defaults.Using a
config.jswould allow to generate the paths using variables available at runtime, maybe even headers provided by the reverse-proxy or ingress-controller likeX-Ingress-Path.Thanks!
Jörn