Make the Ordo PDF cacheable and version-aware #50

New issue

Open

opened 2026-07-01 00:59:07 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 00:59:07 +00:00

(Migrated from github.com)

Problem

PDF rendering is comparatively expensive, so generated Ordo PDFs must be cached immutably per key and only regenerated when the data-version changes.

Acceptance criteria

The PDF response sets ETag and immutable cache headers keyed by inputs and data-version.
Repeated requests are served from cache without re-rendering.
A data-version bump invalidates cached PDFs.
Caching behavior is covered by tests.

Notes

Consider pre-generating current-month PDFs in the static build for the busiest paths.

## Problem PDF rendering is comparatively expensive, so generated Ordo PDFs must be cached immutably per key and only regenerated when the data-version changes. ## Acceptance criteria - [ ] The PDF response sets ETag and immutable cache headers keyed by inputs and data-version. - [ ] Repeated requests are served from cache without re-rendering. - [ ] A data-version bump invalidates cached PDFs. - [ ] Caching behavior is covered by tests. ## Notes Consider pre-generating current-month PDFs in the static build for the busiest paths.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Api#50

No description provided.

Rows
Columns