will
4bc5fdd77f
Found 137 chapters missing from src/data/scripture/ despite the recent bulk import, scattered oddly across ~30 otherwise-covered books. Located the original "Unbound Bible" source archives (douay_rheims.zip/latinv.zip) the earlier import must have used but never preserved in-repo, and re-parsed directly from them. 118 new chapters authored, plus the 3 hand-authored short books (Jude, Obadiah, Philemon) replaced with source-derived text — small wording differences from the hand-typed drafts confirm going back to source was worth it. Store now at 1157 chapter files. Deliberately left unauthored rather than risk bad content: - Daniel 4-14 and Esther 11-16: this digitization's Latin side only has Daniel 1-3 and Esther 1-10 at all (English has the rest). - 12 chapters where the Douay-Rheims side has a corrupted, misnumbered block (e.g. isa-25's tagged verse 1 actually carries verse 11's text) rather than simply missing content -- importing under the source's own wrong verse numbers would silently attach mismatched text to real citations, worse than leaving them missing. Widened bulk-import.test.ts's invariant to tolerate up to 2 genuinely isolated missing-English verses per chapter (extends the pre-existing isa-33/sir-36 pointing-split-half-verse allowance to also cover true source gaps, e.g. an in-file "Transfer interrupted!" download-corruption artifact at matt-12:43), while still failing loudly on anything resembling the corrupted-block pattern above. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Je2mXNHoXmi1DS3xEL67rH
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.)