Can WhoDB be hosted under a sub-path (e.g. /db) behind a reverse proxy?

[anweat]

Hi WhoDB team,

I’m deploying WhoDB behind a reverse proxy and would like to serve it under a sub-path, for example:

• https://example.com/db (so I can host multiple services on one domain)

Right now, when accessed via /db, the frontend appears to request some resources from the root path (e.g. https://example.com/assets/... instead of https://example.com/db/assets/...), so a straightforward sub-path proxy results in 404s.

I also noticed there may be other paths involved (for example routes like /inter, and API endpoints like /api/query). In a sub-path deployment, should those be expected to live under /db/inter and /db/api/query as well? And if so, is there (or could there be) a config option to control this (e.g. basePath / publicUrl / apiBasePath), so users can choose whether to prefix UI routes, static assets, and API paths?

I couldn’t find a configuration knob for this—does WhoDB currently support sub-path hosting? If not, would you be open to a PR adding it?

Thanks!