I’m attempting to create a second instance of Discourse on my machine that would be served on a different domain via a reverse proxy. Would it be OK if I just copied the current app.yml file to app2.yml file, changed what needs to be changed and then ran ./launcher build app2?

Yes. You can do that. But I would recommend spending a bit more time to move to separate web and data containers so that you have only a single instance of redis and Postgres running. But if you don’t care about wasting some ram and don’t need the benefit of reduced down time when your rebuild, you…

[immagine] kuba-orlik: I’m attempting to create a second instance of Discourse on my machine that would be served on a different domain via a reverse proxy. This sounds like something which would help me. I could reduce my costs by consolidating two hosts into one (slightly) bigger one. If …

In that case, yes, a second copy of samples/standalone.yml will do fine - but: make sure to update the /var/discourse/shared/[standalone]/ and other host-exposed resources to another name.

Creare un secondo file simile ad app.yml è sufficiente per il multisito?

Supporto Installazione

riking (Kane York) 3 Giugno 2020, 5:17pm 4

In tal caso, sì, una seconda copia di samples/standalone.yml va bene, ma: assicurati di aggiornare /var/discourse/shared/[standalone]/ e altre risorse esposte all’host con un altro nome.

Argomento		Risposte	Visualizzazioni
Second discourse instance on the same server Self-hosting	4	1466	Febbraio 12, 2019
Anyone have experience running two separate Docker containers instead of the secondsite method? Self-hosting hosting	13	457	Novembre 18, 2025
How to run separate web and data containers? Support	3	2488	Settembre 18, 2018
How could I install another discourse on same server (docker)? Self-hosting	3	1198	Dicembre 20, 2021
Multiple Standalone containers instead of multisite? Self-hosting hosting	4	2809	Novembre 27, 2014

Creare un secondo file simile ad app.yml è sufficiente per il multisito?

Argomenti correlati