Skip to content

v1.3.0 — default port 5100 → 9004 (canonical Uttera-stack scheme)

Choose a tag to compare

@fakehec fakehec released this 18 Apr 21:02
· 8 commits to main since this release

Adopts the canonical Uttera-stack port scheme: TTS services
on 9004 (all backends — both hotcold and vllm siblings),
paired with the opposite service family on the adjacent port. The
Gatekeeper and clients route by service family — hotcold ↔ vllm
becomes a backend swap, not a port swap.

Port scheme

Port Service family Repos
9004 TTS uttera-tts-hotcold, uttera-tts-vllm
9005 STT uttera-stt-hotcold, uttera-stt-vllm
8880 Gatekeeper echo-gatekeeper (OpenResty)

Why move off 5100

While 5100 itself had no mainstream collisions, pairing TTS=5100
with STT=9005 (STT had to move off 5000 due to macOS AirPlay +
Docker Registry v2 collisions) was asymmetric. Both service families
now live in the clean 9000-9099 range (IANA "User Ports", no
canonical assignment).

Migration

Deployments that already override PORT via env var: no change required.

Deployments running on the old default (:5100):

  • Repoint your Gatekeeper / reverse proxy at :9004.
  • Or preserve the old endpoint by setting PORT=5100 in your env.
  • Docker users: update your -p flag or docker-compose.yml.

Related releases

  • uttera-tts-hotcold adopts the same 9004 port.
  • The other family (STT) moves to 9005 in the same round.

See CHANGELOG.md.