I captured what I learned while onboarding the microsoft/vscode-dotnettools repo, which involved:
Updating the configuration for the existing microsoft-dotnet-framework-docker app that was already hosting ML.NET models and running the engine for the microsoft/dotnet-framework-docker repo
When this caused that app to stop successfully loading the ML.NET models, the app was republished to be upgraded to net6.0
Debugging info was added to the app to learn more about the necessary configuration
Updating the configuration of the dispatcher-app to know how to route webhook events for microsoft/vscode-dotnettools to that predictor app instance
Along the way, I finally gained a better understanding of the main vs. feature/public-dispatcher branches in this repository, and I captured that in the documentation here. I also renamed a folder to match its project name to reduce confusion therein.
I captured what I learned while onboarding the microsoft/vscode-dotnettools repo, which involved:
Along the way, I finally gained a better understanding of the
mainvs.feature/public-dispatcherbranches in this repository, and I captured that in the documentation here. I also renamed a folder to match its project name to reduce confusion therein.