Header

Deploying to bluehost

Deploying to your site hosted with bluehost is very simple with DeployHQ.

Firstly, you'll need to set up your DeployHQ project, then connect to your bluehost 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.

New Project

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.

Setting up bluehost

In order to connect to your bluehost server, you'll need to enable SSH and obtain your SFTP connection details. You can follow bluehost's guide to do so.

Once you've set up SFTP on bluehost, head to Servers & Groups, 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:

bluehost - SSH server

Next, enter the hostname and port, followed by the username and password for the SFTP user:

bluehost - SSH connection details

Then a deployment path to upload your files to. If you're just uploading a WordPress theme, you'd enter the path to the theme directory.

You'll then be able to configure some useful Deployment options, including the ability to automatically deploy to the server on push to your repository, and to only deploy files from a specific directory in your repository:

bluehost - deployment options

Again, if you're just deploying a WordPress theme but have your whole WordPress instance committed to Git, you would just enter wp-content/themes/mytheme as the deployment subdirectory. Otherwise, if you want to just deploy your whole repo, or if you just have the theme committed, leave that setting blank.

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 bluehost though 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 bluehost 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 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