A Happy End for the Docker-for-Development Drama
summary
Docker as a dev environment often breaks on macOS: file I/O goes through a VM and FUSE and costs ~100µs per file, turning a native 400ms request into ~3s with delegated mounts. The solution is a docker‑compose template plus a shared reverse proxy and local-beach tooling that uses an init copy plus FS events synchronization into a volume, stable SSH host keys, env var cascades and pinned PHP images. The demo runs, speeds feel acceptable and the setup is reusable.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:45No compromise on tooling
- 5:32Easy to setup Easy to switch
- 8:46Options without Docker
- 12:33Problem #1 Cumbersome setup
- 13:07create templates & scripts
- 15:20Problem #2
- 23:24Problem #4 SSH access
- 26:48Using Composer in the right environment
- 54:39Docker in Production
related talks
45mDocker for dev
29mDeveloping JS Applications Using Docker Containers
05mInstant Self-contained Development Environments
02h 06mDocker Community All-Hands 7 - Day 2
32mBoost your Cloud Foundry Edit-Build-Deploy-Test-Debug Speed!
31mEnvironments as a Service: improve DX
26mWhat's New in Docker Desktop
50mInstant Self-contained Development Environments for Everyone