The discussion revolves around installing a second instance of Discourse on the same VPS. chi_noti_info asks if it’s feasible to clone Discourse into a new directory and run ./discourse-setup without conflicts, especially when using a second IP. pfaffman confirms that using a second IP is possible and suggests modifying app.yml to bind to the correct IP and creating a separate xxx.yml file for the second instance. chi_noti_info seeks clarification on whether both instances are independent and don’t interfere, while pfaffman advises that it’s simpler to create another xxx.yml file in the same directory rather than cloning into a new folder.
Just do the “30 minute installation” on a different directory than /var/discourse? Are there any possible conflicts using this method could create? I would be using a second IP for the new discourse, method I used in the past to run wordpress and discourse in same vps, which works is a lot less messy than setting up reverse proxy to me.
Thanks in advance.
Yes, you can use a second IP. You’ll need to modify app.yml so that it binds only to the correct IP, and then create a second app.yml (with a different name, of course). https://meta.discourse.org/t/howto-bind-discourse-to-a-single-ip-address/97144/3 might help.
Yeah, I have done that in the past. My question is whether installing a second instance is just as easy as git-cloning discourse into a /var/SecondInstance folder and then running ./discourse-setup from there. Do both instances of discourse interfere with each other? DO each have their own app.yml?
Anyone?
I could just go ahead and try it but I don’t want to ruin my currently working setup pf discourse+wordpress.
It’s easier to just create another xxx.yml in the same directory.