Deploying WordPress to LaunchWP via DeployHQ: Fast & Reliable
Deploying to your WordPress site managed with LaunchWP is very simple with DeployHQ. LaunchWP is a WordPress server management dashboard that lets you manage WordPress on any VPS or cloud provider. It provides SFTP access for deployments.
Firstly, you'll need to set up your DeployHQ project, then connect to your LaunchWP-managed server.
Setting up your project
Head to the Projects screen in DeployHQ, then click the New Project button to get started.
You'll be prompted to enter a name for your project, then select where your repository is hosted.
![]()
Next, click Create project and you'll be taken to a screen where you can log in with your repository hosting account to authorise access and then choose your repository.
- Adding a Bitbucket repository
- Adding a Codebase repository
- Adding a GitHub repository
- Adding a GitLab repository
- Adding a repository manually
Setting up LaunchWP
Once you've configured your repository, you'll need to connect to your LaunchWP-managed server.
Your SFTP connection details can be found in the LaunchWP dashboard. For step-by-step instructions, see LaunchWP's SFTP connection guide.
Head to Servers & Groups in DeployHQ, and click the New Server button at the top of the screen. If you've just added your repository, you will have been taken to this page automatically.
Start by entering a name, and choosing SSH/SFTP as the protocol:
![]()
Enter your SFTP hostname, username, and password from the LaunchWP dashboard. The port is typically 22.

For the deployment path, enter the path to your WordPress files. Common paths:
- Full site:
/public_html/ - Theme only:
/public_html/wp-content/themes/your-theme-name/ - Plugin:
/public_html/wp-content/plugins/your-plugin-name/
The exact path depends on how LaunchWP has configured your server — check the SFTP details in your dashboard.
Within Deployment options, you can choose to automatically deploy your server and, if you're only deploying files from a certain directory in your repository, enter a Deployment subdirectory.
![]()
For example, if your repository only contains your WordPress theme, you can leave the deployment subdirectory blank and set the deployment path to the theme directory.
Click Create Server to finish, then you can proceed to start your first deployment.
Run your first deployment
By default, DeployHQ will upload the whole repository to your server on the first deployment, because there is no previously deployed commit to compare to.
If your files are already on your LaunchWP server and up to date with the latest commit, you can follow this guide to skip that first deployment:
Otherwise, just follow this guide to start your first deployment, then after the first deployment, only files that have changed will be uploaded in future.
That's it! You've now set up and run your first deployment to your LaunchWP-managed server and your future changes will be uploaded for you automatically, or at the simple click of a button.
Further reading
DeployHQ has a number of very useful features to help with your WordPress deployments in general that you might wish to find out more about:
- Compiling assets and javascript with the Build pipeline
- Running commands on your server with SSH commands
- Stop certain files from being uploaded in deployments using Excluded files
- Keep important files safely away from your repository using Config files
- Keep your team in the loop and run other useful tasks during a deployment with our Integrations