Capistrano

Automated deployments with Capistrano (Internal Talk at Leapfrog Technology)

Transcript

1. Deployment So#ware deployment is all of the ac5vi5es that make a so#ware system available for use: • Copy/clone code • Run composer, npm, gulp • Run migra6ons • Reload the web server • No6fy about the deployment
2. Deployment Goals
3. 1. One-click/command Deployment
4. 2. Any'me/anywhere (Anyone with permission)
5. 3. Zero Down+me Deployment
6. 4. Reliable Rollbacks
7. 5. Repeatable
8. 6. Scalable
9. Why automated deployments?
10. 1. Less error-prone Just run this command they said. It’s straigh5orward they said. It can’t go wrong they said.
11. 2. More (me for developing so3ware and less (me doing stuff like this...
12. 3. Release more frequently
13. A remote server automa,on and deployment tool wri4en in Ruby. h"p:/ /capistranorb.com/
14. • Uses SSH • Does everything in parallel • Supports Git, SVN, Mercurial • Easy to integrate with PHP projects • Mostly used with rails projects
15. Requirements • Ruby >= 1.9.3 • SSH access to all servers with public keys (recommended)
16. Terminologies • Task • Recipe • Namespace • Role • Stages
17. Task A concrete set of commands to execute.
18. Recipe A collec'on of tasks.
19. Namespace Organizes tasks within recipes and avoids naming collisions.
20. Role Servers can have different roles like: app, demo, web
21. Stages Refers to different set of environments (servers): dev, uat, qa, staging, produc9on Can also include configura0on per stage or even different tasks.
22. Other Alterna+ves • Fabric - Python • Mina - Ruby • Rocketeer - PHP • Shipit - Javascript • Deployer - PHP • CI Services like Travis CI, Circle CI, Jenkins
23. Demo
24. Thank you Let's hope your deployments won't be like this from now on.