-
Notifications
You must be signed in to change notification settings - Fork 165
Description
Describe the bug
The example page for how to set up a reverse proxy uses http://localhost as an example domain. This is confusing and probably never an actual use case beyond just starting it up. Reverse proxies/load balancers use internal and external DNS names to map things together and it is completely unclear which references are for the public side and which are for the internal plumbing side. This should use real(ish) names so that we can tell which is which, ex: rundeck.example.com as the public site and rundeck-server-1.internal.example.com:4440, rundeck-server-2.internal.example.com:4440, etc. Making everything localhost doesn't make any sense, and implies that the reverse proxy is running on the Rundeck server itself, which isn't usually the case.
Source page
Please include the link or name for the page of the documentation which has the issue.
https://docs.rundeck.com/docs/administration/cluster/loadbalancer/reverse_proxies.html