Packaging and Shipping Rails Applications in Docker
summary
Claims that Docker images decay and slow deployments get fixed by concrete steps: exploit build cache reuse and split Gemfile into a separate Gemfile layer so bundle install skips on app-only edits, run local mirrors and a local Docker registry proxy (Nexus/Artifactory) to avoid external downtime, and vendor compiled native gems so image pulls and rails console start fast. Measured builds drop from minutes to seconds and deploys become a simple docker pull and run.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:35Background
- 2:18Optimization
- 6:55Build Phase
- 7:21Binary
- 8:57Docker Image
- 9:56Docker File
- 10:10Environment
- 10:55Build
- 11:39Build Cache
- 12:52Build Changes
- 13:58Separate Builds
- 14:47Initial Build
- 15:06Later Build
- 15:25Build Process
- 16:03Deployment
- 17:19Parallelization
- 18:43Docker Pool
- 19:31Availability
- 20:31Value Stream
- 22:15Proxy Servers
- 23:36Bundler
- 24:26Proxy Repository
- 26:34Conclusion
- 28:02Questions
related talks
01h 01mShipping Ruby Apps with Docker
40mContainerizing Rails: Techniques, Pitfalls, & Best Practices
40mDeveloping Ruby Applications with Docker
07mLightning Talk: How Docker Can Change Rails Deployments
43mServer Infrastructure for Rails in 2016
40mContainerized Ruby Applications with Docker
36mDockerization in the land of Ruby
24mBuild Your Own Shipyard