4 Commits

Include renames

Author	SHA1	Message	Date
Daan MeijerandClaude Fable 5.1	f8cb17903b	voyager 3: the window in the Rust edge ... The indexer finishes files and releases by posting time instead of the range path: the frontier is the median Date of the last 1,024 plausible dates (within 7 days of it; a run of 1,024 agreeing dates moves it), and a release is finished, judged and written once the frontier is 24 h past its last part, flagged edge when posted within a day of the block's start. At the block's end the rest is written provisionally as edges for the block merger. Files short of parts stay in their release (partial: the store writes complete = false). Gone: fragments and the cut-off, uploads_of (online now), check.ts and the fixture comparison; CI replays the fixtures through edge-bench instead. The wire carries finished, edge and partial. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-25 21:28:35 +01:00
Daan MeijerandClaude Opus 5.5	5109481d67	The Rust worker is the product: edge/, built and checked in CI ... User: Rust is the product (option a). tools/edge-bench-rs moves to edge/ (crate edge; binaries edge-node, the worker, and edge-bench, the replay). CI's new job edge runs cargo test and edge/check-fixtures.sh: both RangeIndexers on three committed captures (edge/fixtures, 25k overview lines each of a.b.models, a.b.ath and a.b.boneless in 5 chunks, 3.5 MB), compared field by field with check.ts; deploy waits for it. The TypeScript RangeIndexer stays as check.ts's reference. README: what it is now; the benchmark findings as history. Random names: looksRandom missed long tokens of capitals and digits ("51294P1CUKR2R35X", release 74539068, readable and a Newznab title). 12+ capitals and digits switching 6+ times between them are random (COD4MW2REMASTERED switches 4 times, BEATLES1964REMASTER twice); both implementations, identical on the fixtures. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-11 20:01:18 +02:00
Daan MeijerandClaude Opus 5.5	84d3af5511	Rebuild: a proper deployment for voyager 2 ... Dockerfile with two targets: app (compiled AdonisJS, production dependencies, Node 24.16 as in CI) and edge (the Rust worker, cargo caches as build mounts). deploy/compose.yaml, project usenet-rebuild: postgres (data on the HDD, catalog tablespace on the NVMe), migrate, web, coordinator, edge; edge-ts and ace behind profiles. deploy/deploy.sh (~/bin/deploy-usenet-rebuild on homelab): fetches the commit (must be on rebuild), builds, migrates, recreates web, coordinator and edge (the worker stopped first), never postgres. CI deploys a push to rebuild that passes: the deploy key's forced command passes "deploy-rebuild <sha>" on. A push to master no longer deploys from this branch's workflow. deploy/README.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-10 00:01:38 +02:00
Daan MeijerandClaude Opus 5.5	d3e774a489	Add Gitea Actions: test every push, deploy master to homelab ... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-03 20:04:48 +02:00