cybertec-postgresql / pgwatch / 19888319322

74%

push

github

[+] add support for reverse proxies on a different path, closes #1049 (#1063)

* add support for reverse proxies on a different path, closes #1049

Users can now configure pgwatch to run under a custom path
(e.g., http::/example.com/pgwatch) when behind a reverse proxy like
Apache or Nginx.

- add `--web-base-path` flag to specify custom path prefix
- all API endpoints and static assets respect the configured base path
- inject `<base>` tag and React Router `basename` dynamically at runtime
- set `homepage: "."` in `package.json` for relative asset paths

Example usage:
  pgwatch --web-base-path=pgwatch --web-addr=:8080

Then configure reverse proxy to forward `/pgwatch/*` to
`localhost:8080/pgwatch/*`

* Put the WebSocket config into the example config

The WebSocket proxy needs to come before the general proxy.

* The config is no longer "above"

* Build frontend to `/webserver/build` and use `//go:embed` directly
in `webserver.go`

* make linter happy and remove webui go package

* fix "Download webui artifact" step

---------

Co-authored-by: Christoph Berg <myon@debian.org>
Co-authored-by: Denys Holub <holub.denys20@gmail.com>

119 of 130 new or added lines in 6 files covered. (91.54%)

3694 of 5018 relevant lines covered (73.61%)

0.84 hits per line