[RohanReddy44]

Replaces #16, which did the same thing at container start. The path is known at build time, so this is the smaller mechanism and the conventional one.

The client assumed it owned the origin root. Behind a shared domain at /experience, assets, fonts, config.json and the API were all absolute from / and every one of them 404'd — and the config failure was silent, because an unreachable config.json falls back to the bundled defaults.

How it works

docker build --build-arg VITE_BASE_PATH=/experience/ -t experience-ui .

location /experience/ {
    proxy_pass http://experience-ui:8080/;   # trailing slash strips the prefix
}
location = /experience {
    return 301 /experience/;                 # otherwise a bare /experience 404s
}

Default is / and nothing changes. In CI it comes from a VITE_BASE_PATH repository variable.

The trade: the path is baked into the bundle, so an image built for a sub-path serves only from that path. A deployment needing two paths builds two images. That is the cost of the simpler mechanism, and it is fine while the path is known when the image is built.

What Vite does not handle

It rewrites index.html, imported assets and CSS url(). Three things were invisible to it:

• The API base and config.json URL — now import.meta.env.BASE_URL-prefixed
• Six icon paths in the header and recording controls — string literals pointing at public/, so only those images broke while everything else worked
• Brand asset paths from config.json — these are data, not code. A CDN URL is left alone; a path is resolved against the base

The one that looked like a different bug

The router matched against the origin root. Under a prefix the page loaded, the config resolved, React mounted — and then every route 404'd. It now takes basepath from import.meta.env.BASE_URL. Worth knowing because "the assets load" is not evidence that it works.

Verified

A second nginx container as the edge proxy, both ways:

	built for /experience/	default build at /
page, /chat route	200, renders	200, renders
config.json	200	200
brand/logo.png	200	200
assets/settings.svg	200	200
fonts/poppins-400.ttf	200	—

Screenshotted at the sub-path, since status codes would not have caught either of the two real bugs.

Operationally

nginx resolves a proxy_pass hostname once at config load. Restart the app container and the proxy keeps the old address — I hit a 502 from exactly this while testing, and it looks like the app is down when it is not. Reload the edge after redeploying.

🤖 Generated with Claude Code