I would like to serve Dremio under a path e.g. example.com/dremio but it seems to me Dremio 19.0.0 doesn’t support it.
While I can deploy an nginx proxy with URL rewrite rule, so the dremio/ part will be removed from the request, the UI still tries to download css and js files from example.com instead of example.com/dremio.
Can you add this feature please or guide me how to configure Dremio in this case?
You would have to open the dremio-dac-ui JAR file and edit rest/dremio_static/index.html - the links we generate are absolute.
Thanks, I’ve found it. I guess I could do that, but that would also add to the maintenance cost when upgrading Dremio.
If you guys find the time, it would be great to have a config for this in dremio.conf
I tried this, and it just leads to more trouble further down the road.
It loads all style sheets and javascripts referred to in index.html, but network debugging shows errors further down the road, trying to load /static after the root url again, probably from within those javascripts. Upon adding /static too in nginx to point to the right location, finally I end up with a blank page and a few errors and warnings:
Failed to load resource: the server responded with a status of 404 () o31066.ingest.sentry.io/:1
frame-modern.845d2f4b.js:1 [Intercom] The App ID in your code snippet has not been set. Set it to your App ID found in settings to complete installation: https://app.intercom.com/a/apps/_/settings/web
I think it’s a real pity that Dremio OSS does not support deployment behind a proxy.
Nowadays k8s clusters very often listen on one url, do ssl offload and have multiple apps running on different baseUrl’s.
I was hoping to make Dremio part of our data pipeline stack, but I just can’t make it work because of this.