Repository navigation
Show each template's own block of local ports - #22
Merged
Merged
Conversation
… MCP features The sample movies have recognisable titles now, so every example shows the new ids and numbers. Reviews have text and can be searched by it and by a minimum star rating. MCP has two more prompts, a top rated resource, id completions, resource links, icons, null fields and an optional chat demo. dotnet run listens on port 8080 now, not 5032.
dotnet run redirects http://localhost:8080 to https://localhost:8081, so a curl against the HTTP address got an empty 307. The examples use the HTTPS address and say to trust the development certificate once. Docker Compose only listens on HTTP, so its examples keep http://localhost:8080.
The templates now publish everything in their own block of ten, Minimal API 8710, MCP 8720, GraphQL 8730, Web API 8740 and Lambda Function 8750, so the docs use those ports for Docker Compose and dotnet run, and the configuration references explain the scheme.
8 tasks done
The templates now use 7310, 7320, 7330, 7340 and 7350, and each app listens on that port inside its container too, so docker run and the deploy guides use it as well. Lambda's emulator stays on 8080 inside.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The templates now publish everything on their own block of ten ports so two stacks can run side by side: Minimal API 7310, MCP 7320, GraphQL 7330, Web API 7340 and Lambda Function 7350. Within a block, +0 is the app over HTTP, +1 HTTPS under
dotnet run, +2 the Aspire dashboard, +3 and +4 the collector, +5 the MCP Inspector and +6 the chat demo. Each app listens on its own port inside its container too, so every page now uses one number fordotnet run,docker run -p, Docker Compose and the deploy guides, and the configuration references listASPNETCORE_HTTP_PORTS. Lambda's emulator still listens on 8080 inside, and its pages say so.This branch is built on #21, so merge that first and the diff here shrinks to the port changes.
Related issues
Part of LeanMeanCleanApps/.github#86
Template PRs: LeanMeanCleanApps/CleanMinimalApi#82, LeanMeanCleanApps/CleanModelContextProtocol#62, LeanMeanCleanApps/CleanGraphQLApi#62, LeanMeanCleanApps/CleanWebApi#56, LeanMeanCleanApps/CleanLambdaFunction#50