Configure a path prefix for River UI #231

Hello! I am deploying an instance of Riverqueue in another service. Since I now have two separate microservices using Riverqueue I created two separate databases in Postgres since we need to be able to upgrade Riverqueue in each service independently of the other. Hence, the database migrations for Riverqueue need to happen at different points in time and the services might run with different migration versions which is why I created a separate Riverqueue database for the other service.

Now I want to deploy a River UI for the new service and thought I could use the same URL host but different path prefix for the different instances if the River UI

• https://my-host/service-a
• https://my-host/service-b

In Kubernetes I have added a rewrite of HTTP requests to https://my-host where https://my-host/service-a gets a path rewrite where I strip off /service-a to target path / and the request gets directed to the container that runs the River UI for service a (and vice versa for service b). However, this does not work and I suppose that is because the Frontend performs subsequent requests that are not prefixed with /service-a and then those requests cannot reach the River UI container for service a.

I assume that the short term solution is to use separate host names for service a and b which would be a workaround:

• https://my-host-a
• https://my-host-b

But would be nice with the possibility to have one host with different path prefixes. Would it be easy to make that configurable? I assume that you would not only specify the DATABASE_URL env variable but also an optional PATH_PREFIX=/service-a for example. Just sharing this idea if it's something you would be interested in.