Continuous Delivery for Laravel Applications
Hi, I'm Steven Maguire
- I've been building software since 2004.
- Head of Engineering at Packback.
- Contribute to open source.
- Authoring a Laravel course for Pluralsight.com.
- Tweet from @stevenmaguire
Quick demo!
Let's review
- Local code changes
- Commit to git on master branch
- ....
- Changes available in production
Quick poll
What we didn't see
- Webhook initiated build
- Virtual machine created
- Latest from master pulled from git
- Composer install
- Test suite execute
- Build "passed"
- Webhook initiated deployment on server
- Latest from master pulled from git
- Composer install
- Database migrations
People suck at consistency
People are great at improvement
Continuous
Integration
Deployment
Delivery
Improvement
practice that requires developers to
integrate code into a shared repository
several times a day. Each check-in is then
verified by an
automated build, allowing teams to
detect problems early.
Party over here
It's hard!
Makes our jobs easier and more productive.
There's an app
a tool for that.
Which one is right for you?
Inventory our needs
Local code
Production code
Version control
Code quality
Code deployment
Monitoring
Server configuration
Quick poll
Today is about Codeship and Laravel
I don't work for Codeship or Laravel
(I appreciation them; like a lot)
Laravel = rapid php development
Codeship = rapid php* deployment
*Codeship supports a lot of other languages too!
Needs/solution analysis
Local code
Production code
Version control
Code quality
Code deployment
Monitoring
Server configuration
Demo!
Questions?
Thank you!
@stevenmaguire
on twitter
stevenmaguire@gmail.com
on electronic mail
stevenmaguire
on github
Continuous Delivery for Laravel Applications