Deployment with capistrano
Download as PPTX, PDF0 likes787 views
This document discusses using Capistrano, an open source tool for automating software deployments. It describes some of the issues with manual deployment processes and why automation is needed. Capistrano allows developers to deploy applications by writing scripts that execute commands remotely via SSH. It handles tasks like updating code, databases, and symlinking shared files. Capistrano provides a consistent, secure way for developers to deploy applications while still giving system administrators control over server environments.
Deployment with capistrano
- 1. Revealing Hour Creations Sagar P Junnarkar sj@revealinghour.in @sagarjunnarkar
- 3. How do we deploy? FTP,SFTP,SCP? SSH+GIT? Debian packages? Don’t know? Other team does it for you.
- 4. What are the issues ●Lot of manual processes -backup db, update code, update db etc. ●Room for error. steps could be missed. ●Small organisation : loose server access and permissions ●Large organisation : too restrictive permissions. locked down server env
- 5. What do we need?
- 6. What do we need? ●Give limited power to developers ●Automate entire deployment process
- 7. System admins don’t want you to touching their stuff
- 8. System admins don’t want you to touching their stuff Standard server env: ●Convention ●Consistency ●Security ●Monitoring
- 9. working together to get the job done
- 10. working together to get the job done ●Developers are able to deploy rapidly ●Sys admins have tight control of environments ●All manual process are automated
- 11. Capistrano www.capistranorb.com ●Introduced around 2006 by Jamis Buck of 37 signals ●Written in ruby, initially for rails project ●It is a developer tool for deploying web applications. It is typically installed on your workstation and used to deploy your SCM to one or more servers.
- 12. Simplest explanation ●Lets you write scripts that say “ssh onto remote machine and do things.” ●Program your deployment actions
- 13. Setup and configuration gem install capistrano cap -T # List all commands capify . #capistrano v2 cap install #capistrano v3
- 14. Local Directory Structure ├── Capfile ├── config │ ├── deploy │ │ ├── production.rb │ │ └── staging.rb │ └── deploy.rb └── lib └── capistrano └── tasks ├── Capfile ├── config │ ├── deploy.rb
- 15. Server Directory Structure myapp/releases myapp/current -> releases/20141001001122 myapp/shared
- 16. Symlink for shared files Symlinks are made back to the shared folder, so they are not lost between deployments. e.g. myapp/current/uploads -> myapp/shared/uploads
- 17. How does it works ●No software installed on server, just locally ●Capistrano builds commands to be executed remotely ●executed on the server over ssh
- 18. Local Server Lookup current revision in source control ssh into server using ssh public key checkout specified revision from source control copy a new timestamped site directory Add symlinks to shared directories update current symlink to new site directory Simple Deployment Workflow
- 19. Hooks Before and after hooks at each stage of the deployment lifecycle Extend or customise default capistrano behavior Examples: deploy, deploy:setup,deploy:symlink, deploy:update_code, deploy:rollback
- 20. Some common recipes cap deploy # Deploys your project. cap deploy:check # Check required files and directories exist cap deploy:cleanup # Clean up old releases. cap deploy:migrate # Run the migrate rake task.
- 21. Deploy configuration In deploy.rb set :application, ‘site.com’’ set :scm, :git set :repository, “git@github.com/sagarjunnarkar/site.git” set :branch, “master” set :port, 22 set :user, 'ubuntu' set :deploy_to, “/home/#{user}/#{application}” #/home/ubuntu/site.com role :app, ‘www.example.com’ #server "54.169.95.188", :web
- 22. Made mistake Oops. We’re sorry but something went wrong
- 23. Rollback deployment cap deploy:rollback Set current symlink to previous release directory
- 24. Questions
- 25. Thank you