feat: OmniBioAI Web version for app.omnibioai.org#4
Merged
Conversation
Adds a `--mode web` Vite build target that ships the existing React UI
as a browser SPA, kept strictly isolated from the Electron build:
- src/ui/lib/web/{platform,webApi,session}.js — new, standalone web-only
modules. None are imported by existing Electron-shared files; session.js
(relative /auth/* paths instead of a direct http://<lan-ip>:8001 fetch,
which a real browser can't reach) is swapped in only under `--mode web`
via a vite.config.js resolve.alias, so ../lib/session.js and every file
that imports it are untouched.
- vite.config.js — mode-gated: outDir only becomes dist/web and the alias
only applies when mode === 'web'; the default (Electron-facing) build
path is unchanged (verified: build:ui still outputs to dist/ using the
original direct-IP session.js).
- package.json web/web:build/web:preview now pass --mode web explicitly.
- docker/nginx-web.conf, Dockerfile.web — static SPA serving for a new
web-ui container (no backend proxying — that stays nginx-router.conf's
job).
- docker-compose.yml, docker/nginx-router.conf — new web-ui service +
upstream. `location /` intentionally left pointed at workbench for now;
repointing it to serve the SPA at the domain root is a separate,
deliberate follow-up once nothing else depends on workbench being there.
Verified both build modes independently: `npm run build:ui` (Electron)
and `npm run web:build` (web) both succeed and produce distinct, correct
output trees.
- docker/nginx-router.conf — location / now proxies to web-ui instead of
workbench, making the SPA visible at the domain root. Only that one
location block changed; /_svc/workbench (used by Workbench.jsx,
Services.jsx, Launch.jsx) is untouched — a naive global replace of
every `proxy_pass http://workbench;` would have broken that route too,
since the same string appears in both places.
- Dockerfile.web — fixes two build failures found while actually testing
`docker build`, not just `npm run web:build` on the host:
1. @omnibioai/ui is consumed as prebuilt dist/ output, but .dockerignore
excludes **/dist from the build context, so the copied package had
none. Added an explicit build step for it before the app build.
2. packages/omnibioai-ui/package-lock.json is out of sync with its own
package.json (missing @omnibioai/design-tokens) — `npm ci` refuses a
mismatched lockfile by design. Used `npm install` for that one
sub-package instead of hand-patching a vendored lockfile from a
separately-maintained package.
Verified: `docker build -f Dockerfile.web .` succeeds, the container
runs, serves the real index.html at /, responds on /_health, and falls
through unknown paths to index.html (200) via SPA routing.
- .github/workflows/build-web.yml — builds and pushes
ghcr.io/omnibioai/omnibioai-web on push to main. Adds an explicit
`permissions: packages: write` block; without it GITHUB_TOKEN can't
push to ghcr.io and the job 403s.
- docker-compose.release.yml (not docker-compose.yml) gets the image-only
web-ui service. This repo's existing convention: docker-compose.yml
builds every service from source (workbench/control-center both keep
build: active with # image: commented out); docker-compose.release.yml
is the image-only production compose (workbench there has image: with
no build: block at all). web-ui follows that same split — its
build-from-source version stays in docker-compose.yml from the prior
commit, unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Web version of OmniBioAI Studio
Ships the existing React UI as a browser SPA at app.omnibioai.org, isolated from the Electron build.
Changes
src/ui/lib/web/{platform,webApi,session}.js— standalone web-only modules, not imported by any Electron-shared file.session.jsuses relative/auth/*paths instead of a directhttp://<lan-ip>:8001fetch (which a real browser can't reach); swapped in only under--mode webvia avite.config.jsresolve.alias.vite.config.js— mode-gated:outDironly becomesdist/weband the alias only applies whenmode === 'web'. Electron'sbuild:uiverified unchanged (still outputs todist/with the original session.js).Login.jsx,OAuthLinkConfirm.jsx,App.jsx,RoleManagement.jsx,session.js— the OAuth/session-layer work this branch builds on.Dockerfile.web,docker/nginx-web.conf— multi-stage build serving the SPA as static files. No backend proxying in nginx-web.conf — that staysnginx-router.conf's job.docker-compose.yml(build-from-source) /docker-compose.release.yml(image-only) —web-uiservice added to each, following this repo's existing split (workbench/control-center use the same pattern: build in the dev compose, image-only in release).docker/nginx-router.conf—location /now proxies toweb-uiinstead ofworkbench, making the SPA visible at the domain root. Only that one location block changed —/_svc/workbench(used byWorkbench.jsx,Services.jsx,Launch.jsx) is untouched..github/workflows/build-web.yml— builds and pushesghcr.io/omnibioai/omnibioai-webon push to main.Testing
npm run web:build✅ andnpm run build:ui(Electron) ✅ — verified independently, distinct output trees, confirming isolation held.docker build -f Dockerfile.web .✅ — two real bugs found and fixed while testing this (not caught by the host-onlynpm run web:build, since it doesn't reflect a clean container filesystem):@omnibioai/uiis consumed as prebuiltdist/output, but.dockerignoreexcludes**/distfrom the build context — added an explicit build step for that package.packages/omnibioai-ui/package-lock.jsonis out of sync with its ownpackage.json(missing@omnibioai/design-tokens) — usednpm installinstead ofnpm cifor that one sub-package rather than hand-patching a vendored lockfile from a separately-maintained package.index.htmlat/,/_healthresponds, unknown paths fall through toindex.html(200) via SPA routing.nginx -tonnginx-router.confparses every directive correctly; the only failure is upstream DNS resolution (workbench:8000etc.), expected when test-running a single container outside the real compose network.Not yet done
ghcr.io/omnibioai/omnibioai-web:latestwill exist once this CI workflow runs on main.Deploy
After merge:
Visit: https://app.omnibioai.org