Overview

Buddy.works is a comprehensive Continuous Integration / Continuous Deployment (CI/CD) platform which allows you to automate workflows to get your code into production sooner and in a more reliable fashion.

While Plesk has basic Git integration, Buddy.works allows for a number of intermediate steps (such as image compression and minification) to be actioned at the same time. This guide will show you how to configure a pipeline which is compatible with Plesk.

Information

This guide covers the pipeline configuration only. If you’re new to Buddy.works, we suggest reading their documentation to get an understanding of their full system.

Instructions

  1. Within Buddy.works, select your existing project or create a new one.
  2. Add a new Pipeline:
    Buddy.works code deployment with Plesk
  3. Give your new pipeline a name and select “On push” if you want automated deployments:
    Buddy.works code deployment with Plesk
  4. Search for “FTP” within the actions and select FTPS (not SFTP):
    Buddy.works code deployment with Plesk
  5. Add in your FTP details for your existing Plesk subscription, then click Browse:
    Buddy.works code deployment with Plesk
  6. Select the path of where you wish the files to be deployed to. For example, for a WordPress theme you’ll want to select httpdocs/wp-content/themes/<theme-name>:
    Buddy.works code deployment with Plesk
  7. Save the configuration. You can now test with a manual run:
    Buddy.works code deployment with Plesk
    Once completed, this should provide a confirmation that the pipeline completed without error:
    Buddy.works code deployment with Plesk
  8. To ensure the pipeline is automatically deployed, select Webhook URL from the right hand side:
    Buddy.works code deployment with Plesk
  9. Copy the webhook URL into your chosen Git repository as a hook:
    Buddy.works code deployment with Plesk
  10. Integration between Buddy.works and Plesk has now been configured.

Was this article helpful?

Related Articles