Deploy to Vultr
Buddy turns deployments into a breeze, allowing you to automatically update your servers on every push to branch. You can also deploy manually on click, or recurrently on time intervals.
Example pipeline with deployment to Vultr
If you are new to Buddy, check out our quickstart guides that will tell you how to build and test your application before the deployment.
đź“š Learn more about Vultr action features, integrations and alternatives.
Configure pipeline in Buddy
- Create a new project in Buddy and select your Git provider.
Creating a new project
- Add a new pipeline and configure the details: name, trigger mode, and a branch from which you want to deploy.
Adding a new pipeline
Configure Vultr deployment
- Look up and click Vultr on the action list:
Transfer actions in Buddy
- The action has four 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 server to which you want to deploy
- 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
If you are using build actions in your pipeline, make sure to select the Filesystem as the source to deploy artifacts and processed files.
Vultr action configuration
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.
- When ready, click Add this action to finish configuration.
Congratulations! You have just automated your Vultr deployment. 🥳
Last modified on December 12, 2023