I can’t seem to get the secondsite method working again, so now I’m looking at running my two sites in separate containers on the same server. If anyone has any experience with this, drop me a message.

It is mostly doable on a decently sized machine, You’ll need a reverse proxy at the bare minimum to handle ssl. And maybe use the socketed template instead of exposing ports.

[이미지] itsbhanusharma: And maybe use the socketed template instead of exposing ports. would a docker network be appropriate?

If you know what you are doing then yes. There shouldn’t be any problem.

I’ve done it with treafik and nginx proxy something. It does use more resources than multisite. You still have to understand how to get postgres to have multiple databases (unless you want to run two copies of postgres, which will require still more resources).

This server has 12 processors and 16 Gig and these are not high volume forums, so I’m not worried about the extra resources to have two containers both running postgres. I just need to figure out how to get two containers running at the same time, if I rebuild one, it stops the other. I can handle…

[이미지] MikeNolan: I just need to figure out how to get two containers running at the same time, if I rebuild one, it stops the other. You need to make another yml file, like app2.yml and change all the stuff that conflicts with the other one.

Hi Jay, When you say [이미지] pfaffman: change all the stuff that conflicts with the other one. do you mean I should be treating the two containers as a single site behind a sensible hostname and failover setup (i.e. same DISCOURSE_HOSTNAME with a load balancer/health checks in front), rather …

[이미지] MikeNolan: I just need to figure out how to get two containers running at the same time, if I rebuild one, it stops the other. Wait. Did you clone Discourse twice? You want clone Discourse once and then have multiple yml files in the containers directory. Maybe look at Use Nginx Proxy …

[이미지] pfaffman: [이미지] Ethsim2: I’m assuming both configs can just join the same Docker network rather than binding host ports, which would avoid some of the obvious conflicts — is that the right approach? I have the reverse proxy talk to port 80 on the container. Others prefer to use sock…

[이미지] pfaffman: You can even use discourse-setup if you rename app.yml to, say, hostname.yml before you run ./discourse-setup again. this sounds good, and probably explains why .\discourse-setup wasn’t working with an app.yml rather than the yml file being named the intended hostname?

secondsite 방식 대신 Docker 컨테이너를 두 개 따로 실행해 본 경험 있으신 분?

지원 자체 호스팅

pfaffman (Jay Pfaffman) 11월 17, 2025, 7:56오후 7

app2.yml 같은 다른 yml 파일을 만들고, 다른 파일과 충돌하는 부분을 모두 수정해야 합니다.

글		댓글	조회수
Two Discourse communities on the same VPS Self-hosting	5	916	12월 18, 2022
How to run separate web and data containers? Support	3	2456	9월 18, 2018
How could I install another discourse on same server (docker)? Self-hosting	3	1170	12월 20, 2021
Multiple Forums in a Single Installation Self-hosting	9	4615	10월 27, 2016
Second discourse instance on the same server Self-hosting	4	1408	2월 12, 2019

secondsite 방식 대신 Docker 컨테이너를 두 개 따로 실행해 본 경험 있으신 분?

Related topics