Implement a BASE_PATH option for subpath support on reverse-proxy

[slaxeee]

What type of request is this?

New feature idea

Clear and concise description of the feature you are proposing

Sync-in needs a dedicated subdomain when used behind a reverse-proxy (sync.mydomain.com).

Using a subpath (mydomain.com/sync) causes an issue : screen displays only sync-in text.

By default the server returns response considering a root (/) base and doesn't consider the subpath (/sync). When loading the HTML landing page, /assets/chunk-xxx.js are delivered absolute from the root and not relatively to a path. This can't be corrected by a proxy rule or configuration.

To enable the use of subpath we need a new BASE_PATH parameter for the server to deliver the good url at runtime.

It would be appreciate for self-hosted apps with single domain.

I'm not a JS developper but @darekwojciechowski suggested a small change : Vite base plus a router basename.

Validations

• Check the feature is not already implemented in the project.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
• Check that the feature is technically feasible and aligns with the project's goals.