Developing JS Applications Using Docker Containers
summary
Argues that using Docker makes JavaScript development reproducible and avoids OS/version drift, showing concrete Dockerfiles, docker-compose, and a multi-stage build that installs private repo keys then deletes them so final images are clean. Demonstrates cached layers to speed rebuilds, dockerfile layers cached, volume mounts for live edit with node hot reload, volume mapping for hot reload, and port mapping so VS Code or Chrome can attach to a running process, attach debugger via mapped ports. Reports this setup works in production and for onboarding.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:34Agenda
- 1:04Which Version of Nodejs Do You Use
- 8:04What Docker Containers Are
- 8:15The Problem That Docker Containers Are Trying To Solve
- 14:51Create a Docker Compose File
- 16:11Volumes
- 23:32Dockerfile
related talks
05mInstant Self-contained Development Environments
45mDocker for dev
02h 06mDocker Community All-Hands 7 - Day 2
56mDev Containers. What are they and why do you need them?
16mMy DevContainer Setup: A Reproducible, Flexible Development Workstation
32mLocal development techniques with Kubernetes
47mOptimizing the Microsoft developer experience with Docker
50mInstant Self-contained Development Environments for Everyone