The document discusses the importance of embracing automated deployment, specifically using Capistrano, to simplify and improve the deployment process in software engineering. It highlights deployment goals such as ease of use, reliability, and scalability, as well as presenting Capistrano as a popular tool for remote server automation. Additionally, the document outlines the requirements and terminology associated with Capistrano, along with future trends in deployment.

1. STILL STUCK WITH FTP OR GIT PULL TO
DEPLOY?
IT'S HIGH TIME TO EMBRACE AUTOMATED
DEPLOYMENT WITH CAPISTRANO
Created by /Sumit Chhetri @shhetri
, Kumaripati, LalitpurYIPL

2. OUTLINE
Who Am I?
Deployment?
Deployment Goals
Bene ts of Automated
Deployment
Some Infographics and Stats
Capistrano
Requirements
Terminology
Demo
Future of Deployment
Any Questions?
Thank You

3. WHO AM I?
Sumit Chhetri
Software Engineer @ YIPL

4. DEPLOYMENT
?

5. DEPLOYMENT
is all of the activities that make a
software system available for use
Software deployment
copy/clone code base to server
run composer commands
migrate your database
reload the web server
notify about the deployment
and so on...

6. DEPLOYMENT GOALS

7. One-click / command deployment
Source: devopsreactions.tumblr.com

8. Anytime & Anywhere

9. Anyone (with permission) can deploy

10. Nominal/No downtime (ZDD - zero downtime deployment)

11. Reliable Rollbacks
Pushed code to production, recalled there was a critical bug
Source: devopsreactions.tumblr.com

12. Reusable and should be reproducible (repeatable)

13. Scalable

14. BENEFITS OF AUTOMATED DEPLOYMENT

15. Deployments become much less error-prone
compared to this...
This simulates a manual deployment
Source: devopsreactions.tumblr.com

16. Anyone in the team with permission can deploy software

17. Engineers will spend most of their time developing software
and not have to face this kind of situation...
Problematic deployment is over
Source: devopsreactions.tumblr.com

18. Deploying to somewhere new is not a headache

19. You can release features more frequently as its easy,
automated and reproducible

20. GOOD, BUT HOW DO DEVELOPERS DEPLOY?
Source: Geshan.com.np

21. DEPLOYING WITH FTP NOW IS LIKE...
Source: devopsreactions.tumblr.com

22. DEPLOYMENT TOOLS, WHAT ARE THE POPULAR
ONES
Tool Written In Github Stars Github Watchers
Ruby 329
Python 316
Ruby 90
PHP 81
PHP 85
Capistrano 7476
Fabric 5833
Mina 2701
Rocketeer 1731
Deployer 1334
Source: , data from 04-Sep-2015Github.com

23. CAPISTRANO
A remote server automation and deployment tool written in
Ruby

24. Originally a tool for deploying code

25. Evolved into remote multi-server automation tool

26. Uses SSH

27. Does everything in parallel

28. Support these VCS out of the box
1.8 or higherGit
Mercurial
SVN

29. Easy to integrate with Java projects

30. We @ chose capistrano because it is popular and most
importantly ts for our use-case
YIPL

31. REQUIREMENTS

32. Ruby >= 1.9.3

33. recommended with public keys (password less)
SSH access to all servers,

34. TERMINOLOGY
Task
Recipe
Namespace
Role
Stages

35. TASK
A concrete set of commands to execute.

36. RECIPE
A collection of tasks.

37. NAMESPACE
Organizes tasks within recipes and
avoids naming collisions

38. ROLE
Servers can have different roles like
app
demo
web

39. STAGES
Refers to each environment being a stage like dev, staging,
testing, production.
Usually means different set of servers.
Can also include con guration per stage.
Or even different tasks.

40. DEMO
0:00 / 1:33

41. FUTURE OF DEPLOYMENT
with deploying from Hipchat using HubotChat ops
deployment but looks like a problem in Internet
challenged Nepal :)
Docker

42. ANY QUESTIONS???
You can drop me a message via
Email :
Facebook :
Twitter :
Visit to read
more on this. And for more interesting
stuffs.
sumit.chhetri@yipl.com.np
er.sumit.chhetri@gmail.com
https://www.facebook.com/SHhetri
https://twitter.com/shhetri
http://blog.yipl.com.np/automated-deployment
http://blog.yipl.com.np

43. THANK YOU
Geshan Manandhar
All of you