Thanks in advance. I’m planning setup discourse with high availability in production environment. The below are my design plan and some environment condition. Setup with 3 application servers and 2 Postgres DB servers. Always one PG server on write mode and another in read only mode. These 3 application servers will points to same DB server. DB each instances should server read and write only operations respectively. Production servers doesn’t have internet connectivity but I can pull dockerHub images. We have our own GitLab server. Is it possible to bootstrap docker image and that image on multiple servers? Please anyone help for doing this setup. If any links or suggestions please PM me.

[תמונה] Veeru_Badavath: Any reason for mentioning object storage, can’t we use server internal storage? How are you going to handle multiple app servers and user uploads? A shared network drive between all servers? That may work, but our official solution for that is Object Storage using the S3 API. [תמונה] Veeru_Badavath: In HA setup do we need to copy bootstrap performed discourse directory in all app server? No need for that, as long as you [תמונה] Falco: Are you using an external PostgreSQL, Redis and Object Storage

[תמונה] Veeru_Badavath: Is it possible to bootstrap docker image and that image on multiple servers? After running ./launcher bootstrap app somewhere you will need to save that resulting container image (usually done by pushing it to a registry) and then download and run it on your three app servers. [תמונה] Veeru_Badavath: Setup with 3 application servers and 2 Postgres DB servers. You will also need a central Redis server (and potentially replicas for it). You are also missing a load balancer to direct requests for those different application servers.

Thanks for the reply @Falco We are using HAProxy load-balancer and Nexus repo for artifacts storing.

Hi @Falco In my production env, I dont have internet access, so what I am planning is performing bootstrap on Internet accessible machine taking that bootstrap image to production servers. While doing this on production VM container is not coming up because Unicorn server looking some parent process ID so it is not running. Please help me here, whether do I need copy bootstrap performed /var/discourse dir to production server?

[תמונה] Veeru_Badavath: While doing this What is “this” ? The bootstrap or the running the previously bootstrapped container image?

When I’m running the previously bootstrapped container image

How did you save and exported the image to the production server? How, exactly, are you trying to run this saved image in production?

previously bootstrapped image pushing to Nexus repo and from Nexus repo pulling in production server. docker run command generating from ./launcher start-cmd app and running same command in production server.

run-parts: executing /etc/runit/1.d/00-ensure-links run-parts: executing /etc/runit/1.d/00-fix-var-logs run-parts: executing /etc/runit/1.d/01-cleanup-web-pids run-parts: executing /etc/runit/1.d/anacron run-parts: executing /etc/runit/1.d/cleanup-pids Cleaning stale PID files run-parts: executing /etc/runit/1.d/copy-env Started runsvdir, PID is 42 chgrp: invalid group: ‘syslog’ ok: run: redis: (pid 51) 0s ok: run: postgres: (pid 56) 0s supervisor pid: 53 unicorn pid: 75 config/unicorn_launcher: line 71: kill: (75) - No such process config/unicorn_launcher: line 15: kill: (75) - No such process (53) exiting ok: run: redis: (pid 51) 7s ok: run: postgres: (pid 101) 0s supervisor pid: 96 unicorn pid: 103 config/unicorn_launcher: line 71: kill: (103) - No such process config/unicorn_launcher: line 15: kill: (103) - No such process (96) exiting ok: run: redis: (pid 51) 14s ok: run: postgres: (pid 127) 0s supervisor pid: 120 unicorn pid: 129 config/unicorn_launcher: line 71: kill: (129) - No such process config/unicorn_launcher: line 15: kill: (129) - No such process (120) exiting ok: run: redis: (pid 51) 22s timeout: down: postgres: 0s, normally up, want up ok: run: redis: (pid 51) 30s timeout: down: postgres: 1s, normally up, want up ok: run: redis: (pid 51) 37s ok: run: postgres: (pid 174) 0s supervisor pid: 165 unicorn pid: 176 config/unicorn_launcher: line 71: kill: (176) - No such process config/unicorn_launcher: line 15: kill: (176) - No such process (165) exiting ok: run: redis: (pid 51) 48s ok: run: postgres: (pid 196) 1s supervisor pid: 191 unicorn pid: 198 config/unicorn_launcher: line 71: kill: (198) - No such process config/unicorn_launcher: line 15: kill: (198) - No such process (191) exiting ok: run: redis: (pid 51) 54s timeout: down: postgres: 1s, normally up, want up

Are you using an external PostgreSQL, Redis and Object Storage? That is expected when doing HA, and both your production servers and the build servers need to have access to those external services.

הגדרת Discourse HA בסביבה מבודדת רשת

תמיכה התקנה

Falco (Falco) 17 במרץ,‏ 2022,‏ 6:22pm 9

Can you share the error log when starting it on production?

נושא		תגובות	צפיות
Multiple app containers for a single Discourse site Self-hosting hosting	5	319	19 בינואר,‏ 2026
High Availability 3 Server setup Self-hosting hosting	10	2104	19 בפברואר,‏ 2021
Discourse High Availability Self-hosting	5	5121	19 בדצמבר,‏ 2024
Looking for Production Discourse Instructions Self-hosting	9	4854	18 בפברואר,‏ 2020
Can Discourse ship frequent Docker images that do not need to be bootstrapped? Development	211	41865	13 ביולי,‏ 2025

הגדרת Discourse HA בסביבה מבודדת רשת

נושאים קשורים