I would like to know what can be/should be removed/changed in the application when working in a single tenant app, if I should remove anything at all.
For example, I see we have EditionManager, TenantManager. Seed data also has stuff for host/tenant (languages and settings for host).
The reason I am asking is that I don't want to keep anything that I won't ever be using inside the application/database. This can raise questions later on like: Why do we have this thing here? Can we remove? Will it break anything?
Can you clarify on this subject please?
3 Answer(s)
-
0
Hi,
You are right, when developing a single tenant application some concepts are meaningless like EditionManager, Edition, TenantManager etc...
You can delete multi tenancy related stuff including some of unit tests.
If you dont delete those classes, in the future you can easyly convert your app to a multi tenant application. It is up to you :).
By the way, I haven't tried this before, so there might be some unexpected errors. We can help if you face any problems while deleting those things.
-
0
Hmm It might be interesting to keep stuff around if we think about converting to multi-tenancy later, thanks for pointing that!
About the seed data, and other DB stuff, should I change any code to always be related to tenant 1 (default)? For example the languages. Or should I keep tenant id null?
-
0
Hi,
You shouldn't change it for the current version. Leave it as tenant 1 (default).
