Containerizing legacy applications
summary
Legacy PHP forum (MyBB/phpBB style) is containerized using Docker Compose, Docker Swarm and eventually Kubernetes with Helm, moving config files into volumes and ConfigMaps; Consul and Vault hold secrets while Consul Template renders files at runtime. The demo builds multi‑replica web containers and a single DB, adds short‑lived DB credentials (leases ~2–3 minutes) and dynamic reloads; it mostly works but exposes real failures: JVM/entrypoint quirks, simultaneous restarts and an onstage restart crash.
AI-written summary · about
chapters (26)
- 0:00Start
- 2:19Steps
- 3:38Old(er) application candidate
- 5:20Older applications live on
- 8:49Container tutorial assumptions
- 9:49Why not just use Dockerfiles?
- 10:28Baking container images
- 10:49Additional environment configuration
- 12:05Docker Compose
- 13:26Container Orchestrators
- 13:55Docker Swarm
- 15:34Container quickstarts
- 16:48Templating
- 17:33Helm
- 17:56Kubernetes Volumes
- 19:07key points
- 19:59Persistent Volume for settings.php
- 20:28ConfigMap updates
- 21:06Consul Template
- 24:44Secrets management
- 24:58HashiCorp Vault
- 28:18Container environment detection
- 28:41Forking
- 29:24Storage inconsistencies
- 29:44Recap
- 29:56That's a wrap!
related talks
37mLessons learned from dockerizing complex Web Apps
49mDocker & PHP development and deployment
01h 09mDocker in Production
37mHigher order infrastructure: from Docker basics to cluster management
34mTest Environments Management with
37mShaping Applications for Docker, CoreOS, Kubernetes & Co.
50mComposing your Containerized Microservices
28mMulti-Container Applications with Docker Compose