Header

Deploying to Pressidium

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

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

In order to connect to your Pressidium server, you'll need to enter your SFTP connection details.

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:

Pressidium - SSH server

Next, enter your Pressidium website's SFTP server name as the hostname (As indicated in your Pressium overview tab), followed by the port, username and password as indicated in your portal account.

You can find a full guide for connecting to your Pressidium site via SFTP in Pressidium's documentation.

Pressidium - SSH connection details

This will normally start with your site name when deploying to Pressidium, and you can then specify additional subdirectories if you're only deploying to a folder within it, such as a WordPress theme or plugin directory.

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

Pressidium - deployment options

You might, for example, be deploying a WordPress site, but only want to upload your theme folder.

When you're finished, just click Create Server and you can proceed to run 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 Pressidium 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 Pressidium 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