Repository navigation
Add a troubleshooting page to each template's docs #81
Description
Launch traffic will hit the same handful of first-run problems. A short reference page per template answers them before they turn into issues.
Phase 1: The pages
-
reference/troubleshooting.mdxfor each template: port already in use, dev certificates, SDK version refused by the template constraint, Docker not running, the SQLite file locked,--include-authwithout--authority(Add a troubleshooting reference page for each template leanmeancleanapps.github.io#28) - Template-specific entries (Nitro, the MCP Inspector, the Lambda emulator) (Add a troubleshooting reference page for each template leanmeancleanapps.github.io#28)
- Link it from SUPPORT.md and each getting-started page (Link the troubleshooting page from SUPPORT.md CleanMinimalApi#85, Link the troubleshooting page from SUPPORT.md CleanModelContextProtocol#65, Link the troubleshooting page from SUPPORT.md CleanGraphQLApi#64, Link the troubleshooting page from SUPPORT.md CleanWebApi#59, Link the troubleshooting page from SUPPORT.md CleanLambdaFunction#51, Add a troubleshooting reference page for each template leanmeancleanapps.github.io#28)
Checks: the site builds, and each fix has been tried on a freshly generated solution.
Activity
Link the troubleshooting page from SUPPORT.md (#51)
Link the troubleshooting page from SUPPORT.md (#59)
Link the troubleshooting page from SUPPORT.md (#64)
Link the troubleshooting page from SUPPORT.md (#65)
Link the troubleshooting page from SUPPORT.md (#85)
stphnwlsh commentedon Nov 8, 2026
Handoff
Done: the five
SUPPORT.mdlinks are merged:The pages themselves are in LeanMeanCleanApps/leanmeancleanapps.github.io#28, which is still open.
Checked (8 November, Minimal API generated from
main):docker compose port api 7310prints0.0.0.0:7310.Bind for 0.0.0.0:7312 failed: port is already allocated, matching the page's port-clash entry.--include-authwithout--authoritywrites nothing and exits with 102.src/Presentation/movie-reviews.dbpath is right.Not tried by hand: trusting the dev certificate (it changes the keychain), the SDK refusal, Docker not running, and the per-template entries for MCP, GraphQL and Lambda.
Left: merge #28. The
SUPPORT.mdlinks point at its pages, so they 404 until it deploys.Waiting on: Steve's merge of #28.