Ready To Code: Automate Your Development Environment
summary
Claim: a checked-in Vagrant configuration boots a full Ruby/Postgres dev VM so a new developer is coding in about 15 minutes using Vagrant+VirtualBox, with provisioning via shell or Puppet RVM module. Built items: box templates, synced folders, port forwarding, Postgres init SQL, gems like bundler and mailcatcher. Results: it works and is easy to destroy and rebuild; surprises: base boxes are ~6–7GB and shared-folder disk IO is slow so NFS and service restarts are needed.
AI-written summary · about
chapters (41)
- 0:00Introduction
- 0:45Problem
- 2:14Virtualization
- 3:00Development Environments
- 3:28Benefits
- 5:05The Bad
- 6:29Vagrant
- 6:52Boxes
- 7:29Vagrant File
- 7:49Vagrant Box Add
- 8:47Vagrant Configuration
- 9:06Vagrant URL
- 11:16Configuration Options
- 11:37Sync Folders
- 12:02Home Folder
- 12:12Port Forwarding
- 12:45Configuration
- 13:38Simple Shelter
- 14:03Shell Scripts
- 14:23Puppet
- 15:30Modules
- 16:38Run aptget
- 17:02Update manifest
- 17:26Puppet configuration
- 18:09Install Ruby
- 19:00Custom Puppet Modules
- 19:11Postgres Module
- 20:44Use Postgres
- 20:58Failed
- 21:22Change Default Database
- 21:47Troubleshooting
- 22:29Restart Postgres
- 22:53Share with Team
- 23:17Get SubModules
- 23:46UserConfig
- 24:06Config
- 24:36Startup Script
- 25:23Quick Demo
- 26:43Benefits of Vagrant
- 27:47Cons of Vagrant
- 29:11Vagrant Documentation
related talks
46mBuilding Virtual Development Envrionments with Vagrant
54mReproducible and Portable Development Environments with Vagrant
20mHow fast can you onboard a new team member?
25mVagrant: The Stick and Carrot of a DevOps Leader
27mGetting your Python Development Environment Ready with Vagrant
38mEasy Ruby Development and Deployment with Otto
30mUsing Ruby to Automate Your Life
19mUnbox Development in Production