Activities of "liangshiwei"

Hi,

I could not reproduce the problem.

abp new Qa -u blazor-server --tiered --old

could you share the full steps or a minimum reproducible project with me? thanks.

Hi,

could you send an email to info@abp.io

I'm closing this and refunded your ticket.

Hi,

You can use context.ServiceProvider.GetRequiredService to get any services from the IOC container.

okay

how about 9AM EST ?

Join Zoom Meeting https://us05web.zoom.us/j/85322147091?pwd=S0b4SG45n7KqOBU6SpFFTThibsTCfu.1

Hi,

I'm living UTC+8, work hours are 9am to 6pm

If possible can we set up a meeting, I can share it from my local.

okay

Hi,

Sorry, I didn't find the problem.

could you share a minimum reproducible project with me? i will check it.

Those are unfortunately our requirements: We have to be able to host every tenant db on a separate server, which means every tenant db needs to be a separate container. Ok. So we could modify HandleEventAsync() of this handler to call a script on the server to create the docker container and only then apply the migration?

You can use a DOCKER CLI NET client library to create containers https://github.com/dotnet/Docker.DotNet

Hi,

We want to automate the tenant creation process. Since we want our tenant dbs in docker containers, before the tenant db is created and seeded we need to create the docker container (with a script executed on the server), and only then we know what the connection string for the tenant will look like.

I don't understand; you can use the same DB container instead of create a new DB container.

Is there a way to pass seeding data to the DbMigrator when executing it with dotnet run? Asked another way: How does the DbMigrator get the admin credentials of a newly created tenant if it is executed separately with dotnet run?

When you create a new tenant, you need to enter the admin credentials

As a second step, we plan to execute the DbMigrator to apply migrations and seeding data to this newly created tenant db container.

you don't need to do it; ABP will publish a tenant-created event, and the handler will create a database.