Add customizable path of db-scheduler-ui

[schmaki]

Hi all,

first of all thanks for creating this db scheduler extension ! I am trying to include db-scheduler-ui into one of my projects, but am running into the problem, that my production spring servlet app is deployed at a custom base route www.mydomain.com/api/.
This breaks the ui part in my cloud environment and produces 404 erros for all loaded resources. On the other hand if i test it locally with root path "/" everything works.

With my limited understanding, i assume the reason for these errors is the fact that the index.html references "/db-scheduler" as absolute path in the hrefs, which leads to a fetch error since www.mydomain.com/db-scheduler/ is not part of my app.

Am i correct with this assumption ? Is it possible to make db-scheduler-ui work without having to customize db-scheduler-ui-frontend ?

Thanks!

[geirsagberg]

Correct, currently the app only supports running on the specific URL of /db-scheduler. It is certainly possible to make it configurable, but might take some fidgeting.

https://github.com/bekk/db-scheduler-ui/blob/main/db-scheduler-ui/src/main/java/no/bekk/dbscheduler/ui/controller/SpaFallbackMvc.java would be the place to start, PRs are welcome 😅

[srxx]

In addition, the base path could change between envs or be dynamic completely, e.g. imagine having multiple backend servers all with embedded db-scheduler-ui, that are served behind the same reverse proxy hence each will have a different based path to access db-scheduler. In other words this would need a 'at runtime' resolution, not just statically via vite relative base paths or similar.

@geirsagberg thanks for the amazing work so far, but could you guide through on how to achieve this in more detail as not all of us are frontend/vite oriented to know enough about the topic?