Front-end access through reverse proxy

[VadimJCA]

Hi,

We've heard about PGSTY and really liked the concept! We're now trying to implement it for our clusters but are having some difficulty understanding the front-end access URL design.

We've completed the installation and assigned an FQDN for the PGSTY host through our on-site NGINX, which successfully serves the Home Page. However, the page contains links to other front-ends like:

Home        http://h.pigsty
Grafana     http://g.pigsty
Prometheus  http://p.pigsty
Alertmanager http://a.pigsty
Pgadmin     http://adm.pigsty

We noticed these hostnames were added to /etc/hosts under a #pigsty dns comment. How is this intended to work?

Our installation was basic - we simply specified an inventory with a meta host and a 2-node PostgreSQL cluster, then ran bootstrap-configure-install. Currently, our only solution seems to be abandoning the PGSTY home page and creating separate FQDNs for each front-end service by port. We're running PGSTY on a VM inside of our own Openstack cloud.

What are we missing?

[Vonng]

Here are some releated content that may be helpful

https://doc.pgsty.com/docs/admin/portal/

https://doc.pgsty.com/docs/admin/domain/

https://doc.pgsty.com/docs/admin/cert/

[VadimJCA]

We got it working by creating a wildcard Type A DNS record for "*.pigsty.myorg.com", then configuring a server for it on our local reverse proxy and redirecting the root location "/" to Pigsty's NGINX at its internal IP. We then modified the infra_portal section in pigsty.yml as follows:

infra_portal:
  home         : { domain: h.pigsty.myorg.com}
  grafana      : { domain: g.pigsty.myorg.com, endpoint: "${admin_ip}:3000" , websocket: true }

Now the home page and all its links work as expected.
Thank you for your guidance!