# Central master config for multi-tenant multi-forum solution

**URL:** <https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148>\
**Category:** Support\
**Created:** [5 Maggio 2017, 6:56am UTC](https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148 "2017-05-05T06:56:09Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![modius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/modius/32/108600_2.png) [@modius](https://meta.discourse.org/u/modius)\
**Post date:** [5 Maggio 2017, 6:56am UTC](https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148/1 "2017-05-05T06:56:09Z")

</div>

I’m looking at a little project where I need lots of tiny communities that are almost identical except for the users and content; that is, configuration, theme, SSO provider, etc.

What’s the best way to lock down config/settings across lots of forums on exactly the same server where the config will vary only slightly between forums? Also I’d like to be able to programatically create new forums, utilising the central config with slight variations between forums.

Is it possible to create a plugin who’s sole responsibility is managing a central set of configuration items? For example, use the plugin designated config unless the forum has a local setting.

What about a central “master” forum that’s not used except for configuration, that other forums inherit from?

---

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [5 Maggio 2017, 7:00am UTC](https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148/2 "2017-05-05T07:00:05Z")

</div>

Our (CDCK) multi-tenant hosting containers use an (internal-only) plugin to do what you describe – hard-code (or derive) default values for some settings, make settings invisible (and hence unavailable to be changed), that sort of thing. Programmatically creating new forums is simply a matter of creating (and migrating) a new DB and adding the config to the multisite config.

I wouldn’t call the whole setup “trivial”, but it’s certainly not the most complicated thing I’ve ever seen, either.

---

<div class="post-metadata">

**Author:** ![modius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/modius/32/108600_2.png) [@modius](https://meta.discourse.org/u/modius)\
**Post date:** [5 Maggio 2017, 7:08am UTC](https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148/3 "2017-05-05T07:08:56Z")

</div>

I was looking at using the `app.yml` to add a bunch of things like:

```plaintext
- exec: rails r "SiteSetting.notification_email='hello@bricabrac.io'"

```

And some how scripting that process.

---

<div class="post-metadata">

**Author:** ![modius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/modius/32/108600_2.png) [@modius](https://meta.discourse.org/u/modius)\
**Post date:** [5 Maggio 2017, 7:47am UTC](https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148/4 "2017-05-05T07:47:44Z")

</div>

> [@mpalmer](#):
>
> I wouldn’t call the whole setup “trivial”, but it’s certainly not the most complicated thing I’ve ever seen, either.

Hmm.. certainly doesn’t seem trivial the more i look at it. I’m back to seeing if this is possible by restricting users to category and sub-category trees and controlling that set up instead.

---

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [8 Maggio 2017, 2:01am UTC](https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148/5 "2017-05-08T02:01:01Z")

</div>

I wouldn’t try and do any of that in `app.yml`; that only gets run at container rebuild time, and there’s no need to trigger a rebuild in order to add another site to a multisite config. I’d strongly recommend going down the custom plugin route to apply config settings, unless your single-forum-with-category-restrictions approach is working for you (which is even easier).

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\
**Post date:** [3 Giugno 2019, 2:57am UTC](https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148/6 "2019-06-03T02:57:09Z")

</div>



---

<div class="post-metadata">

**Author:** ![Sangeet\_Agarwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sangeet_agarwal/32/120629_2.png) [@Sangeet\_Agarwal](https://meta.discourse.org/u/Sangeet_Agarwal)\
**Post date:** [16 Settembre 2019, 2:21pm UTC](https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148/7 "2019-09-16T14:21:38Z")

</div>

Abbiamo già una soluzione ospitata [http://community.ncqa.org/](http://community.ncqa.org/) e il gruppo aziendale è molto soddisfatto.

Ora, altri gruppi all’interno della nostra azienda stanno mostrando interesse nell’avere i propri forum.

È possibile una soluzione multi-tenant con più forum, simile a quella discussa qui, per una soluzione ospitata?

---

<div class="post-metadata">

**Author:** ![Sangeet\_Agarwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sangeet_agarwal/32/120629_2.png) [@Sangeet\_Agarwal](https://meta.discourse.org/u/Sangeet_Agarwal)\
**Post date:** [16 Settembre 2019, 6:49pm UTC](https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148/8 "2019-09-16T18:49:43Z")

</div>

Se vai su [http://community.ncqa.org/u](http://community.ncqa.org/u), vedrai un elenco di utenti.

Questi utenti sono entrati tramite il nostro login SSO.

Mentre erano su [community.ncqa.org](http://community.ncqa.org), hanno personalizzato la loro immagine del profilo.

Ora riceviamo da voi un altro sito ospitato.

Chiamiamolo [dmc.ncqa.org](http://dmc.ncqa.org).

Ora, quando uno degli utenti che ha personalizzato la propria immagine del profilo su [http://community.ncqa.org/u](http://community.ncqa.org/u) visita [dmc.ncqa.org](http://dmc.ncqa.org), dovrebbe vedere in modo trasparente la propria immagine del profilo personalizzata all’interno di [dmc.ncqa.org](http://dmc.ncqa.org).

Quindi, in sostanza, volevo sapere se questo livello di multi-tenancy è possibile su una soluzione ospitata da [discourse.org](http://discourse.org).

Grazie!

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\
**Post date:** [24 Aprile 2023, 7:32pm UTC](https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148/9 "2023-04-24T19:32:16Z")

</div>



---

<div class="post-metadata">

**Author:** ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)\
**Post date:** [11 Giugno 2023, 9:08am UTC](https://meta.discourse.org/t/central-master-config-for-multi-tenant-multi-forum-solution/62148/10 "2023-06-11T09:08:29Z")

</div>


