Install Self-Hosted
Get Started on Cloud
BasicsPipelinesTargetsActions & ServicesIntegrationsSelf-HostedYAMLBuddy GitTroubleshootingAPI

Deploy to Vultr

How to deploy to Vultr?

To begin the deployment process to Vultr using Buddy CI/CD, you need to set up a pipeline and specify the server to deploy to. You can configure the pipeline to perform manual, recurrent or automated server updates. This guide will show you how to configure a deployment pipeline to optimize your workflow.

Image loading...Example pipeline with deployment to Vultr

Tip
If you are new to Buddy, check out our workflow guides that will tell you how to build and test your application before the deployment.
Hint

📚 Learn more about Vultr action features, integrations and alternatives.

Configure pipeline in Buddy

  1. Create a new project in Buddy and select your Git provider.

Image loading...Creating new project

  1. Add a new pipeline and configure the details: name, trigger mode, and a branch from which you want to deploy.

Image loading...Adding new pipeline

Configure Vultr deployment

  1. Look up and click Vultr on the action list:

Image loading...Transfer actions in Buddy

  1. The action has five configuration tabs:
  • Transfer – here you define the source path, deployment provide your repository path, select the source, and define files to ignore
  • Target – here you select the Vultr integration and provide the details of the Vultr deploy server
  • Variables – here you can add and modify environment variables required by your workflow
  • Conditions – here you configure the trigger conditions for which the action will run
  • Options – here you define the action's name and behavior on failure and timeout

Image loading...Transfer tab in Vultr action configuration window

Warning
If you are using build actions in your pipeline, make sure to select the Pipeline Filesystem as the source to deploy artifacts and processed files.

Image loading...Target tab in Vultr action configuration window

Hint
Buddy's deployment is based on changesets. This means only changed files are deployed, which makes it lightning fast ⚡️. The first deployment is always performed from scratch, unless you set a revision on the server in the Options tab.
  1. When ready, click Add this action to finish configuration.

Congratulations! You have just automated your deployment. Thanks to Buddy and Vultr integration, deploying applications will now be easier than ever. To increase the overall performance of your CI/CD process even more, you can use the deployment pipeline to perform automated tests of your application, monitor your website and notify you in case something goes wrong.

Hint
Read how to configure Vultr with YAML.

Last modified on Sep 24, 2024

Previous pageShopifyNext pageIntroduction to variables