fix: port standardization per hero_ports registry #2

Closed
mik-tf wants to merge 6 commits from development_heroports into development
Owner

Summary

  • Update default listen address to 127.0.0.1:3394
  • Update default Redis URL to port 3378
  • Include Redis auth in default connection URL
  • Standardize hero_os port reference to 8880

Test plan

  • hero_launcher starts on port 3394
  • Connects to hero_redis on port 3378
## Summary - Update default listen address to 127.0.0.1:3394 - Update default Redis URL to port 3378 - Include Redis auth in default connection URL - Standardize hero_os port reference to 8880 ## Test plan - [ ] hero_launcher starts on port 3394 - [ ] Connects to hero_redis on port 3378
fix: standardize hero_os port to 8880 (88xx frontend convention)
All checks were successful
Build and Test / build-and-test (pull_request) Successful in 5m57s
2e1f7cd34e
- Replace hero_wasmos references with hero_os
- Align all port references to 8880 (was 3388/8201)
- hero_wasmos is archived, hero_os is the active frontend
fix: update default listen to 127.0.0.1:3394 and redis to port 3378 per hero_ports registry
All checks were successful
Build and Test / build-and-test (pull_request) Successful in 5m42s
94da84a8a5
fix: include hero_redis auth in default redis URL
All checks were successful
Build and Test / build-and-test (pull_request) Successful in 5m53s
eae5299333
mik-tf changed title from fix: standardize hero_os port to 8880 to fix: port standardization per hero_ports registry 2026-02-14 04:44:02 +00:00
fix: don't pass extra CMD arg to Docker container
All checks were successful
Build and Test / build-and-test (pull_request) Successful in 5m51s
6a1ac0837a
The Dockerfile ENTRYPOINT is ["hero_zero", "run"]. Passing "hero_zero"
as CMD made the effective command "hero_zero run hero_zero", which
treated "hero_zero" as an unknown service name filter.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
fix: disable admin UI in hero containers to avoid port conflicts
All checks were successful
Build and Test / build-and-test (pull_request) Successful in 4m57s
282c0fc062
Pass --admin-port 0 to hero_zero inside containers since --network host
shares the host's port space and the admin UI port would conflict.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
fix: poll container status and transition from initializing to running
All checks were successful
Build and Test / build-and-test (pull_request) Successful in 7m7s
6f0ff9abbf
After launching a container, poll its status every 2s for up to 60s.
Transition to Running when container is up, or Error if it exits
or times out. Previously status was stuck on Initializing forever.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Author
Owner

Superseded by #3 — consolidated to development_mik branch with latest development merged in.

Superseded by #3 — consolidated to `development_mik` branch with latest `development` merged in.
mik-tf closed this pull request 2026-02-19 02:59:26 +00:00
All checks were successful
Build and Test / build-and-test (pull_request) Successful in 7m7s

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_launcher!2
No description provided.