Deploying to tsoHost with DeployHQ
Deploying to your site hosted with tsoHost is very simple with DeployHQ.
Firstly, you'll need to set up your DeployHQ project, then connect to your tsoHost 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 tsoHost
Once you've configured your repository, you'll need to connect to your tsoHost server. To be able to do this, you'll first need to enable SSH/SFTP access, which you can do by following tsoHost's guide.
Once you've done that, 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:
Nest, enter shell.gridhost.co.uk, followed by the username and password that you've been presented with after enabling SFTP. The port can be left blank to use the default (22).
Next, enter a deployment path - this is the place that files will be uploaded to on the server. This will normally start with public_html on tsoHost, and you can add additional directories to the path, for example, if you wanted to just deploy to a Wordpress theme folder.
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.
Again, you might specify the path to your WordPress theme directory if you want to just deploy the theme folder but have your whole WordPress instance committed to your repository.
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 tsoHost 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 tsoHost 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
