will
c4726c2953
Continues the full-year sanctoral import: Ss. Tiburtius and Susanna, Ss. Hippolytus and Cassian, the Vigil of the Assumption, St. Joachim (Duplex II Classis, own full proper content), St. Hyacinth, St. John Eudes, St. Jane Frances de Chantal, the Immaculate Heart of the BVM (Duplex II Classis, instituted 1942, full proper content), St. Joseph Calasanctius, and St. Raymond Nonnatus. Several of the new fixed dates (Aug 16, 17, 21, 22) fall within or adjacent to St. Lawrence's and the Assumption's overlapping octave windows and now win outright there under the ordinary-feria/ordinary- sunday precedence rules, displacing what several existing tests expected to be bare octave commemorations or ferial fallbacks. Updated: - august-sanctoral.test.ts: Aug 22 now correctly shows the Immaculate Heart of Mary as the winner, with the Assumption's octave still commemorated alongside her. - day-label.test.ts: the two octave-priority tests pinned to Aug 17 (now St. Hyacinth's own day) moved their "day 8 alone" case to All Saints' own octave (Nov 8, still open); the two-octaves-overlap comparison can no longer be demonstrated via any real date in this app since every day where St. Lawrence's and the Assumption's octaves genuinely overlap is now real sanctoral content -- the underlying `pickWinningOctave` mechanism itself stays covered by tests/calendar/octaves.test.ts's own synthetic-data unit test. - vespers.test.ts: the Thursday Ps 138 split test moved off Aug 20, whose own first Vespers is now claimed by St. Jane Frances de Chantal's fixed day (Aug 21). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.)