Sync-in server with subpath

[slaxeee]

I'm using sync-in (npm install) behind a reverse proxy. I've tried with nginx (location and proxy_path) and zoraxy.
I can't manage to find a configuration for a subpath access (https://mydomain.com/sync).
With a dedicated subdomain uri it works perfectly of course.
After the first request, i've got a sync-in text in the middle of the screen and all others chunck-xxx.js requests are unresolved due to the bad path.
Does anyone got a working config ?
Maybe Sync-in needs a baseurl parameter to correct this.

[darekwojciechowski]

This isn't something the proxy can fix. The frontend is a bundled SPA, and the base path gets baked into the JS at build time. So the HTML loads (that's your "sync-in" text), then it asks for /assets/chunk-xxx.js — absolute, from the root — and your proxy has nothing there. Rewriting response bodies with nginx sub_filter can paper over the HTML, but the chunk URLs the router builds at runtime will keep breaking, and so will the API calls.

You're right that this needs a base URL option on the server side. Without one, the two working setups are:

Dedicated subdomain, which you already found works — that's the supported path today.

Or a dedicated port/root on an internal host, proxied at the root of a subdomain. Same thing really.

Worth opening a feature request for a BASE_PATH build/runtime option if there isn't one already — it's a common ask for anyone consolidating self-hosted apps under one domain, and it's a small change on their side (Vite base plus a router basename).

If you want to confirm the diagnosis before giving up on it: load https://mydomain.com/sync, open devtools Network, and check the failing requests. If they're going to https://mydomain.com/assets/... instead of https://mydomain.com/sync/assets/..., that's the baked-in base path and no proxy config will change it.

[slaxeee]

@darekwojciechowski
Thanks a lot for this explanation.
I can confirm the html asks for /assets/chunk-xxx.js with absolute with the bad url, so nothing is loaded and display.

The BASE_PATH parameter is the expected feature to correct this clearly.