服务器上部署发现问题

[code-lixm]

我现在将三个端口统一从一个域名下转发，如下

现在发现一个奇怪的现象：
每次普通刷新：

控制台打印的变量都不是设置的变量

然后强制刷新再打印

但是config.ts访问还是访问不到，导致走默认firebase的逻辑，请有时间看一下

[ajf12f]

清理缓存，或者换个浏览器再测

[majunze2001]

On Ubuntu 22.04.5 with Docker version 27.4.1, the environment variables weren't passed in the frontend. Modifying the docker-compose file and the frontend Dockerfile worked.

[alswl]

@majunze2001 Can you show me the patch code?

[majunze2001]

Sure. Modifications to the frontend in the docker-compose.yaml:

  frontend:
    build:
      context: ./excalidraw
      args:
        VITE_APP_BACKEND_V2_GET_URL: "https://example.com:8081/api/v2/scenes/"
        VITE_APP_BACKEND_V2_POST_URL: "https://example.com:8081/api/v2/scenes/"
        VITE_APP_WS_SERVER_URL: "https://example.com:8082"
        VITE_APP_FIREBASE_CONFIG: "{}"
        # alswl'fork env
        # forked excalidraw can use env https://github.com/excalidraw/pull/5
        VITE_APP_HTTP_STORAGE_BACKEND_URL: "https://example.com:8081/api/v2"
        VITE_APP_STORAGE_BACKEND: "http"
        PUBLIC_URL: "https://example.com"

The excalidraw directory is cloned from your repo, with the following lines added to the Dockerfile after the base image.

ARG VITE_APP_BACKEND_V2_GET_URL
ARG VITE_APP_BACKEND_V2_POST_URL
ARG VITE_APP_WS_SERVER_URL
ARG VITE_APP_FIREBASE_CONFIG
ARG VITE_APP_HTTP_STORAGE_BACKEND_URL
ARG VITE_APP_STORAGE_BACKEND
ARG PUBLIC_URL

I am not sure if this is because I'm using arm machines, but anyway, I need to build the images manually.
The room and storage backend worked out of the box for me. Thank you for the great work!