Feature Request: Support Configurable Base Path When Self-Hosting Evidently UI

[robert-inkpen]

Hello,

We are currently self-hosting Evidently UI on our servers and need to integrate it with our existing infrastructure, which includes single sign-on (SSO) and hosting the application under a specific base path.

It would be great if Evidently UI could support configuring a base path when self-hosting, so that all the URLs and static assets correctly reference the base path. This would allow us to host it behind a reverse proxy or under a specific path in our instance.

Thank you!

[Dhavaleswar]

Hi @robert-inkpen did you find any workaround temporarily

[robert-inkpen]

Evidently is in POC phase at our company so for the time being we provisioned it it's own endpoint sitting behind our SSO. Which doesn't allow it to be in our catalogue of tools but gets some of the power users access.
One of the problems is that it has to be managed separately compared to everything else.

[elenasamuylova]

Hi @robert-inkpen, I'm afraid we don't currently have the capacity to implement this feature, but we welcome your contributions here if you are up to it!

Note that we also offer a commercial enterprise version with extra features (available for self-hosting) if that's an option for you.

[DimaAmega]

@robert-inkpen I think I have dirty hack for you request, try to use this image (it may be broken in some corner cases 😃 but I would try it)

FROM evidently/evidently-service:latest

# Change `BASE_PATH`, escape `/` by `\/` as in example below

RUN BASE_PATH="evidently\/ui" && \
    cd $(python -c "import evidently as e;print(e.__path__[0] + '/ui/assets')") && \
    sed -i "s/\(src\|href\)=\"\//&$BASE_PATH\//g" index.html && \
    find . -type f -name '*.js' -exec sed -i \
        -e "s/\(to\|path\|baseUrl\):\"\/\"/\1:\"\/$BASE_PATH\"/g" \
        -e "s|static/js/|$BASE_PATH/static/js/|g" {} +

Also, have you considered using subdomains for hosting evidently?