Skip to content

feat(#109): expand kanban port range to 7100-9100#131

Merged
dennisonbertram merged 1 commit intomainfrom
issue-109-kanban-port-range
Mar 21, 2026
Merged

feat(#109): expand kanban port range to 7100-9100#131
dennisonbertram merged 1 commit intomainfrom
issue-109-kanban-port-range

Conversation

@dennisonbertram
Copy link
Owner

Summary

  • Expands default kanban port range from 401 to 2001 ports (7100-9100)
  • Configurable via AH_KANBAN_PORT_START and AH_KANBAN_PORT_END env vars
  • Invalid port ranges fall back to defaults
  • 7 new tests covering custom ranges, defaults, validation, exhaustion

Test plan

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>
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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 {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

@dennisonbertram dennisonbertram merged commit baf8807 into main Mar 21, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

enhancement(kanban): expand port range beyond 7100-7500 (401 ports max)

1 participant