# Cloudflare Workers Setup — Linear Void

Linear Void uses Cloudflare Workers for two purposes:

| Product     | Purpose            | What                                                                                 |
| ----------- | ------------------ | ------------------------------------------------------------------------------------ |
| **Workers** | Static SPA hosting | Vite-built frontend (`frontend/dist`) served as Worker static assets                 |
| **Workers** | Edge cache logic   | `infrastructure/cloudflare/worker.js` — adds immutable cache headers to HLS segments |

Both are managed under **Workers & Pages** in the Cloudflare dashboard.

## Dashboard URLs

| Resource                 | URL                                                                                                                 |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------- |
| Workers & Pages overview | `https://dash.cloudflare.com/deb11491c54ec53a24772e98ac6d8128/workers-and-pages`                                    |
| Worker: linearvoid       | `https://dash.cloudflare.com/deb11491c54ec53a24772e98ac6d8128/workers/services/view/linearvoid/production/settings` |
| API tokens               | <https://dash.cloudflare.com/profile/api-tokens>                                                                    |

## Worker: `linearvoid` (edge cache headers)

The Worker at `infrastructure/cloudflare/worker.js` runs on the `linearvoid` Workers service. It intercepts requests and adds immutable `Cache-Control` headers to `.m4s` segment files.

Deploy via Wrangler CLI:

```bash
npx wrangler deploy infrastructure/cloudflare/worker.js
```

Or paste into the Workers dashboard at the URL above (Quick Edit).

## Worker: static frontend

Serve the Vite-built SPA (`frontend/dist`) as Worker static assets:

1. Build the frontend: `cd frontend && npm run build`.
2. Bind `frontend/dist` to the Worker as static assets (Workers Static Assets / `assets` in `wrangler.toml`).
3. Attach the `linearvoid.tv` custom domain to the Worker.

See [gitea-cloudflare-workers.md](./gitea-cloudflare-workers.md) for the automated deployment workflow.

### Build-time variables

The `VITE_PUBLIC_*` values are baked into the bundle at build time by Vite (`vite.config.ts` uses `envDir: ".."` to read them from the repo root). They are supplied by the Gitea Actions build environment from Gitea secrets — not as Worker runtime variables. The static-assets Worker has no runtime JavaScript, so it reads no `env` at request time.

| Name                                     | Value                                           |
| ---------------------------------------- | ----------------------------------------------- |
| `VITE_PUBLIC_APP_URL`                    | `https://linearvoid.tv`                         |
| `VITE_PUBLIC_WS_URL`                     | `wss://linearvoid.tv/ws`                        |
| `VITE_PUBLIC_HLS_URL`                    | `https://media.linearvoid.tv/hls/playlist.m3u8` |
| `VITE_PUBLIC_ADMIN_DEFAULT_MODERATOR`    | `boogers`                                       |
| `VITE_PUBLIC_ADMIN_DEFAULT_ROOM`         | `main`                                          |
| `VITE_PUBLIC_ADMIN_MODERATION_LOG_LIMIT` | `50`                                            |

Backend services (playout, chat, nginx) read their own runtime variables (`ADMIN_*`, `HLS_*`, `PLAYLIST_PATH`, `R2_*`, `DATABASE_URL`, `REDIS_URL`) from the container environment — see [`.env.example`](../../.env.example).

## Custom domains

- `linearvoid.tv` → Worker (static SPA)
- `www.linearvoid.tv` → redirect to `linearvoid.tv`
- `media.linearvoid.tv` → R2 bucket (separate; not a Worker)

## Related

- [Gitea to Cloudflare Workers deployment guide](./gitea-cloudflare-workers.md)
- [Cloudflare & UptimeRobot checklist](./cloudflare-uptimerobot-checklist.md)