feat(web-studio): bundle web-studio into docker, serve at /studio

[ZaynJarvis]

Description

Bundles the web-studio Vite SPA into the OpenViking docker image and exposes it at /studio/ on the same OV server origin (port 1933). After this change, running the image is enough to get both the API and the new web frontend on a single port — no separate hosting, no CORS dance, no extra deployment unit.

Type of Change

• New feature (non-breaking change that adds functionality)
• Bug fix (non-breaking change that fixes an issue) — same-origin default for ovClient

Changes Made

• Dockerfile: new web-studio-builder stage (node:20-bookworm-slim) runs npm ci + npm run build -- --base=/studio/ and emits /web-studio/dist. The runtime stage copies /web-studio/dist → /app/web-studio/dist and exports OPENVIKING_WEB_STUDIO_DIR=/app/web-studio/dist so the server picks it up out-of-the-box. The npm install layer is cached on /root/.npm keyed by TARGETPLATFORM, so rebuilds only re-run when package.json / lockfile change.
• openviking/server/app.py: when OPENVIKING_WEB_STUDIO_DIR (or the in-repo fallback path) contains a built dist/, register /studio and /studio/{path:path} handlers. The latter serves matching asset files when they exist, and falls back to index.html for unknown paths so TanStack Router deep-links survive a hard refresh. index.html is sent with Cache-Control: no-store to avoid stale shells. The legacy console/static favicon directory is replaced by the same web-studio/dist (web-studio now owns the canonical icons), so the top-level /favicon.* and /mcp/favicon.* routes stay backwards-compatible without a separate static folder.
• web-studio/public/: add favicon.ico, favicon-32.png, apple-touch-icon.png so the build emits the icon set the server expects.
• web-studio/src/lib/ov-client/client.ts: drop the hardcoded 'http://127.0.0.1:1933' fallback in the module-level ovClient initializer. normalizeBaseUrl already falls back to window.location.origin in browsers, but the literal short-circuited it — so when the SPA was served by OV at /studio/, every API call still tried to hit the user's local 127.0.0.1:1933 and failed. Removing the literal makes the default same-origin, which is the right answer for every "served by OV" shape (docker bundle, port-forwarded docker, reverse-proxied custom domain). The in-app Connection dialog can still override the base URL at runtime (persisted to localStorage), so dev workflows running vite separately can either set VITE_OV_BASE_URL or just punch in the local URL once.

Testing

• Existing OV server unit tests pass locally (no test surface changed)
• web-studio npm run build passes
• End-to-end smoke on a live Railway deploy of the resulting image:
  • GET /health → 200
  • GET /studio/ → 200 (SPA shell)
  • GET /favicon.ico → 200
  • ov add-resource <file> → upload + semantic/embedding queues drain successfully
  • ov add-memory '<text>' → 200, retrievable via ov find
  • Loading /studio/ in a browser issues API calls back to the deployed origin (same-origin), not localhost
• Tested on platforms:
  • Linux (CI / Railway)
  • macOS (local docker build)

Additional Notes

• Outside docker, the server falls back to <repo>/web-studio/dist so npm run build inside web-studio/ is enough to enable /studio/ locally without setting any env var.
• This is intentionally minimal — no changes to existing console routes; the legacy /console static path is untouched. A follow-up PR can deprecate / remove openviking/console/static once the team is comfortable.

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🏅 Score: 78

🧪 No relevant tests

🔒 No security concerns identified

✅ No TODO sections

🔀 Multiple PR themes Sub-PR theme: Add web-studio build stage to Dockerfile Relevant files: Dockerfile Sub-PR theme: Serve web-studio SPA and handle favicons from web-studio dist Relevant files: openviking/server/app.py Sub-PR theme: Update ovClient default baseUrl to use ENV_BASE_URL only Relevant files: web-studio/src/lib/ov-client/client.ts

⚡ Recommended focus areas for review Favicon Routes Regression The favicon routes are now only registered when the web-studio dist directory exists and contains all required files. This breaks backwards compatibility for setups that don't use the web-studio bundle, as the favicon routes are no longer available at all. _favicon_source = _studio_dir if _studio_dir.is_dir() else None if _favicon_source is not None and all( (_favicon_source / fname).is_file() for fname, _ in _favicon_files.values() ): def _make_favicon_handler(filename: str, media_type: str): path = _favicon_source / filename async def _handler(): return FileResponse(path, media_type=media_type, headers=_favicon_headers) return _handler for _route, (_fname, _mime) in _favicon_files.items(): app.add_api_route(_route, _make_favicon_handler(_fname, _mime), include_in_schema=False) Missing Base URL Fallback Removed the default fallback to http://127.0.0.1:1933 for the ovClient baseUrl. If ENV_BASE_URL is not set (e.g., in local development when running web-studio separately via Vite dev), the baseUrl becomes undefined, potentially breaking API connectivity. export const ovClient = createOvClient({ baseUrl: ENV_BASE_URL, bindSdkClient: true, })

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.