feat(host-agent): serve built console via SPA-aware static mount

Add an optional single-process mode where the backend serves the built
console bundle itself, so operators don't need a separate `npm run dev`
for edge/dev setups. When RUNTIME_CONSOLE_STATIC_DIR points at the
console dist directory, the app mounts a SpaStaticFiles handler at /ui/
(with 404 fallback to index.html for client-side routing) and redirects
/ to /ui/. The console build uses an empty VITE_API_BASE_URL for relative
API paths (same-origin, no CORS), and Vite's base is set to /ui/ so
assets resolve under the mount. /console/* JSON API is unchanged and is
shared by both serve modes.

api.ts now treats an explicitly-empty VITE_API_BASE_URL as "use relative
paths" instead of falling back to the dev default, which previously
forced absolute URLs even in same-origin builds.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

This commit is contained in:

q792602257

2026-07-14 13:29:58 +08:00

co-authored by

Claude Opus 4.6

parent 8381b3068a

commit c0a653fa3f

4 changed files with 60 additions and 4 deletions

									
										console/vite.config.ts
									
		+1
		
												View File
												
				@@ -3,4 +3,5 @@ import vue from "@vitejs/plugin-vue";

				export default defineConfig({

				  plugins: [vue()],

				  base: "/ui/",

				});