finallycoffee/matrix-docker-ansible-deploy
finallycoffee/matrix-docker-ansible-deploy
5
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

Browse Source
This commit is contained in:
Slavi Pantaleev 2022-06-22 22:50:43 +03:00
parent f4cf7b9cc1
commit 2e68c9963b
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
roles/matrix-prometheus-postgres-exporter/defaults/main.yml
View File

@ -29,14 +29,14 @@ matrix_prometheus_postgres_exporter_database_port: 5432
matrix_prometheus_postgres_exporter_database_name: 'matrix_prometheus_postgres_exporter' 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`, # Official recommendations are to run this container with `--net=host`,
# but we don't do that, since it: # 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) # - 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, # 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). # but that's trickier to accomplish and won't necessarily work (hasn't been tested).