New feature: AWS CLI

Every developer in the world knows exactly what AWS is. So does Buddy: it even has a separate section for Amazon services only. You can, for instance, upload a new version of the application to Elastic Beanstalk, deploy files to S3 or launch a Lambda function.

Update to Atomic deployments

Atomic deployments are the first in the series of pipeline templates that we introduced to Buddy.

In short, they allow you to update your website with zero downtime by uploading the files a cache directory on the server and switching the symlink of the web server to the new version when everything’s finished.

Recently we’ve modified the template by adding a feature that lets you define how many website versions you want to keep on the server.

Introducing: Private Git repositories

We’re excited to announce that private repositories are now supported by BuddyWorks!

This means you can hook up Buddy with repositories on your private Git server, as well any other external Git provider, including:

  • Assembla
  • CloudForge
  • Codebase
  • Deveo
  • RhodeCode
  • Springloops
  • Visual Studio Team Services

All you need to do is provide configuration details of your repo + set up a web hook in your version control that will automatically refresh the list of commits in Buddy and trigger the deployments:

Private repo configuration screen

So, if you guys know of any developer who couldn’t use BuddyWorks because it didn’t support their Git provider, do not hesitate and spread the good news! 🙌

Introducing: Rsync deployments

The most popular pipeline feature in Buddy is code delivery. You can use one of the many integrations to deploy your code – such as Elastic Beanstalk, Amazon S3, Rackspace, Google Cloud Storage or Microsoft Azure – or stick to the standard SFTP/SCP protocols, or even the good ol’ FTP.

Deployment tools such as Capistrano may be used as well, with Rsync joining the party in the latest release.

Rsync is a great tool which allows you to sync files between different locations. It checks the files and uploads only those that were changed. Until now you could only use Rsync by defining custom upload scripts in build actions at the end of the actual build commands.

In response to high popularity of this action, we’ve decided to add a dedicated action for Rsync. All you need to do is provide the server details and the path where the files will be uploaded, and Buddy will handle the rest for you.

Rsync action details

Additional options

By default, the Rsync action has these options enabled:

  • Compress file data during the transfer: Files are compressed on the upload, which increases the upload speed
  • Archive mode: this feature allows you to move symlinks (without hardlinks), permissions and groups, as well as times of file and owner modification
  • Delete extraneous files: when a file is deleted in the pipeline filesystem, it will also be deleted on the host.

If you’d like to learn more about Rsync and introduce it to your workflow, just let us know at the chat at the bottom right corner, or drop a word to support@buddy.works.

Buddy Goes Enterprise

Ever since BuddyWorks was conceived we wanted to deliver a service that could be installed on-premises: there are many companies who cannot use a cloud solution and would rather keep stuff in-house, usually because of regulations regarding code storage.

Exclusive preview: Buddy Sandboxes

INFO: UPDATE 25.05.2017

Today we have activated the beta of Sandboxes in over a hundred accounts of Buddy users: if you can see the Sandboxes tab in the top navigation menu, it means the luck is upon you :) Soon you will receive an email together with an invitation to a special Slack channel, where you can report feedback and share your impressions.

If you can’t see the tab, not all is lost: just drop an email to <sandboxes@buddy.works> with the URL to your account and we’ll activate the feature for you!

The Problem

Hosting development & staging versions of projects involves a pain of managing dozens locations. In-house previews, QA stages, client presentations – they all take much more hassle than they should. There are:

  • servers and vhosts that need to be set up
  • passwords that need to be remembered.
  • deployments that must be defined.

At the end, you have to remember what’s still in use and where, what’s alive and what’s a zombie—and you end up in a little sysadmin’s nightmare.

Get started now

14 days of unlimited trial. No credit card required.