Kristian WindandClaude Opus 5
1bb28ce862
The server side has been finished for a while — VAPID keys, RFC 8291 encryption, delivery on reminders and assignments — and nothing in the browser ever asked for a subscription. web/static/ had a manifest and an icon and no sw.js, so a subscription could not be created at all. The worker handles push and notificationclick and nothing else. There is deliberately no offline cache: the app is a live view of a list other people are editing, and a cached shell serving yesterday's data is worse than the browser saying it cannot connect. Adding one later means versioning and invalidating it, which is a feature rather than a few lines here. Unsubscribing tells the server first. If the browser unsubscribed and then the request failed, the server would keep pushing to an endpoint nothing is listening on, and only a 410 from the push service would ever clean it up. Still not verified against a live push service — this is the client half of a chain whose other half has only ever been tested against the RFC. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
web
The SvelteKit PWA. Not written yet — this directory holds its place so the Docker build has something to copy, and so the frontend stage can tell "not built yet" apart from "the build failed".
The Dockerfile builds this directory when it finds a package.json here, and
otherwise emits a placeholder page. So adding the real app is exactly: put a
SvelteKit project in this directory whose npm run build produces build/.
What it needs to be
- SvelteKit,
adapter-static, output inbuild/. The Go binary embeds that directory at compile time and serves it, falling back toindex.htmlso client-side routes survive a reload. - A PWA: installable, offline reading of already-cached lists, swipe gestures for complete and schedule.
- Nordic minimalism. Dark by default, light available. One accent colour, everything else neutral. Runic mark for Verdande.
- Optimistic on every local action. No spinner ever appears for something the browser could already know the answer to.
Talking to the backend
Same origin — the Go binary serves both. /api/v1 for REST, /api/v1/ws for the
live sync. Session cookie is httpOnly, so the frontend never handles the token
itself.
During development, run the backend on 8080 and point the Vite dev server's proxy at it:
VERDANDE_DATA_DIR=./data VERDANDE_DEV=true go run ./cmd/verdande