* Fix Hermes agent port configuration
* fix: bind dashboard to 0.0.0.0 so port-forwarded hosts can reach it
Restore the full three-container compose file (previous commit replaced
it wholesale) and change only the dashboard port binding: 127.0.0.1:9119
prevents access via the server IP, which is exactly the issue reported
in #6876.
* compose: restore loopback-only dashboard binding, document opt-in
The dashboard runs --insecure; publishing it on 0.0.0.0 exposes an
unauthenticated service on every host interface. Restore the
127.0.0.1:9119:9119 binding that matches the file convention (all
services are loopback by default) and document the opt-in exactly
like the webui service does (#6876).
* fix: bindable ports for remote access (issue #6876)
---------
Co-authored-by: mercael91 <mercael91@users.noreply.github.com>
Co-authored-by: nesquena-hermes <nesquena+hermes@gmail.com>
