You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The worker service applies the migrations really well. One pain point has always been applying these migrations with a script or bundle due to the fact that the devops server is usually cloud based and can't communicate with the database due to the firewall.
I'm considering using a worker service like this on production as well. The pipeline can deploy updated versions and start the worker service in azure container apps.
Looking for feedback on whether this would be advisable.
Type of issue
Other (describe below)
Description
The worker service applies the migrations really well. One pain point has always been applying these migrations with a script or bundle due to the fact that the devops server is usually cloud based and can't communicate with the database due to the firewall.
I'm considering using a worker service like this on production as well. The pipeline can deploy updated versions and start the worker service in azure container apps.
Looking for feedback on whether this would be advisable.
Page URL
https://learn.microsoft.com/en-us/dotnet/aspire/database/ef-core-migrations
Content source URL
https://github.com/dotnet/docs-aspire/blob/main/docs/database/ef-core-migrations.md
Document Version Independent Id
570db834-663e-58f9-b714-5938e410ebd5
Article author
@IEvangelist
Related Issues
The text was updated successfully, but these errors were encountered: