Publish: write only changed items (don't re-version unchanged pages, assets, theme or asides) #5
Labels
No labels
feature request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rhelwig/DecentSite#5
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Every release re-versions every page, asset, theme and aside, even when nothing changed.
validateReleaseRequestrequires every record to share the releasepublishBatchId.Seen on 2026-10-10: publishing one new post plus a small theme/aside change took about 20 writes. All 11 existing pages had an identical
bodyHashto their previous Platform version. Only id, createdAt, previousVersionId, publishBatchId and sequence differed. Only-changed releases would need about 7 writes.Wanted:
validateReleaseRequest/ inspection) and Stub resolution.Cuts fees, time, and the number of steps that can fail. It matters most for large sites.
Follow-up notes: https://git.ronhelwig.com/rhelwig/DecentSite/src/branch/main/docs/PUBLISH-FOLLOWUPS-2026-10-10.md
Design is written up (doc only, no code) in PR #10:
docs/SPECS.md§ Only-changed releases (planned).inspectReleaseRequestchecks that each reused record is in the parent manifest and already exists on Platform.version: 2, so older Auth builds fail closed.Expected for ronhelwig.com release 2: about 20 writes down to about 7. Implementation has not started.
First implementation PR: #11 (branch feat/only-changed-versioning,
aaeec1b). It adds release-request version 2, has Admin reuse unchanged versions (opt-in with DECENT_RELEASE_REUSE_UNCHANGED=1, which needs Auth 0.1.20+), and makes validation/inspection fail closed on bad reuse. Tests: 176/176 pass.Still to do after #11: an Admin setting instead of the environment variable, "unchanged (already on Platform)" wording in Auth plus a count on the fee screen, and rollback by reference. Once Auth 0.1.20 is built and installed, we'll measure the write-count saving with the #6 timing logs.
Status: the first increment of only-changed releases is on
main(PR #11, merge745c57ed08).~/.config/systemd/user/decent-site-admin.service.d/reuse-unchanged.conf: thensystemctl --user daemon-reload && systemctl --user restart decent-site-admin. To disable it, delete that file, reload and restart. Putting the same line in~/.config/decent-site/admin.env(the unit's EnvironmentFile) also works.I'm leaving this open until a real publish is measured: the write count and fee should drop to just the changed items. Timing data from #6 should show it.