feat(vcs): live on vcs.coline.dev; fewer round trips, small objects in the database, batched git view
Radin committed
- Author
- Radin · radin@coline.appOct 27, 2026 at 23:45
- Committer
- Radin · radin@coline.appOct 27, 2026 at 23:45
- Parents
- 3b7c11dddde7
feat(vcs): live on vcs.coline.dev; fewer round trips, small objects in the database, batched git view Deployed as the coline-vcs Worker. Found on the live host: - new Upstream repos answer 404 while provisioning: project creation waits, and "not found" isn't cached; Upstream lookups run in parallel and are shared per data center (Cloudflare cache) - Durable Object SQLite takes at most 100 bound parameters (local dev allows more): lookups batch by 100 and local dev fails the same way - storing small uploads in R2 was most of a land's time: bundles up to 512 KB are stored in the project's database and moved to R2 packs in batches once there are 16 MB of them - the git view pushed one commit per version and fell behind bursts: up to 64 waiting versions go in one push Protocol: a land is one call (the change's record and newest save ride along, with the takeover check), a change and its save are one call, small uploads skip the missing check and refresh is one call (2 requests per land, was 8). Also: refresh fills versions others landed just before yours, and getting a workspace where a deleted one was works. Live from us-west: a land takes ~0.3 s, 64 agents landing at once all land in 0.8 s, and the git view of 291 versions clones, passes fsck --strict and matches vcs main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
10 files changed+155−48