Deployment Overview
SnapTeX Web has two explicit deployment modes built from the same UI.
| Mode | Command | Remote projects | Offline PWA |
|---|---|---|---|
| Static | npm run web:build-static | No | Yes |
| Server | npm run web:build-server | Yes, authenticated | Application shell only; projects require the server |
Choose by where project files should live:
- Choose Static when users open local folders or browser workspaces and the host should serve only application files.
- Choose Server when named projects must remain on a controlled machine and be opened through an authenticated API.
The server edition includes the same local and browser-workspace features as the static edition. It adds remote project access; it does not replace local editing.
Static Web
Use the static build for GitHub Pages, object storage, or any ordinary static host. It supports local directory handles, browser workspaces, the demo, project ZIP export, and offline application assets.
SnapTeX Server
Use the server build when project files should remain on a machine you control and be accessed by project name. The Node service adds login, server-side sessions, CSRF checks, and a constrained project file API.
Android status
The repository reserves apps/android for a future wrapper around the standalone host. There is currently no production APK build. The reusable core and standalone host are already separated so the Android shell can reuse them without embedding VS Code APIs.
Reading path
- For GitHub Pages, object storage, or a local static host, use Static Web and PWA.
- For a private or public remote-project service, use SnapTeX Server, then complete the Security Model checklist before exposing it.