Skip to content

Give each template its own block of local ports - #62

Open
stphnwlsh wants to merge 1 commit into
mainfrom
feature/port-blocks
Open

stphnwlsh wants to merge 1 commit into
mainfrom
feature/port-blocks

Conversation

@stphnwlsh

Copy link
Copy Markdown
Collaborator

Summary

Every template published the same ports on the host, so you couldn't run two stacks side by side. Each template now has its own block of ten ports: Minimal API 8710, MCP 8720, GraphQL 8730, Web API 8740 and Lambda Function 8750, with every port at the same place in each block. The app is on 8720 under Docker Compose and dotnet run (8721 for HTTPS), the dashboard on 8722, the collector on 8723 and 8724, the Inspector on 8725 and the chat demo on 8726. The Inspector also listens on 8725 inside its container, through CLIENT_PORT, because it only accepts calls from the origin it listens on. Everything else stays put inside the containers, so the image still listens on 8080.

docs/RUN.md gets a Ports section. The shared docker-and-compose skill describes the scheme, and the shared serilog and telemetry skills now point at docs/RUN.md instead of naming a port, so all five stay identical.

Related issues

Part of LeanMeanCleanApps/.github#86

Type of change

  • Bug fix
  • New feature
  • Breaking change (the generated solution or template parameters change in a way existing users will notice)
  • Refactoring or clean-up
  • Documentation
  • Build, pipeline or dependency update

Shared layers

  • This only touches the Presentation layer of this template.
  • This touches the Application or Infrastructure layers, tests, pipeline or repository setup, so it needs to be carried across all five templates.

Checklist

  • dotnet build and dotnet test pass locally with no warnings.
  • I added or updated tests, and line coverage stays at or above 95%.
  • I updated the README or docs where behaviour changed.
  • If this changes how we do something, I updated the matching skill in .agents/skills.
  • I checked the template still installs and creates a working solution (see CONTRIBUTING.md).

Generated by Claude Code

Every template bound 8080, 4317, 4318 and 18888 on the host, so two stacks
couldn't run side by side. Each template now publishes everything in its own
block of ten (Minimal API 8710, MCP 8720, GraphQL 8730, Web API 8740, Lambda
Function 8750), with the same offsets in every block. Inside the containers
the app stays on 8080.
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Build Pipeline

✅ Ready to merge. Every stage passed.

Stage Result Details
Build 🟢 Passed Version 2026.11.06.220-pr-62 · Template package 249 KB
Test 🟢 Passed 304 passed · 0 failed · 0 skipped · Template installs, builds and passes its tests
Coverage 🟢 Passed 100% (1119 of 1119 lines) · Needs 95%
Static Analysis 🟢 Passed No open CodeQL alerts
Dependency Review 🟢 Passed 0 vulnerable packages · 0 licence problems
Container Scan 🟢 Passed Image starts and answers · No open Trivy alerts

Commit 44b68b5 · Full run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant