{"id":2908,"date":"2018-11-14T04:42:49","date_gmt":"2018-11-14T10:42:49","guid":{"rendered":"https:\/\/www.supportpro.com\/blog\/?p=2908"},"modified":"2019-10-30T02:40:25","modified_gmt":"2019-10-30T08:40:25","slug":"capistrano","status":"publish","type":"post","link":"https:\/\/www.supportpro.com\/blog\/capistrano\/","title":{"rendered":"Capistrano"},"content":{"rendered":"

\"Capistrano<\/a><\/p>\n

Capistrano is a remote server automation open-source tool written in Ruby that gives a set of advanced tools to deploy web applications to the servers.<\/span><\/p>\n

To perform the deploy functions Capistrano does not require any big set of additional applications; it just requires an ssh connection with a new user who has the permission to copy the code from the source control repository to the server and Ruby Gems, the package manager for the Ruby programming language.<\/span><\/p>\n

Although Capistrano is written in Ruby, it can easily be used to deploy projects of any language.<\/span><\/p>\n

 <\/p>\n

Why Capistrano?<\/strong><\/h2>\n

The main advantage of Capistrano is that it\u2019s also possible to deploy to multiple machines at once and can be deployed by writing just one console command cap and if something goes wrong the application can be rollback to the last release by using another one cap.<\/span><\/p>\n

Capistrano decides on how to structure the scripts, where deployed files should be placed on the server, or how to perform common tasks.<\/span><\/p>\n

Capistrano instance can be easily extended using the RubyGems package manager and can run each deployment task concurrently across those servers i.e the parallel execution of the task,\u00a0 that too without any downtime.<\/span><\/p>\n

 <\/p>\n

Main Features of Capistrano<\/strong><\/h2>\n
    \n
  • SSH connection\u00a0<\/span><\/li>\n<\/ul>\n

    Capistrano does not require a big set of additional applications on the server. All it needs is an ssh connection, i.e. it depends on connecting to the server(s) with SSH using key-based (i.e. password-less) authentication.\u00a0<\/span><\/p>\n

      \n
    • Multiple stages<\/span><\/li>\n<\/ul>\n

      Multiple stages are all about parallel execution of the task in a fleet of servers, as the Capistrano has the ability to run each task concurrently by giving specified roles to the participating servers.\u00a0<\/span><\/p>\n

        \n
      • More roles for servers\u00a0<\/span><\/li>\n<\/ul>\n

        Capistrano assigns each server with one or more roles to control the tasks that are executed, as the application may need different types of servers for database, application, web etc.<\/span><\/p>\n

          \n
        • Extensible\u00a0<\/span><\/li>\n<\/ul>\n

          As Capistrano is a Ruby program, the RubyGems package manager helps to extend the Capistrano instance. The plugins in the Capistrano for different frameworks provide a set of tasks. This plugin is intended to be used before any deployment task.<\/span><\/p>\n

          Also, some of the Ruby projects comes with Capistrano tasks built-in.<\/span><\/p>\n

          The official Capistrano Plugins are listed below.<\/span><\/p>\n

          ======<\/span><\/p>\n

          >> Bundler<\/span><\/p>\n

          >> Composer<\/span><\/p>\n

          >> Drupal<\/span><\/p>\n

          >> rbenv<\/span><\/p>\n

          >> RVM<\/span><\/p>\n

          >> Ruby on Rails<\/span><\/p>\n

          >> Symfony<\/span><\/p>\n

          >> Laravel<\/span><\/p>\n

          >> npm<\/span><\/p>\n

          >> Phusion Passenger<\/span><\/p>\n

          >> chruby<\/span><\/p>\n

          ======<\/span><\/p>\n

           <\/p>\n

          How Capistrano?<\/strong><\/h2>\n

          Capistrano can be installed as a standalone Gem or bundled into the application and as Capistrano is a Ruby package, we will need to install Ruby on our system and can be set by running ‘cap install’ in the project\u2019s root directory.\u00a0<\/span><\/p>\n

          When the cap is run, Capistrano connects to the servers via SSH and executes the steps necessary to deploy your project.\u00a0<\/span><\/p>\n

          Below is the structure of the files and directories for a Capistrano-enabled project with two\u00a0stages, namely staging\u00a0and\u00a0production.<\/span><\/p>\n

          The stages will have a set of servers that can have many roles.\u00a0<\/span><\/p>\n

          ===<\/span><\/p>\n

          \u251c\u2500\u2500 Capfile\r\n\u251c\u2500\u2500 config\r\n\u2502   \u251c\u2500\u2500 deploy\r\n\u2502   \u2502   \u251c\u2500\u2500 production.rb\r\n\u2502   \u2502   \u2514\u2500\u2500 staging.rb\r\n\u2502   \u2514\u2500\u2500 deploy.rb\r\n\u2514\u2500\u2500 lib\r\n    \u2514\u2500\u2500 capistrano\r\n            \u2514\u2500\u2500 tasks<\/code><\/pre>\n
          ===<\/span><\/p>\n
           <\/p>\n
          The stage-specific configuration files are for introducing the Capistrano about the task on the servers.<\/span><\/p>\n
          The files that Capistrano creates are simply templates and we should make sure to edit the deploy.rb and stage files so that they contain values appropriate for the projects and the target servers.<\/span><\/p>\n
          There are two modes for the execution of commands in Capistrano, interactive<\/strong> and non-interactive<\/strong> modes.<\/span><\/p>\n
          The difference is that the interactive mode is used to get immediate feedback when we don\u2019t know which command needed to be executed and the non-interactive mode is used when we know the command to be used and just want to see the result.<\/span><\/p>\n
          The latest released Capistrano v3 provides a default deploy flow and a rollback flow. The tasks involved are listed below.<\/span><\/p>\n
          Deploy flow<\/strong><\/span><\/h3>\n
          deploy: starting –\u00a0 starts deployment<\/span><\/p>\n
          deploy: started\u00a0 –\u00a0 start hook for the custom tasks<\/span><\/p>\n
          deploy: updating\u00a0 –\u00a0 updates the servers to a new release<\/span><\/p>\n
          deploy: updated\u00a0\u00a0 –\u00a0 update hook for the custom tasks<\/span><\/p>\n
          deploy: publishing –\u00a0 publishes the new release<\/span><\/p>\n
          deploy: published\u00a0 –\u00a0 publish hook for the custom tasks<\/span><\/p>\n
          deploy: finishing\u00a0 –\u00a0 finish the deployment<\/span><\/p>\n
          deploy: finished –\u00a0 finish hook for the custom tasks<\/span><\/p>\n
          The hooks are used for adding their own tasks.<\/span><\/p>\n
          Rollback flow<\/strong><\/span><\/h3>\n
          deploy: starting <\/span><\/p>\n
          Deploy: started <\/span><\/p>\n
          Deploy: reverting- reverting the server to the previous version. <\/span><\/p>\n
          Deploy: reverted- reverted hook <\/span><\/p>\n
          Deploy: publishing <\/span><\/p>\n
          Deploy: published <\/span><\/p>\n
          Deploy: finishing_rollback – finish the rollback\u00a0<\/span><\/p>\n
          Deploy: finished\u00a0 \u00a0\u00a0<\/span><\/p>\n
           <\/p>\n
          Benefits of Capistrano\u00a0\u00a0<\/strong><\/h2>\n
          -> Can deploy the application by one console command.<\/span><\/p>\n
          \u00a0 \u00a0 \u00a0cap <stage_name> deploy<\/span><\/p>\n
          -> Can rollback the application by another command.<\/span><\/p>\n
          \u00a0 \u00a0 \u00a0cap <stage_name> rollback<\/span><\/p>\n
          -> Can simply SSH to a lot of servers and perform a bunch of actions\u00a0<\/span><\/p>\n
           <\/p>\n
          Conclusion<\/strong><\/h2>\n
            \n
          • Capistrano is much easy such that it makes the development so simple and will decrease the workflow.<\/span><\/li>\n
          • The power of Capistrano becomes more specified when we have many servers with distinct roles.<\/span><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
            Capistrano is a remote server automation open-source tool written in Ruby that gives a set of advanced tools to deploy web applications to the servers. To perform the deploy functions…<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[67,5,3],"tags":[],"class_list":["post-2908","post","type-post","status-publish","format-standard","hentry","category-devops","category-general-topics","category-technical-articles"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/2908","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/comments?post=2908"}],"version-history":[{"count":23,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/2908\/revisions"}],"predecessor-version":[{"id":4092,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/2908\/revisions\/4092"}],"wp:attachment":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/media?parent=2908"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/categories?post=2908"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/tags?post=2908"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}