readyblockedneeds helpallepicskb

Split web server into standalone Omni/Web service

t-669·WorkTask·
·
·
Created1 month ago·Updated1 week ago·pipeline runs →

Dependencies

Description

Edit

Split web server process from Ava bot runtime.

Implement a dedicated web service entrypoint (Omni/Web.hs) that runs Omni.Web.Core as its own executable/systemd-deployable unit, and stop booting the web server from Omni/Ava/Core.hs.

Acceptance:

  • Ava bot no longer forks/hosts the web server process.
  • New Omni/Web.hs builds as a standalone executable (e.g. web) and serves current Omni web routes.
  • Deployment manifest includes a separate web service for beryllium.
  • Existing behavior for web endpoints remains available via the new web service.

Timeline (9)

🔄[human]Open → InProgress1 month ago
💬[human]1 month ago

Implemented standalone web service split. Added Omni/Web.hs (out: web), removed web fork from Omni/Ava/Core.hs, and deployed new web.service on beryllium via manifest + push.sh --force. web.service now runs /nix/store/mqxgfdrild8yfbwblky2jrza5sadxyh4-web/bin/web --port 8081 and serves tasks/tag UI (health=ok, /tasks=200). Follow-up t-671 created for /news link/routing alignment on standalone web. Evidence: _/tmp/proof-t-669.md

🔄[human]InProgress → Review1 month ago
💬[human]1 month ago

Final cutover completed under t-672: ava now runs without in-process web, and standalone web.service now owns port 8079.

💬[human]1 week ago

Ava verified: implementation present in live tree (file/feature confirmed via inspection). Moving to Verified.

🔄[human]Review → Verified1 week ago