From c795993a644f0201321d67ddb10b575b26dc93a2 Mon Sep 17 00:00:00 2001 From: ArthurErlich Date: Thu, 3 Sep 2026 20:49:25 +0200 Subject: [PATCH] fix(omniroute): publish API and dashboard ports directly, drop OMNIROUTE_PORT Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01Qx22CV9EUS3hGATucQav13 --- .env.example | 1 - docker-compose.yml | 3 ++- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.env.example b/.env.example index 372638f..95d1335 100644 --- a/.env.example +++ b/.env.example @@ -45,7 +45,6 @@ SEARXNG_LAN_IP= # API_PORT, omniroute's own container-internal port (left at its default, # not reconfigured to match). The dashboard (DASHBOARD_PORT) is never # published at all — see docker-compose.yml's omniroute service comment. -OMNIROUTE_PORT=4000 OMNIROUTE_API_PORT=20129 OMNIROUTE_DASHBOARD_PORT=20128 # Random values, filled in automatically by ./scripts/update.sh — leave diff --git a/docker-compose.yml b/docker-compose.yml index ef735a4..9f4f30f 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -103,7 +103,8 @@ services: # always published (NPM/firewall already point there), without having # to also change omniroute's own internal port config to match. ports: - - "${OMNIROUTE_PORT:-4000}:${OMNIROUTE_API_PORT:-20129}" + - "${OMNIROUTE_API_PORT:-20129}:${OMNIROUTE_API_PORT:-20129}" + - "${OMNIROUTE_DASHBOARD_PORT:-20128}:${OMNIROUTE_DASHBOARD_PORT:-20128}" # 10+ GiB ceiling per OmniRoute's Docker guide, matching # OMNIROUTE_MEMORY_MB=8192 above. mem_limit: 10g