Starts in:
0 DAY
21 HRS
33 MIN
50 SEC
Starts in:
0 D
21 H
33 M
50 S

Activities of "imranStem"

I have created one abp module class library where I need to fetch the features, I am already fetching the setting and setting is working fine. I have added Volo.Abp.Features reference in the class library to get the required features.

In the class, I injected ISettingStore settingStore, IFeatureStore featureStore.

When I get the setting from the settingStore then I am getting the setting value but when I am using the featureStore to get the feature, it returning the null value. I am not able to fetch the feature values from feature store.

Do I need to add dependency of AbpFeaturesModule ?

[DependsOn(typeof(AbpFeaturesModule))]

However, this can work only if the audit log database with the given connection string is available. So, you need to create the second database, create audit log tables inside it and maintain the database tables. No problem if you manually do all these. However, the recommended approach is the code first migrations. One of the main purposes of this document is to guide you on such database separation scenarios.

Ok, I understand, The migration for module can be manage by module itself, not the application.

I have add builder.ConfigureYourModule() and migration is updating default database not module database.

I mean one apps can have multiple databases connection string, Like If I want abp audit log in different database then we can configure that same way, I want different database for custom module. One is default connection string and ModuleConnectionString.

public static class ModuleDbProperties
{
    public static string DbTablePrefix { get; set; } = "Module";

    public static string? DbSchema { get; set; } = null;

    public const string ConnectionStringName = "Module";
}

I have already called builder.ConfigureYourModule(); in module class, If I add builder.ConfigureYourModule(); in main application ef core module then it will create entities in same database, not in module database. Right?

Execution command : dotnet ef migrations add TestName Folder: Ef core module in main application

Migration run successfully but only with abp entities, not module entity. I have add reference of module ef core in main ef core module and also add DependsOn ef core module ref to main ef core module.

Do I need to do any other configuration to add module entities migration?

Confirm email is disabled.

The issue is fixed. I got the idea from your Forwarded headers.

The issue was the IP whitelisting in ingress yaml.

nginx.ingress.kubernetes.io/whitelist-source-range

I have removed the IP whitelisting from Authserver ingress and it started working, Do you have any idea about this? Web, Gateway and Authserver is pointing to same IP address.

Thank you for your support.

If I login with auth server then its working fine.

The error message is same.

Showing 1 to 10 of 68 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06