From 44f480bd91eb79eb17f78e72e8ad27dbce236625 Mon Sep 17 00:00:00 2001
From: Ivan Folgueira Bande <ivansete@status.im>
Date: Wed, 9 Aug 2023 16:03:57 +0200
Subject: [PATCH] Avoid exposing postgres ports as they might collide with a
 running PG instance

This comes from Vaclav's advice given that kind of port collisions are
quite likely to happen.
---
 docker-compose.yml | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index 98f030a..0c244fd 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -102,8 +102,6 @@ services:
       - ./postgres_cfg/postgresql.conf:/etc/postgresql/postgresql.conf
       - ./postgres_cfg/db.sql:/docker-entrypoint-initdb.d/db.sql
     command: postgres -c config_file=/etc/postgresql/postgresql.conf
-    ports:
-      - 5432:5432
     healthcheck:
       test: ["CMD-SHELL", "pg_isready", "-d", "db_prod"]
       interval: 30s
@@ -119,8 +117,6 @@ services:
     volumes:
       - ./monitoring/configuration/postgres-exporter.yml:/etc/pgexporter/postgres-exporter.yml
       - ./monitoring/configuration/pg-exporter-queries.yml:/etc/pgexporter/queries.yml
-    ports:
-      - 9187:9187
     command:
       # Both the config file and 'DATA_SOURCE_NAME' should contain valid connection info
       - --config.file=/etc/pgexporter/postgres-exporter.yml