I am planning to deploy an on-premises app to multiple clients. can I setup a single tenant application with editions and features for each client on-premises? and without having them (edition,featuers) setup on the DB as the client will have access to the DB and may change the assigned edition and features
what is the best way to implement this scenario using abp commercial ?
4 Answer(s)
-
0
HI,
Do you mean you want to pre-assign tenants to clients?
-
0
the app is a single tenant deployed on my client on-premises datacenter.
but I want to use the app in multiple clients (my customers) and each client will have different editions/features enabled of the same app.
I want to make sure that the client can not modify the editions/features as they have access to the DB on-premises
what is the best way to handle deployment of abp commercial in this scenario?
-
0
Hi,
I think you should hardcode tenant and features when publishing and always use
DefaultTenantStore,NullFeatureStore.cs. because they will not read data from the database .See https://docs.abp.io/en/abp/latest/Multi-Tenancy#example-define-tenants-as-hard-coded https://github.com/abpframework/abp/blob/42f37c5ff01ad853a5425d15539d4222cd0dab69/framework/test/Volo.Abp.Features.Tests/Volo/Abp/Features/TestFeatureDefinitionProvider.cs
-
0
Looks promising, Thanks.
