Capistrano vs DeployBot: What are the differences?
Developers describe Capistrano as "A remote server automation and deployment tool written in Ruby". Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows. On the other hand, DeployBot is detailed as "Instantly deploy from Github, Bitbucket, or Gitlab without complex scripts, commands or configs". DeployBot makes it simple to deploy your work anywhere. You can compile or process your code in a Docker container on our infrastructure, and we'll copy it to your servers once everything has been successfully built.
Capistrano and DeployBot are primarily classified as "Server Configuration and Automation" and "Continuous Deployment" tools respectively.
Some of the features offered by Capistrano are:
- Reliably deploy web application to any number of machines simultaneously, in sequence or as a rolling set
- Automate audits of any number of machines (checking login logs, enumerating uptimes, and/or applying security patches)
- Script arbitrary workflows over SSH
On the other hand, DeployBot provides the following key features:
- Manually deploy with a click in the app, automatically deploy on each push, or use deploy tags in a commit [deploy:production].
- DeployBot gathers new and changed files from your repositories since the last deployment. You can even preview the changes first.
- Files are uploaded, SSH commands are executed and deployment hooks are triggered. Everything is logged for you.
"Automated deployment with several custom recipes" is the primary reason why developers consider Capistrano over the competitors, whereas "Easy setup" was stated as the key factor in picking DeployBot.
Capistrano is an open source tool with 11.1K GitHub stars and 1.71K GitHub forks. Here's a link to Capistrano's open source repository on GitHub.
According to the StackShare community, Capistrano has a broader approval, being mentioned in 293 company stacks & 81 developers stacks; compared to DeployBot, which is listed in 37 company stacks and 6 developer stacks.
What is Capistrano?
What is DeployBot?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Capistrano?
What are the cons of using DeployBot?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Shipit, our deployment tool, is at the heart of Continuous Delivery at Shopify. Shipit is an orchestrator that runs and tracks progress of any deploy script that you provide for a project. It supports deploying to Rubygems, Pip, Heroku and Capistrano out of the box. For us, it's mostly kubernetes-deploy or Capistrano for legacy projects.
We use a slightly tweaked GitHub flow, with feature development going in branches and the master branch being the source of truth for the state of things in production. When your PR is ready, you add it to the Merge Queue in ShipIt. The idea behind the Merge Queue is to control the rate of code that is being merged to master branch. In the busy hours, we have many developers who want to merge the PRs, but at the same time we don't want to introduce too many changes to the system at the same time. Merge Queue limits deploys to 5-10 commits at a time, which makes it easier to identify issues and roll back in case we notice any unexpected behaviour after the deploy.
We use a browser extension to make Merge Queue play nicely with the Merge button on GitHub:
Both Shipit and kubernetes-deploy are open source, and we've heard quite a few success stories from companies who have adopted our flow.
#BuildTestDeploy #ContainerTools #ApplicationHosting #PlatformAsAService
Quick deployment on demand for manual deployment, automatic deployment for dev and staging servers on code commit.
For deploying to a VPS like DigitalOcean. This pairs nicely with https://github.com/cyrusstoller/gardenbed.
Deployment automation all of the websites and apps are deployed to linux via capistrano.