Docker from Dev to Production: Streamlining the CI/CD process for BALR
summary
Built a Symfony-based ecommerce on a fork of Silius and runs the same Dockerfile in development, testing, acceptance and production, using docker-compose locally and a single-container Docker on AWS Elastic Beanstalk. CI runs PHPUnit, phpspec and Behat in Travis CI, then Travis CI -> EB deploy builds images, runs migrations and uploads to Elastic Beanstalk; New Relic monitors containers and EC2. Pain points: NFS file-sync slows Grunt-based frontend workflow and EB health checks against robots.txt cause brief broken states during swaps. Outcome: automated pipeline works in production and developers get a PR merged on day one.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:49Business requirements
- 5:19Technical requirements
- 7:38Proof of concept
- 13:16Test automation
- 19:29Docker
- 24:43Challenges
- 27:49Success & Achievements
related talks
37mLessons learned from dockerizing complex Web Apps
37mTaking Solidus From Development to Production
42mKickass Laravel Development with Docker
40mGoes Beyond CI to Production Scale PaaS with Docker
52mDocker: Multi-Stage and Multi-Environment -php2019
01h 04mPreparing your Dockerised Application for Production
49mDocker & PHP development and deployment
31mDockerized app in production? YES WE CAN!!