Header

Deploying to a Google Cloud Platform Compute Engine VPS with DeployHQ

Deploying your code or Wordpress site hosted with Google Cloud Compute Engine is very simple with DeployHQ.

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

Once you've configured your repository, you'll need to connect to your Compute Engine server.

As a prerequisite, make sure that your VPS firewall is not blocking DeployHQ's IPs based on your project's region. For more information on what IPs to allowlist, refer to the following article.

Once done, 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:

Strattic

Before adding your server details in DeployHQ, you can follow this guide to set up your Compute Engine server with the SSH key provided in DeployHQ's server configuration page. This will allow you to connect your DeployHQ instance with your Compute Engine VPS without a password.

SSH RSA key

Next, enter your Compute Engine hostname (the server's IP), your username and your port (22 by default) in DeployHQ's server configuration page. Details on how to view these credentials and other useful parameters can be found in your Compute Engine Dashboard, as described in the following article.

Once this is done, you can enter a deployment path (where you want files to be placed on the server). In this case, you'll most likely start with the name of our site, followed by the path to the theme directory.

Next, 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.

Pressable - deployment options

In this case, as you probably just want to deploy your Wordpress theme folder, you'll enter the path to the theme. If you only keep the theme in version control, you can leave it 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 Compute Engine 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 Compute Engine 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

Want to learn more about deployment or Wordpress? Check out our documentation or contact our support team for assistance.

Tree

Proudly powered by Katapult. Running on 100% renewable energy.