Setting up a forum and really wanted to do a two container install, but am enough of a newbie that I found the discussion about editing the template files offputting. Then stumbled across the “2container” commandline option for discourse-setup which made it a breeze. I only found it because I happened to read the discourse-setup script. Is is intentional that this option has not been added to the install instructions? (If it is there but I missed it, I apologize) Thanks to the developers and the community for a great product. Mark B

2container is an undocumented feature as it is not recommended for someone without a hands on understanding of discourse. There is a rationale that a first time user trying to set up discourse may find it confusing.

Why do you say this? There is #howto for dual container config.

When @pfaffman added the 2container feature to ./discourse-setup I had asked him to write a full howto about the process and he suggested it wasn’t necessary as it may add unnecessary confusion. Perhaps the 2container low key warns that it isn’t officially supported while proceeding with the setup that way. Does that need to change?

Since a FAQ cleanup is in process, maybe this one can be added to a dedicated FAQ topic?

[image] mbronstein: I only found it because I happened to read the discourse-setup script. It is documented. From: Move from standalone container to separate web and data containers [image]Move from standalone container to separate web and data containers Added by @pfaffman 2019-12-11. NOTE: If you want to create a 2 container site you can do this: ./discourse-setup 2container It works just like normal except it’ll create separate data and web_only containers and generate a random password for the database. If you already have an app.yml you’ll need to rename it, or discourse-setup will just update it. You could then copy a backup into /var/discourse/shared/web_only/backups/default and restore that, which is a little easier than what’s described below. [image] mbronstein: Is is intentional that this option has not been added to the install instructions? (If it is there but I missed it, I apologize) I am reluctant to put it in the 30 minute install instructions, which is used by many people who can only barely understand those instructions and don’t read them carefully, because it requires that you have enough wherewithal to re-write the instructions every time you see ./launcher rebuild app to something like ./launcher rebuild web_only. “I did ‘./launcher rebuild app’ and I got an error! Help!”

I mean link the command line docs and command line output with the topic, please. Not referring to any github doc changes here.

I don’t understand what topic needs to be changed.

The command line output / help from the bash script should print the topic URL as reference. That’s what I mean. If I can be clearer, let me know how!

2container setup option

Product Support Self-hosting

codinghorror (Jeff Atwood) April 20, 2020, 6:12am 5

@pfaffman should either pull that or link it to the meta topic explicitly.

Topic		Replies	Views
Move from standalone container to separate web and data containers Sysadmins docker , how-to , advanced-setup , two-container	138	31671	September 21, 2026
Web_only installation Self-hosting	7	551	October 23, 2024
Container restart - discourse tries to reinstall Self-hosting unsupported-install	22	3341	July 30, 2020
No web_only.yml Self-hosting	3	147	September 10, 2024
Discourse and my personal experience using it Community Building	10	764	April 16, 2025

2container setup option

Related topics