Summary
When --web-base-path is configured, the embedded web UI renders a blank page
because the built frontend bundle is referenced with a root-relative / assets/... URL instead of a base-path-aware URL.
Steps to reproduce
- Enable
--web-base-path=pgwatch in docker/compose.pgwatch.yml
- Start pgwatch using the documented Docker flow
- Open
http://localhost:8080/pgwatch/
Actual behavior
The page is blank.
Browser devtools show the main JS bundle requested from /assets/index-*.js,
which returns 404 Not Found, so the module never loads.
Expected behavior
The frontend bundle should be requested from /pgwatch/assets/index-*.js and
the UI should load normally.
Notes
The backend routes and frontend API calls already honor web-base-path; the
problem is that the generated frontend asset URLs are root-relative.
Desktop (please complete the following information):
- OS: Ubuntu
- Browser firefox
- Version latest
Summary
When
--web-base-pathis configured, the embedded web UI renders a blank pagebecause the built frontend bundle is referenced with a root-relative
/ assets/...URL instead of a base-path-aware URL.Steps to reproduce
--web-base-path=pgwatchindocker/compose.pgwatch.ymlhttp://localhost:8080/pgwatch/Actual behavior
The page is blank.
Browser devtools show the main JS bundle requested from
/assets/index-*.js,which returns
404 Not Found, so the module never loads.Expected behavior
The frontend bundle should be requested from
/pgwatch/assets/index-*.jsandthe UI should load normally.
Notes
The backend routes and frontend API calls already honor
web-base-path; theproblem is that the generated frontend asset URLs are root-relative.
Desktop (please complete the following information):