Просмотр исходного кода

Fix matrix-prometheus-postgres-exporter port number in some comments

pull/1617/merge
Slavi Pantaleev 3 лет назад
Родитель
Сommit
2e68c9963b
1 измененных файлов: 3 добавлений и 3 удалений
  1. +3
    -3
      roles/matrix-prometheus-postgres-exporter/defaults/main.yml

+ 3
- 3
roles/matrix-prometheus-postgres-exporter/defaults/main.yml Просмотреть файл

@@ -29,14 +29,14 @@ matrix_prometheus_postgres_exporter_database_port: 5432
matrix_prometheus_postgres_exporter_database_name: 'matrix_prometheus_postgres_exporter'


# Controls whether the matrix-prometheus container exposes its HTTP port (tcp/9100 in the container).
# Controls whether the matrix-prometheus container exposes its HTTP port (tcp/9187 in the container).
#
# Takes an "<ip>:<port>" value (e.g. "127.0.0.1:9100"), or empty string to not expose.
# Takes an "<ip>:<port>" value (e.g. "127.0.0.1:9187"), or empty string to not expose.
#
# Official recommendations are to run this container with `--net=host`,
# but we don't do that, since it:
# - likely exposes the metrics web server way too publicly (before applying https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1008)
# - or listens on a loopback interface only (--net=host and 127.0.0.1:9100), which is not reachable from another container (like `matrix-prometheus`)
# - or listens on a loopback interface only (--net=host and 127.0.0.1:9187), which is not reachable from another container (like `matrix-prometheus`)
#
# Using `--net=host` and binding to Docker's `matrix` bridge network may be a solution to both,
# but that's trickier to accomplish and won't necessarily work (hasn't been tested).


Загрузка…
Отмена
Сохранить