Move bot health server off port 8080 to avoid Adminer conflict #130
Labels
No Label
ai-changes-requested
ai-failed
ai-pr-opened
ai-reviewed
ai-reviewing
ai-working
ai-working
bug
enhancement
feature
in-queue
performance
security
tech-debt
todo
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cal/paper-dynasty-discord#130
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The bot's health server (
health_server.py) listens on port 8080, which is the same port Adminer is exposed on in the docker-compose stack. Curlinglocalhost:8080/healthfrom the host hits Adminer's login page instead of the bot's health endpoint.Proposed Fix
Change the health server to a different port (e.g. 8081 or 9090) and update:
health_server.py— listen portdocker-compose.yml— exposed port mapping (if applicable)Context
Discovered while verifying the bot was healthy after a deploy —
curl -s http://localhost:8080/healthreturned Adminer HTML instead of the bot's health response.PR #131 opened: #131
Changed health server default port from 8080 to 8081 in
health_server.py. Updated all references inCLAUDE.md,tests/refractor-integration-test-plan.md, andtests/refractor-preflight.sh.Note:
docker-compose.ymlis gitignored so can't be committed — the production compose onsba-botswill need its healthcheck URL updated to port 8081 manually when deploying.