Given that a multisite installation of discourse uses about the same resources as an ordinary install with the same traffic , I wonder what exactly the downsides are, apart from a more complicated setup procedure. An obvious one is that if one of your sites is down, all of your sites are down (right?). But what about support, for example? If I search meta for a solution to an issue and find something, will it automatically apply to my multisite install, even though the original topic doesn’t explicitly deal with multisite?

An obvious one is that if one of your sites is down, all of your sites are down (right?) Yes

[image] tophee: But what about support, for example? If I search meta for a solution to an issue and find something, will it automatically apply to my multisite install, even though the original topic doesn’t explicitly deal with multisite? Typically yes – however, for some steps, you’ll need to make sure you work on the correct instance. The key is to set an environment variable like RAILS_DB=myfancypantsinstance1 e.g. when entering the rails console. This is why I recommend making the first instance on a multisite host a test instance: If you ever forget to specify the instance, you’ll target your test instance, which is probably safer than working with a production instance by accident :wink:

[image] tophee: about the same resources as an ordinary install with the same traffic That is not entirely true: for each Unicorn process there can a separate database connection for each site in the multisite. So 5 Unicorns, 1 Sidekiq and 5 sites = 30 Postgres server processes. Some other disadvantages / things you need to be aware of with multisite: Sidekiq is shared and /sidekiq is only available on the master site All plugins are shared, there can not be separate plugin choices discourse.conf is shared so there can only be one mail server Some plugins are incompatible with multisite

[image] RGJ: So 5 Unicorns, 1 Sidekiq and 5 sites = 30 Postgres server processes. I don’t understand a word what you are saying, but that is entirely my fault. I understand, though, that you are counting software processes and I have no idea how these translate into hardware recourse requirements. Could you elaborate? [image] RGJ: Sidekiq is shared and /sidekiq is only available on the master site I understand that this can be a disadvantage from the perspective of a (commercial) hoster because your clients wont have access to /sidekiq on their respective sites and if you give them access to the mastersite they will possibly see more than they want or should see, right? But if all sites are mine, it probably doesn’t matter, right? [image] RGJ: All plugins are shared, there can not be separate plugin choices Very important point, thanks for bringing that up! However, provided that all installed plugins have a switch to turn them off, it doesn’t really matter, does it? [image] RGJ: discourse.conf is shared so there can only be one mail server Wait, the only one of my instance where I did something with a discourse.conf file is the one where I have discourse behind a reverse proxy and there is nothing about email in that file. [image] RGJ: Some plugins are incompatible with multisite How do I know which ones? Trial and error? Or, since this also about future compatibility, what type of plugins are likely to be incompatible?

[image] tophee: Could you elaborate? Very easily put: there is a (albeit small) memory penalty that is proportional to the amount of multisite forums. [image] tophee: But if all sites are mine, it probably doesn’t matter, right? Correct. [image] tophee: provided that all installed plugins have a switch to turn them off, it doesn’t really matter, does it? Most plugins just turn off their functionality but they are still loaded into memory. So there is a (small) memory and performance penalty there. [image] tophee: where I did something with a discourse.conf file is the one where I have discourse behind a reverse proxy This is not about the nginx discourse.conf but about the Discourse one. I think it’s generated out of app.yml. [image] tophee: How do I know which ones? Trial and error? Or, since this also about future compatibility, what type of plugins are likely to be incompatible? Trial and error…

Is it possible to have a multisige that supports many different languages, not just en-US? Or each Discourse multisite can support just the language in the main config?

It seems that n8n Community follows that approach, the downside could be related with SSO if you are planning to use it within a blog or another domain/app.

[image] Greg Magarshak: Is it possible to have a multisige that supports many different languages, not just en-US? Yes that is possible. [image] satonotdead: the downside could be related with SSO Can you please elaborate on that?

This was 5 years ago. Is there any changes on how to check which plugins work with multisite and which don’t? If anyone is curious, here are the plugins i’m using on all my sites: - git clone https://github.com/focallocal/dcs-discourse-plugin.git - git clone https://github.com/discourse/discourse-assign.git - git clone https://github.com/hnb-ku/discourse-custom-hamburger-links - git clone https://github.com/paviliondev/discourse-custom-wizard.git - git clone https://github.com/paviliondev/discourse-events.git - git clone https://github.com/discourse/discourse-kanban-theme.git - git clone https://github.com/discourse/discourse-data-explorer - git clone https://github.com/discourse/discourse-solved - git clone https://github.com/discourse/discourse-akismet - git clone https://github.com/discourse/discourse-post-voting - git clone https://github.com/discourse/discourse-docs - git clone https://github.com/discourse/discourse-docs-card-filter - git clone https://github.com/discourse/discourse-category-experts - git clone https://github.com/discourse/discourse-cakeday - git clone https://github.com/discourse/discourse-code-review

It looks like you have a couple of theme components in there by accident?

Pros and cons of a multisite installation

Product Support Self-hosting

Isambard (Isambard) June 9, 2024, 6:15pm 13

what determines which is the ‘first’ instance? how does one go about converting a standard install to multi-site with a dummy first instance?

Topic		Replies	Views
Multisite vs another Install Self-hosting	1	913	November 17, 2014
I have some questions about multisite Feature	2	923	September 24, 2015
Multisite vs multiple containers Self-hosting	11	2277	June 15, 2026
One server for 2 Discourse communities? Self-hosting hosting	56	2025	August 27, 2026
Pros and cons of multiple standalone containers vs one for multiple Discourse installs? Self-hosting	5	2055	January 3, 2026

Pros and cons of a multisite installation

Related topics