6 Commits

Include renames

Author	SHA1	Message	Date
Your Name	df173879fa	fix: route IM clients through current origin	2026-10-19 17:23:34 +08:00
Your Name	d7bfd2f417	fix: route production IM API correctly	2026-10-19 11:05:50 +08:00
richjohnrambo	8a26a4ccf9	fix production attachment file origin	2026-10-14 15:22:46 +08:00
richjohnrambo	b7f214daf5	remove legacy root Tinode webapp	2026-10-14 14:01:52 +08:00
Your NameandClaude Sonnet 5	db0f8e4543	fix(deploy): build/serve the new web/ Vite app instead of the old webpack build ... The deploy pipeline (.gitea/workflows/deploy.yml -> Dockerfile) never got updated when the frontend was rewritten under web/ -- it was still doing `npm ci`/`npm run build` at the repo root and copying the old app's umd/, css/, index.html, etc. into the nginx image. Every deploy therefore kept shipping the old app regardless of what was actually on dev, no matter how much of the rewrite had landed. Dockerfile now builds from web/ (Vite) and copies its self-contained dist/ output (index.html + content-hashed assets/, no separate umd/css/ img/audio/manifest/service-worker/firebase files -- none of that exists in the new app). VITE_TINODE_API_KEY is what src/lib/config.ts actually reads (Vite only exposes VITE_-prefixed env vars to client code), so the existing TINODE_API_KEY build-arg is now renamed into that on its way into the build environment instead of passed through under its old name. nginx.conf updated to match: index.html stays no-cache (its URL never changes, so a stale cached copy would keep pointing at deleted asset filenames after a deploy), assets/ gets a long immutable cache (Vite content-hashes every filename there, so a new build never reuses an old URL). Dropped the old umd/ and img/ location blocks, neither exists in the new build. Verified locally: `docker build` succeeds, the container serves the new app's real index.html/assets with the intended cache headers, and an unknown client-side route (/messages/slf) correctly falls back to index.html. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-09 20:56:21 +08:00
Your Name	85ac8ce43b	接入Gitea Actions蓝绿发布：API_KEY构建时注入、新增Dockerfile ... - src/config.js 的 API_KEY 改为从构建时环境变量 TINODE_API_KEY 注入， 不再依赖官方demo默认值；未设置时保留原demo key作为本地快速测试的兜底 - webpack.config.js 新增 DefinePlugin 完成注入，并自动加载(gitignored的) .env.local，开发者本地调试不需要每次手动export - 新增 Dockerfile(node构建+nginx serve) 和 docker/nginx.conf - 新增 .gitea/workflows/deploy.yml：手动触发的蓝绿发布流程	2026-08-11 12:40:12 +08:00