In this discussion, denvergeeks seeks to integrate Discourse with CloudPanel as a reverse proxy on a Hetzner server, aiming to host multiple sites (Ghost, WordPress) alongside Discourse. After consulting guides and community advice, they learn that Discourse must be configured to run on a non-standard port (e.g., 81) or socket, with SSL/Let’s Encrypt disabled, before enabling CloudPanel as a reverse proxy Stephen. pfaffman warns that this setup is complex and requires manual configuration, not the standard ./discourse-setup script — instead, ./launcher rebuild app is required after editing app.ymlpfaffman. After successfully installing the first instance, denvergeeks struggles to create a second Discourse instance, discovering that data is being shared because both instances point to the same /var/discourse/standalone directory. pfaffman advises changing the directory to standalone2 for the second site, and suggests considering a two-container setup to share PostgreSQL if resources allow. denvergeeks confirms success by manually editing app2.yml and the Vhost file to use standalone2, then rebuilding with ./launcher rebuild app2, and clearing caches. They plan to document the full procedure for others, particularly for creators integrating Ghost and Discourse. Canapin encourages posting the tutorial under #documentation:sysadminhow-toadvanced-setup to preserve it. The thread highlights the steep learning curve for reverse proxy and multisite Docker setups, but also the community’s willingness to guide newcomers through complex sysadmin tasks.
First follow one of those guides to move discourse to another port and remove the ssl and let’s encrypt templates and rebuild. Then tell your reverse proxy to use that port.
It’s not a setup for a simpleton. You’ll have to understand both how a reverse proxy works and how to configure discourse manually. It’s not going to be simple, or intuitive.
It’s difficult enough to support the standard install for novices. Many, many hours have been spent making those instructions work for people who don’t know anything about system administration.
To create a second Discourse instance I create and edit the app2.yml, and the server_name.conf for the second Discourse, changing the DISCOURSE_HOSTNAME and the server_name.
But then… how do I build the app2? I tried:
service nginx restart
./launcher stop app
./launcher rebuild app2
and
./discourse-setup (I had used ./discourse setup for installing the first instance and then went back and edited the app.yml, and it did work out on the first instance.)
This procedure did result in a Discourse at the second URL, but it seems to be getting data from the first instance.
I’m not understanding something. What is the proper way to build the second site on the second domain?
You need to change the directory that it uses where it says /var/discourse/standalone to something different (standalone2?).
You might want to use a two container setup so that your running only one copy of postgres (I think the Multisite configuration with Docker has some hints), but if you have lots of ram you may not care.
Whoa. I never would have figured that out on my own. You are my hero of the day.
What I’m doing here is (for a client) building a prototype for a versatile Discourse publishing system for Creator-types, integrating Ghost with Discourse.
I’m a front end dev, and now need to fully learn the sysadmin.
So I need to build both a multisite and separate containers.
This is my server setup:
a dedicated server on Hetzner (6 CPU Cores, 64 GB Ram and 2x512GB NVMe)
a VPS on Contabo (8 CPU Cores, 30 GB Ram and 200 GB NVMe)
I don’t know anything about it, but if you and others think your tutorial is reliable, feel free to create a new #documentation:sysadminhow-toadvanced-setup and whatever other tags you think fits in
(before your answer is automatically deleted in one month )