Published Docker image is out of sync with repo main; frontend defaults break i18n and API routing

[eph2]

Hi, I deployed MiroFish from the published Docker image and found that the runtime frontend does not match the current repository state.

Main problems observed:

1. The published container frontend is older than the current repo

• /app/frontend/src/main.js in the image does not register i18n
• frontend/package.json in the image does not include vue-i18n
• frontend/vite.config.js in the image does not include the current aliases

2. The frontend locale defaults are problematic for non-Chinese deployments

• default locale falls back to zh
• previous browser state can keep forcing Chinese
• English users end up with a Chinese UI even when the page HTML is already set to lang="en"

3. API base path can become duplicated in production

• if VITE_API_BASE_URL=/api is set at deploy time, requests like /api/simulation/history become /api/api/simulation/history

4. The image may miss the locales directory expected by the current frontend code

• this causes Vite/runtime failures for languages.json and locale JSON imports depending on how the image was built

Suggested fixes:

• rebuild/publish the Docker image from the current repo state
• ensure frontend/package.json includes vue-i18n
• ensure frontend/src/main.js registers i18n
• keep frontend/vite.config.js aligned with the repo
• include the locales/ directory in the image
• consider changing the default locale fallback from zh to en or making it configurable via env
• document that VITE_API_BASE_URL should not duplicate /api if the frontend methods already call /api/...

I validated this in production during deployment:

• old image rendered a Chinese home page by default
• old image generated broken API paths in some setups
• after syncing the frontend files and dependencies with the current repo, the app rendered in English correctly and /api/simulation/history worked again

[dosubot]

Hi @eph2! I'm Dosu and I’m helping the MiroFish team.

Thanks for the detailed report! I looked into the current repo state and can confirm/clarify a few things:

On the Docker image being out of sync: The current repo does have i18n properly set up — vue-i18n@^11.3.0 is in frontend/package.json [1], i18n is imported and registered in frontend/src/main.js [2], and the @ and @locales aliases are configured in vite.config.js [3]. So the issue is indeed that the published Docker image was built from an older commit, before PR #428 (Multi-language Support) was merged on April 2.

On the default locale being zh: Confirmed — both the default and fallback locale are hardcoded to 'zh' in the i18n config [4]. Notably, PR #475 (French locale) already proposes changing the default to English instead of Chinese.

On the /api path duplication: The axios base URL defaults to http://localhost:5001 [5], while all API calls already include /api/ in their paths (e.g., /api/simulation/create) [6]. So if someone sets VITE_API_BASE_URL=http://example.com/api, requests would indeed become /api/api/.... The .env.example doesn't document this variable at all [7], which makes misconfiguration easy. Also worth noting: VITE_API_BASE_URL is a build-time variable baked into the frontend bundle, so it can't be changed at runtime without rebuilding.

On the locales/ directory: The directory exists at the project root with languages.json, en.json, and zh.json [8]. The COPY . . in the Dockerfile does include it [9], so it should be present in any newly-built image — the issue is just that the current published image predates these files.

Relevant open PRs that address some of these issues:

• PR #478 — Docker improvements including building from source instead of pre-built images
• PR #482 — Fixes the Vite dev proxy configuration for VITE_API_BASE_URL

Rebuilding and republishing the Docker image from the current main should resolve problems 1 and 4. Problems 2 and 3 are architectural and would benefit from the fixes you suggested (and some are already being worked on in the PRs above).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}
  

[666ghj]

Okay, we will release a new version later, and the Docker will be updated accordingly.