This project is read-only.

Multi tenancy settings in database

Topics: Customizing Orchard
May 16, 2013 at 10:01 PM
I would like to change where the multi tenancy settings are stored. Currently as I understand it, these are stored in the settings.txt file and adding a tenant effectively re-starts the other tenants in that orchard instance.

I would like to modify the multi tenancy module so that these settings are stored in the database. What are the implications of making this change?
May 16, 2013 at 10:20 PM
The implication is that you need to implement a ShellSettingsManager to save/read shell settings for each tenant. Which means you will need to store the connection string to this "common" database somewhere.
May 27, 2013 at 7:13 AM
Thanks for providing such a wonderful information. Also I would like to add that multi-tenancy database requires 4 nodes per database. Just click here to find economics of multi-tenancy that can help in cost savings, data aggregation/data mining, complexity, release management.