Are there any other database connection definition locations other than the DISCOURSE_DB_HOST in /var/discourse/containers/app.yml? I have my PostgreSQL server running separately from my Discourse docker server and recently I changed the database connection hostname from the database server’s publi…

Yes, that is exactly what was followed. Cannot for my life understand why it’s using the public IP though after this change. Especially if that’s the only place to change the IP.

Can you block access to the public port? Maybe something else is accessing it. Or you’ve left an old container running?

app.yml의 DISCOURSE_DB_HOST 외에 데이터베이스 연결 IP/호스트를 설정하는 다른 위치가 있나요?

지원

Falco (Falco) 5월 24, 2021, 2:45오후 2

Make sure you follow Running Discourse with a separate PostgreSQL server.

글		댓글	조회수
How to Connect to discourse db from public ip inside docker container Self-hosting	1	590	10월 26, 2020
Running Discourse with pg_bouncer and a separate DB Self-hosting	2	935	9월 20, 2020
Linking containers Self-hosting hosting	5	1567	3월 31, 2014
Discourse docker runs successfully, cannot access discourse host name Self-hosting	5	178	10월 2, 2025
Can't access site after installation Self-hosting	10	4221	4월 14, 2016

app.yml의 DISCOURSE_DB_HOST 외에 데이터베이스 연결 IP/호스트를 설정하는 다른 위치가 있나요?

Related topics