Rebuilding the heart of the Ruby community in 60 hours
summary
A security breach forces rubygems.org to be rebuilt publicly and reproducibly; the team reconstructs the stack with Rails, nginx, Postgres, Redis, memcached and Chef, migrates gems to S3, adds datadog monitoring and Jenkins automation, and debates gpg vs x509 signing for package trust. The site relaunches after rebuilt in ~60 hours but still runs on three AWS instances so availability and multi‑provider CDN ideas with Fastly remain open work.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:21How the incident started
- 3:38The rebuild
- 9:39Installing Postgres
- 11:32Rebuilding
- 15:36Gem signing
- 18:18Rubygems
- 20:52Human capital
- 23:32Outro
related talks
37mExtreme Makeover: Rubygems Edition
35mState of the RubyGems
44mThe Technical and Organizational Infrastructure of the Ruby Community
37mOpen Source Maintenance
35mMaking it on your own and the pitfalls of gem dependencies
29mTaking over Someone Else's Open-Source Projects
27mRuby in 79 AD (Open Sourcing my Role as Indiana Jones)
17mBuilding Secure Open Source Communities From the Ground Up