-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thinking behind having a separate Migrations Service isn't clear #1846
Comments
@JamesNK I made a doc using your sample but we've heard some feedback that they don't see why the migrations need to live in their own separate service. Do we have any guidance on that? Regarding connecting a DBMS client of some kind, I'd like a doc like that but the way he did it was by manually setting the password in his dev environment with |
@JamesNK also, could you give me a clue about why we have migrations in a worker service in this tutorial? If that's the best place for them, I think we should add some text explaining why. Thanks! |
@alistairmatthews As I remember it, when I wrote this doc based on James' sample, the explanation was:
|
Can... can I assign this to you, @alistairmatthews? It was assigned to me when I was doing more Aspire stuff but my focus has changed a bit. |
Thanks for the info @CamSoper - yes, please assign this one to me. |
Done. It's very nice to be working with you again! I sang your praises to my manager last week when I was asking for some writing help. 😁 |
Glad to hear that! We have capacity if he/she needs help. |
Watch this video and update the docs in question, with related/relevant information.
Summary by @CamSoper:
Critical that Connect to SQL doc, EF Migrations doc, and EF Seeding doc are separate docs.
Critical that per EF Migrations doc (which was in turn based on this sample), we show a separate Migrations service that runs once and shuts down.
Builds a demo that is more or less exactly the same as what we show in the three docs, except they put the migration/seeding logic in the application code itself.
Shows how to connect SSMS to the SQL Server container and view the database.
The text was updated successfully, but these errors were encountered: