Nick Gordon
10/01/2025, 2:41 PMhttps://<hostname>/apps/lakefs
, but this appears to not be a style of pathing supported by LakeFS. When trying to access the UI or pre-signed URLs, it tries to access from the root (so https://<hostname>/main.js
which fails to resolve. Is there a known method for enabling this or working around it? If not, is the team open to us opening a PR that would allow for a customizable relative path to serve assets from?