Postgrest service usually answers requests at http port 3000 (i.e. http://localhost:3000/)
pgAdmin might be also needed and provides an http-interface at some port (80?)
both will likely be exposed via a (apache) reverse proxy listening on https port 443 only (i.e. for providing and terminating https (ssl) with official certificates)
for this use-case (i.e. in TI's DMZ) it's needed, that different components are configured to work also when called trough such a reverse proxy and in a subdirectory (i.e. postgrest as https://ci.thuenen.de/postgrest/ or pgAdmin as https://ci.thuenen.de/pgAdmin/)
Postgrest service usually answers requests at http port 3000 (i.e. http://localhost:3000/)
pgAdmin might be also needed and provides an http-interface at some port (80?)
both will likely be exposed via a (apache) reverse proxy listening on https port 443 only (i.e. for providing and terminating https (ssl) with official certificates)
Rules might look like: `
ProxyPass /postgres/ http://ip_of_docker_host:3000/ ProxyPassReverse /postgres/ http://ip_of_docker_host:3000/ ProxyPass /pgAdmin/ http://ip_of_docker_host/ ProxyPassReverse /pgAdmin/ http://ip_of_docker_host/ `
for this use-case (i.e. in TI's DMZ) it's needed, that different components are configured to work also when called trough such a reverse proxy and in a subdirectory (i.e. postgrest as https://ci.thuenen.de/postgrest/ or pgAdmin as https://ci.thuenen.de/pgAdmin/)