From Pain to Solution: Private Rust Crates with CrabHub
summary
Private registry that uses GitHub for crate blobs and index and plugs into Cargo works: backend stores crates in VCS, honors SemVer, accepts cargo publish, and runs cheaply on Kubernetes. The deployment proves functional but the hastily hand‑coded frontend and unclear trust model — CrabHub’s server touching package bytes so it’s not fully on‑prem — trigger strong community pushback on Reddit. Postmortem leads to an open source rewrite and clearer docs and promises compatible with Cargo publish and backend works on Kubernetes, frontend fails.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:11What is CrabHub
- 3:00Private registries needed
- 5:28VCS-based registry design
- 9:00First iteration challenges
- 10:27Easy setup and Cargo
- 13:19Cost efficiency benefits
- 14:03Reddit feedback
- 16:30UI and perception issues
- 17:57Privacy failures
- 19:44Lack of documentation and transparency
- 21:08Community engagement
- 22:35Trust model problems
- 23:15Sprint limits and plans
- 24:20Key takeaways
- 25:02Postmortem and reboot
related talks
18mThe Death and Rebirth of Docs.rs
48mRelease-plz: releasing crates like it's 2023
36m2 Hours to 10 Minutes: Building Rust Monorepos at Scale with Bazel RBE
45mWhat it's Like to Work on Open Source
30mDIY Private Container Registry
37mDockerising and deploying a full stack Rust + WASM web app
17mShipping a stable compiler every six weeks
37mWrapping Cargo for Shipping