Containerizing Local Development... Is It Worth it?
summary
Argues that containerizing local development can be helpful but is a workflow tradeoff: uses Docker Community Edition and docker-compose, shows three concrete setups (single app, multi-repo bootstrap orchestrator, gem workspace), provides Dockerfiles and compose examples, and demonstrates that multi-app bootstraps speed onboarding and mirror production while gem work is painful — not worth it for gem development. Notes real drawbacks: VM slowness, macOS filesystem sync issues, extra RAM/drive cost, and that rebuilds fix most breakage.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:29Ground Rules
- 4:46Dockerfile
- 9:13docker-compose.ymly
- 12:39docker-compose commands
- 16:15Scenario-One or more independent apps (alternative setup)
- 22:04Scenario - Multiple Apps, Multiple Teams (docker-compose.yml)
- 24:30Scenario - Multiple Apps, Multiple Teams (compose files per-team)
- 29:57Scenario -Simple Ruby Hacking / Gem Dev?
- 33:17Shared Amongst All Scenarios (CON)
related talks
27mDesigning a local development environment based on containers
36mDockerization in the land of Ruby
29mPackaging and Shipping Rails Applications in Docker
45mDocker for dev
40mDeveloping Ruby Applications with Docker
31mFrom Local Setup Nightmares to DevContainers: Our Experience Report
21mMaking Docker Actually Work
37mUnveiling the Ultimate Showdown A Comparative Analysis of Local Development Tools