Devops for PHP Developers
summary
Claims that continuous delivery cuts cycle time dramatically and cites a 2014 study of ~9,200 organisations showing high performers deploy 30x more often and are 8000x faster to deploy, with 50% fewer failures and 12x faster restores. Concrete practices include making environments early with Vagrant/Docker and Packer, managing servers with Chef, Puppet, Ansible, building CI pipelines, automated acceptance tests and scripted deployments (Capistrano/Rocketeer/Deployer) so releases become routine.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:14About
- 2:47Common DEVOPS definition - CAMS
- 6:28Developer Mindset
- 8:22Breaking Down the Silos
- 9:12DEVOPS is Cultural shift
- 9:34The state of DEVOPS 2014
- 12:04Takeaway
- 12:27Increasing collaboration between dev and ops
- 13:44Change your definition of done
- 17:53Practices
- 19:06Cycle Time
- 19:46Key Finding - DEVOPS 2013 Report
- 20:11Some problems dev and ops teams face
- 22:32Key Goals of Continuous Delivery
- 23:40Benefits of deploying more frequently
- 24:37Deployment becomes a non event
- 25:14Continuous Integration
- 27:37Automated acceptance testing
- 30:46Key objectives of Deployment pipeline
- 32:03Automated Deployments
- 35:47Measurement and monitoring
- 36:58Sharing - Pain
- 40:38Summary
- 41:47Patrick Debois
related talks
34mDevOps: Next
26mHow Continuous Delivery and Lean Management Make your DevOps Amazeballs
51mBetter software, faster: principles of Continuous Delivery and DevOps
45mDevOps: The Key to IT Performance
32mDevOps for Vue developers
36mWhat do we know about continuous delivery – and what would we like to know
33mSecurity, Don't Fear the DevOps
41mContinuous Delivery of a webapp by example