fix: route production IM API correctly

2026-10-19 11:05:50 +08:00
parent d2b4cb0440
commit d7bfd2f417
5 changed files with 31 additions and 1 deletions
@@ -14,6 +14,11 @@ COPY web/. .
 ARG TINODE_API_KEY=
 ENV VITE_TINODE_API_KEY=$TINODE_API_KEY

+# The production web UI and IM REST API use different origins. Local development leaves this unset
+# and continues to use Vite's same-origin /v1/im proxy.
+ARG TINODE_API_BASE=
+ENV VITE_TINODE_API_BASE=$TINODE_API_BASE
+
 # File downloads must use the canonical IM API origin. The web origin has its own independently
 # deployed path router and may otherwise send /v0/file requests to an older IM server.
 ARG TINODE_FILE_BASE=https://api.118im.com/v0/file