Ready To Code: Automate Your Development Environment
summary
Claims that a complete dev VM boots from source in minutes and that a new hire is up and running in ~15 minutes. Uses Vagrant with VirtualBox/VMware, synced folders, port forwarding and Puppet or shell provisioners to install RVM Ruby, Postgres, gems (bundler, mailcatcher). Provides a git repo with Vagrantfile and modules, demonstrates creating a Rails/Postgres environment, reproducing it by destroy/up, and notes NFS and performance tweaks when shared folders slow asset serving.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 0:45The Problem
- 2:14Virtualization
- 3:00Development Environments
- 3:28Benefits
- 5:05The Bad
- 6:28What is Vagrant
- 6:52Why Vagrant works
- 9:05Sharing VirtualBox Configuration
- 11:16Configuration Options
- 11:37Out of Sync Folders
- 12:13Port forwarding
- 13:42Shell Provision
- 14:22Puppet Manifest
- 15:30Modules
- 15:44RVM Module
- 17:02Update manifest
- 17:25Puppet configuration
- 18:09Install Ruby
- 18:23Install Puppet
- 19:00Puppet Modules
- 19:11Postgres Modules
- 20:00Install Development Library
- 20:58Errors
- 21:22Scripting
- 21:45Troubleshooting
- 22:29Restarting Postgres
- 22:44Ready to go
- 23:00Ignorance
- 23:18Git submodules
- 23:40Git configuration
- 24:07Default config
- 24:36Startup script
- 25:23Demo
- 27:06The Good Parts
- 29:11Vagrant Documentation
- 29:57Thank You
related talks
46mBuilding Virtual Development Envrionments with Vagrant
54mReproducible and Portable Development Environments with Vagrant
30mUsing Ruby to Automate Your Life
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
33mUnsucking Your Team's Development Environment
33mUsing Ruby to Automate Your Life