Run apps directly from your Git repository with Buddy!

UPDATE: December 2018

After one year of testing, we have decided to shut down the beta of Sandboxes. Using the feedback that we gathered, we are currently working on a new and improved version of the test environment feature. Make sure to follow us on Twitter for news and updates on the release date.

We’re happy to announce that Sandboxes are coming to Buddy! This means you will be able streamline your process by launching your apps directly from your Git repository.

Yes, this is the BIG feature that we’ve been teasing you with in the past couple of weeks. The main part of development has been finished and we are currently testing it inside-out. By mid-April we should be ready with beta for you to check out. Stay tuned for more information, and in the meantime check out how it works in our super-exclusive video below:

Version Control: Feature overview

In addition to GitHub, Bitbucket and GitLab support, Buddy offers a fully-featured Git hosting for private repositories, both in cloud and self-hosted version. This option is useful for people who like to keep everything in one place, prefer a clean GUI over cluttered interface, or cannot use any of the aforementioned Git providers for whatever reason.

Buddy v1.4.44 Released

New features


  • Changed condition for skipping recurrent pipelines. From now on, if there’s more than one execution queued in the pipeline, only the first newest will be executed.

Bug fixes

  • [REST API] Fixed method fetching project list. The bug has officially claimed the 1st place for the most ‘WTF?’ bug in the history of Buddy: if a project was starting with the ‘API’ word, it was not returned (?). Big shout out to Marco for pointing that out!

Buddy v1.4.43 Released

New features


  • You can now recreate GitHub, Bitbucket and GitLab integrations in /my-id settings if you have problems resynchronizing your repositories
  • Action and execution views have a new, more compact design

Bug fixes

  • Fixed default commands for the Jekyll action
  • Fixed bug with automatic pipelines not triggering if there was another pipeline with branch assignment set to ‘None’

Buddy v1.4.41 Released

New features

  • The BIG feature that we announced last week has just left the testing phase and was merged to the DEV branch. If all goes well, it should be live in about one month


  • It is now possible to resynchronize the repository with your provider. Buddy uses webhooks to fetch information about changes in GitHub, Bitbucket and GitLab repositories. Sometimes, for reasons independent from us, the web hooks did not reach our service and the changes were not reflected in Buddy. Clicking Resynchronize Repo in the Code tab will fetch the latest version of the repository and trigger dependent pipelines
  • When adding a new deployment action to a pipeline which has already been executed you will be asked if you want to deploy the files from scratch. This way there won’t be any problems with badly calculated changesets on the first execution

Bug fixes

  • Some time ago we made some improvements to action validators and accidentally entered a bad regex which prevented adding actions containing an underscore. Fixed
  • There was a bug in one of the external libraries used to send the status of execution to GitHub which caused recurrent pipelines to crash. We have reported and fixed that on the very same day [applause]
  • If there are more than 100 files in the changeset the diffs for them are not displayed by default and you need to expand them manually. Sometimes there was a problem with that. Fixed
  • [Buddy GO] Fixed bug with the wrong number of concurrent executions available for Enterprise licenses. If you’re a Premium user and still have this problem, please refresh your license at $URL_TO_STANDALONE/payments/license

Integrations with Amazon Web Services

Of all supported Buddy integrations one of the most popular are Amazon Web Services. There are currently 5 AWS services supported by dedicated actions with more to come in the future (depending on the community feedback):

Deploy to Amazon S3

Together with Elastic Beanstalk and EC2, one the most successful Amazon service. A lot of web developers use S3 to store static files (sometimes entire static pages). With Buddy, you can define a pipeline that will automatically upload repository files to the selected S3 Bucket on push to branch. You can add additional actions that will process your files prior to the deployment, eg. Grunt or Gulp.

Example pipeline:

The project is PHP. Static assets, such as videos, PDFs, Javascript, CSS and image files are kept in an S3 bucket. On every push to the master branch Buddy will test and upload your website to the SFTP server + and update assets on AWS S3.

Deploy to Elastic Beanstalk

AWS Elastic Beanstalk is a classic PaaS service, similar to Heroku or Google App Engine. It lets developers upload, build and serve their code, leaving infrastructure configuration and scaling at the AWS side.

Example pipeline:

Deployment to Elastic Beanstalk is based on uploading a zip file with the application code. Buddy lets you create a pipeline that will upload the package automatically on push, on demand, or recurrently at a given time. Just like with S3, you can add build and test actions before the deployment.

You can also Dockerize your apps first and deploy them Elastic Beanstalk later:

Build and push Docker image to ECR

Amazon EC2 Container Registry is a Docker image storage for AWS developers.

Example pipeline:

To build a Docker image, you need a repository with the application code and a dockerfile with instructions how the image should be built. You can configure Buddy to build a new Docker image and push it to the ECR on every push to the selected branch. It’s also possible to add an SSH action that will pull the Docker image on the selected host and launch the new version of the application.

You can read more about building Docker images in this article

Selecting ECR registry in Docker image build action

Run Lambda function

AWS Lambda allows developers run code without provisioning servers. It scales to the size of the application and execute only when required, from a couple of requests per day to thousands of operations per second. With Buddy, you can automate deployment of Lambda functions to S3 buckets or trigger the functions with a dedicated Lambda action.

Example pipeline:

Let’s assume we have a web application with backend executed in Lambda functions. Both backend and frontend is stored in the same repository. The pipeline for that could look like this:

  1. Build and test application on every push to repo
  2. If all tests have passed, use Lambda function to perform backup
  3. Deploy application frontend to SFTP server
  4. Upload updated backend files to Amazon S3 with another Lambda function
Details of Lambda action

Deploy to CodeDeploy

CodeDeploy is a tool that facilitates application deployment to EC2 instances and custom user servers. The whole process boils down to uploading the app to CodeDeploy via S3, with the rest of operations handled entirely by AWS.

Example pipeline

Let’s assume we have a Node.js project that requires performing Gulp tasks and tests before the deployment. With Buddy, you can create a pipeline that will, for example, execute all of the above once a day at midnight – provided there were any changes at all in the repository. If one of the actions has failed, a notification with the error description will be sent to the selected Slack channel.

Example Gulp-CodeDeploy-Slack pipeline

Appendix: AWS Policies required by Buddy

In order to make the AWS actions work properly, you need to define the policies for them. You can find the complete list of policies here.

Buddy v1.4.39 Released

New features

  • Something BIG is coming. Stay tuned.


  • Better support of submodules in the Code tab
  • If you have two or more integrations of one type (eg. AWS) the list of integrated items in the action settings (eg. S3 buckets in Deployment to S3) will now display the ID’s of their parent integration
  • Every AWS action now displays the list of policies it requires. You can find the full list here

Bug fixes

  • Fixed bug with uploading files from the filesystem to a relative path on SFTP server

Get started now

14 days of unlimited trial. No credit card required.