fix: route IM clients through current origin
Deploy im-webapp production / deploy (push) Successful in 1m35s

This commit is contained in:
Your Name
2026-10-19 17:23:34 +08:00
parent b0d1199fb6
commit df173879fa
9 changed files with 116 additions and 18 deletions
+3 -3
View File
@@ -19,9 +19,9 @@ ENV VITE_TINODE_API_KEY=$TINODE_API_KEY
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
# Leave the file origin unset in production so downloads use the current site's /v0/file route.
# A build-time override remains available for isolated development deployments.
ARG TINODE_FILE_BASE=
ENV VITE_TINODE_FILE_BASE=$TINODE_FILE_BASE
RUN npm run build