My short presentation about automated deployment & capistrano performed in VilniusPHP meetup on 2013-09-05

1. Capistrano
Still Uploading Files to FTP?
Vidmantas Kabošis @ VilniusPHP, 2013-09-05

2. Manual deployment
● Easiness of deployment
● No configuration
● Simple & everywhere accessible tools

3. Manual deployment
Yeah, but:
● Inconsistent state
● Messy rollbacks
● Messy dependency management
● Interrupted flow
● Handmade!

4. Automated deployment
● Consistent state
● Rollbacks
● Dependency handling
● Automated!!!11!1one

5. Automated deployment
● You must still handle exceptions by hand
● One more tool into a project
● “Automated” part is only for usual use
cases

6. Automated deployment
● But anyway, it’s sexy and a must for even
smallest projects
● Red/blue pill

7. Capistrano
● Platform for automation
● Ruby
● De facto standard for deploying Ruby apps
● Many capistrano-like projects for PHP too
● Why bother with copycats, if you can use
original tool?

8. Capify
● gem install capistrano
● capify .

9. Setup
current -> releases/…
releases/
20130901101023/
20130901090144/
…
shared/
tmp
pids
conf

10. Flow
deploy
deploy:update
deploy:update_code
>> transaction kicks in
deploy:finalize_update
deploy:create_symlink
deploy:restart
deploy:cleanup

11. Caveats
● SSH
● Upcoming v3

12. Happy automation!
● Questions?

13. end
@vidmantas / vidmantas@kabosis.lt