Veritas can be installed from a trusted remote/server host as a browser PWA. Use this only with HTTPS, auth enabled, localhost bypass disabled, and the web app, /api, /ws, manifest, icons, and service worker served from the same public origin or subpath.
iOS uses Safari’s Add to Home Screen flow instead of the browser install prompt. The installed shell keeps the Veritas origin and session behavior from Safari.
Chrome shows the install prompt only when the manifest and service worker are reachable from the current origin.
The service worker caches only the static app shell, manifest, icons, and same-origin static assets. It does not cache /api responses, WebSocket traffic, task data, work products, tokens, comments, or mutation responses.
When the device is offline or realtime sync is reconnecting:
For a subpath deployment such as https://kanban.example.com/veritas/, build and serve the web app with VITE_BASE_PATH=/veritas/. The manifest uses relative start_url and scope, and the service worker registers under the same base path.
Reverse proxies should route these paths to the same Veritas host:
//api/ws/manifest.webmanifest/sw.js/favicon.png/apple-touch-icon.png/icons/*/assets/*If the app is served under a subpath, apply the same subpath prefix to each route.