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.
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.
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.
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!”
Je veux dire, liez la documentation de la ligne de commande et la sortie de la ligne de commande au sujet, s’il vous plaît. Il ne s’agit pas de modifications apportées à la documentation GitHub.
La sortie de la ligne de commande / l’aide du script bash doit afficher l’URL du sujet en référence. C’est ce que je veux dire. Si je peux être plus clair, faites-moi savoir comment !