feat(#109): expand kanban port range to 7100-9100#131
Conversation
Expand default range from 401 to 2001 ports. Configurable via AH_KANBAN_PORT_START and AH_KANBAN_PORT_END environment variables. Closes #109 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6db3600ed8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if dockerClient == nil { | ||
| panic("kanbans: NewManager requires non-nil docker client") | ||
| } | ||
| if portStart >= portEnd || portStart < 1 || portEnd > 65535 { |
There was a problem hiding this comment.
Allow single-port ranges in constructor validation
NewManagerWithPortRange documents inclusive bounds, and findFreePort can operate on a one-port interval, but the validation currently treats portStart == portEnd as invalid and silently resets to defaults. In practice this means setting AH_KANBAN_PORT_START and AH_KANBAN_PORT_END to the same value (to pin kanban allocation to one known port) will not work in production and will unexpectedly reopen the full default range.
Useful? React with 👍 / 👎.
Summary
Test plan
go test ./...passesCloses enhancement(kanban): expand port range beyond 7100-7500 (401 ports max) #109
🤖 Generated with Claude Code