We support many types of deployment in DeployBot—you may upload your updated files through FTP/SFTP, push them to a cloud hosting like Elastic Beanstalk or Heroku, or even connect to your server through SSH using our Shell deployments, allowing you to execute arbitrary commands necessary for your deployment, without us uploading anything. It's the Shell deployments we're going to be talking about today.
Choosing the right build tool is as important as choosing a programming language, a text editor or IDE, the CI/CD tool, and the rest of the software involved. But what exactly is a build tool? And how do you decide on one?
Using build tools can significantly improve your development workflow. In DeployBot, you can execute scripts or commands in pre-defined Docker containers. Additionally, you can create your own Docker images, upload them to Docker Hub, and ask DeployBot to retrieve your own image from there.
Are you working on a larger project, and do you have to deploy your code to several servers at the same time? That can be a complex task and even error-prone if you do this manually. Let DeployBot help you—our favorite bot can deploy to several servers simultaneously, from just two servers to 20 or over one hundred.
Every developer has to deal with legacy code—sooner or later. This means she or he should find a way to handle this code, in the best possible way. It doesn't necessarily mean migrating to a CI/CD workflow. Continually delivering or deploying code might not be right for you, your software project, or even your team. But even then, you should consider automation, at least for tests and the build process.