# Buddy Continuous Integration / Deployment

**URL:** https://discourse.roots.io/t/buddy-continuous-integration-deployment/19100
**Category:** general
**Created:** 2020-09-14T03:49:44Z
**Posts:** 3

## Post 1 by @jasperfrumau — 2020-09-14T03:49:45Z

Has anyone here any experience using [Buddy](https://buddy.works/) for CI/CD with Trellis? Or using WordPress with Buddy? A client of mine uses it and its pipelines and actions do look really neat, but I have not found any blog posts or articles on using Trellis, Bedrock, Sage or Bedrock and Sage using Buddy.

I only found a [general tutorial](https://buddy.works/guides/how-introduce-continuous-deployment-to-wordpress) on settings WordPress up with Git and Buddy. So I am curious to see if anyone here uses Buddy and what their experience has been.

---

## Post 2 by @Genyus — 2020-09-24T14:34:22Z

I’ve never used Buddy, but it seems to work much the same way as any other CI/CD platform, just with a user-friendly UI on top.

Deploying a site built on Bedrock works pretty much the same as any other Composer-based application, which effectively requires two steps:

1. Getting your files onto the server
2. Running Composer

The Buddy documentation does provide an example of how to deploy a Composer application, which would work just as well for your Bedrock site:

> **[Automate PHP Dependencies Management with Composer PHP Turbocharged with Buddy](https://buddy.works/guides/php-composer)**
>
> Learn how to improve PHP libraries management with Composer.

You’d just need to account for the modified web root and environment variables within your hosting environment.

---

## Post 3 by @system — 2020-10-26T03:49:47Z

This topic was automatically closed after 42 days. New replies are no longer allowed.