will
65a1f359e6
- nocturnReadingIds no longer lets a demoted commemoration's temporal id (equal to the plain governing-Sunday temporalId) sneak a Sunday's own homily into an unrelated weekday's pool via the commemorations loop — a second code path than the one a prior fix gated, affecting 18 days/year. - Reading pool order now follows id priority (winner first, then every temporal commemoration, then every sanctoral commemoration) instead of raw nocturn-tag/array order, matching the day label's own temporal-then-sanctoral convention. - gospelReadingPart now falls back to the paired homily's own responsory when the Gospel entry has none of its own, instead of silently dropping it. - Patristic source labels now show "(for <occasion>)" so a reader can tell which occasion a pooled reading belongs to on a multi-reading day. - collectCommemorations no longer restates the plain generic temporal label (e.g. "Saturday in the 15th week after Trinity") once anything else is already being celebrated — general, not Ember-specific. Updated 4 day-label tests that encoded the old behavior. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MKC2QQGLYo2UTiDjDyWEkW
vu
A static, offline-first PWA for praying the Divine Office — Matins, Lauds, Prime, Terce, Sext, None, Vespers, and Compline — in bilingual Latin/English, for any given date.
This isn't a reconstruction of any single historical breviary. It's a personal design that
draws on several historical sources without reproducing any one of them exactly: hour
structure chiefly from the Monastic Tridentinum (1617), precedence/rubrics from Divino
Afflatu, and a calendar merged from both the Tridentine 1906 and Divino Afflatu calendars,
with more generous handling of commemorations and octaves than any one historical rite used.
See CLAUDE.md (gitignored, not shipped in this repo) or the project's own notes for the full
rationale if you're extending it.
There's no backend and no database — everything is a pre-built static bundle, and the app is designed to keep working fully offline once it's been loaded once.
Development
Requires Node.js (developed against Node 20+).
npm install
npm run dev # start the Vite dev server
npm run build # type-check (tsc --noEmit) and produce a production build in dist/
npm run preview # serve the production build locally
npm test # run the test suite (vitest)
Run a single test file or a subset by name:
npx vitest run tests/hours/vespers.test.ts
npx vitest run -t "some test name"
Running in production
The app is entirely static once built, so "running it" just means serving dist/ — any static
file host works, as long as it falls back to index.html for unknown paths (the app does its
own client-side routing for URLs like /2026-08-09/prime).
Docker
A Dockerfile builds the static bundle with Node and serves it with Caddy:
docker build -t vu .
docker run -p 8080:80 vu
Or with Docker Compose (docker-compose.yml is included):
docker compose up -d --build
This serves the app on http://localhost:8080. Put a reverse proxy/TLS terminator in front of
it for a real deployment; the container itself just listens on port 80 internally and has no
configuration, secrets, or external dependencies.
Without Docker
Any static file server works — build the app, then serve dist/ with SPA-style fallback
routing. For example, with Caddy directly:
npm run build
caddy file-server --root dist --listen :8080
(For a real deployment you'll want a fallback rule so unknown paths resolve to index.html —
see the Caddyfile in this repo for the pattern.)