Lessons learned from dockerizing complex Web Apps
summary
Started with mixed PHP/Perl app and ends up running PHP, MySQL, Solr, Redis, Cassandra, SQS, S3 and short‑lived background workers inside Docker images built by Jenkins and pushed to AWS Elastic Container Service; deployments pull immutable images, remove servers from the load balancer, run the new container and reattach. Local machines mount code from host and use Vagrant for Windows devs; large datasets (around 100 GB DB) stay on staging. Key fixes: use compact Dockerfiles, reuse official images and avoid importing huge data on every build.
AI-written summary · about
chapters (10)
- 0:00Start
- 4:07Why Do We Use Vagrant Instead of Docker Compose
- 8:01Background Processing
- 8:38Docker Is Not Only for Linux
- 15:22Connect to Docker Using Socket
- 23:32Add Custom Configuration for a Php
- 24:28Vagrant File
- 25:43Link Multiple Containers
- 27:12Issues with Docker
- 28:12Link between Containers
related talks
24mFrom Zero to a Full Docker Based IT Teams
46mDocker from Dev to Production: Streamlining the CI/CD process for BALR
30mContainerizing legacy applications
35mPractical PHP Deployment with Jenkins
49mIn Silicon Valley, Engineers Deploy-and-Tell: Stories About Dockerizing an Application
31mDockerized app in production? YES WE CAN!!
01h 18mEmbracing Docker simplicity - while harnessing platform power
43mServer Infrastructure for Rails in 2016