Deployment Targets for your projects
Save time and streamline your workflows with DeployHQ's deployment targets. Effortlessly deploy your code to multiple servers at once—whether it's a single FTP server, AWS Elastic Beanstalk, Heroku, or a cluster on DigitalOcean—managing all your destinations in one place.
What are deployment targets?
In DeployHQ, deployment targets are destinations for your code. For you, this could be a single FTP server, or a group of servers on DigitalOcean that all run the same application.
You can consider a target representing a specific environment that your code lives on, such as a production or staging server. Within a DeployHQ project, you can only connect to a single repository, however you can add as many targets as you like.
You can also set up multiple targets to deploy to the same server, which is useful if you want to deploy to a staging and production environment on the same server, or if you want to deploy to multiple directories on the same server.
-
FTP or FTPS
![]()
-
SFTP
![]()
-
AWS S3 & Elastic Beanstalk
![]()
-
DigitalOcean
![]()
-
Shopify
![]()
-
Cloudflare R2 and CDN
![]()
-
Heroku
![]()
Why are deployment targets useful?
In many cases, a typical DeployHQ project will consist of three targets, one for development, one for staging and another for production.
The development target will be set up to deploy from a dev branch, then the staging and production targets from master. You can individually specify which targets will be deployed to manually or automatically to as well - you might not want your code automatically deployed to production when you’ve pushed a change to your master branch!
