Building Gophercises
summary
A production site gets built as a tiny codebase: exercises live in one big Go slice, auth is email magic links, deploys are rsynced to a $5 DigitalOcean droplet, and assets embed into a single binary via Packr so only one file uploads. CLI uses Cobra and Mage, storage uses bolt DB, templates render server side with decorator and service objects. Manual verification takes 30–60 seconds, downtime is one second on deploy, no automated tests, and the whole thing ships and works.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:10Why this talk
- 2:39Content Management System
- 4:06Authentication System
- 5:30Deploying
- 7:03Buffalo Packer
- 8:42Mage
- 11:19Rendering
- 12:54Templates
- 13:52Decorator
- 16:57Service Objects
- 19:24Testing
- 21:15Key Takeaway
related talks
45mBuffalo: Rapid Web Development in Go
33mUnsucking Your Team's Development Environment
29mBuild Your Developer Tools in Go
35mState of the Gopher Nation
17mHow we built and launched Gopherize.me
29mBest Practices for Production Environments
46mRediscovering Go
46mSimplifying Scalable Cloud Application Development with Go