Buddy makes it simple to add insurance to your software application. One code snippet provides access to and transaction of any type of insurance.

Buddy

buddy

This article will explain how to secure yourself from merging errors in your projects with BuddyWorks tests run on Buddy. GitHub Introduction Git along with its branches seems to be the best invention over the ages (at least for developers). Adding branches, gitflow and pull requests to development workflow is a perfect way to make your quality better. code Gitflow in practice usually looks like this: Junior Developer gets a task ‘extend a new feature’ He/she adds a new branch and codes the feature Once the feature is ready, the developer adds a pull request Senior Developer checks the code and assigns back with the comments Eventually, the feature branch is merged into the master branch and the brand new feature is ready to be deployed Bear in mind that no matter how well-skilled the Senior Dev is, such approach doesn't guarantee that the code includes no errors. The principle rule of Continuous Integration states that all changes made in the code need to be tested before merging them to the master branch. Read the whole article here .

How to protect code with Buddy and GitHub status checks

The following article will guide you how to set up Continuous Deployment to Azure using Buddy. : Upon reading this guide you will be able to Initialize Continuous Deployment on Microsoft Azure Create a pipeline in Buddy that will deliver your .NET app to Azure Configure Buddy to test your app before deployment Why do I need Continuous Deployment? Usually, developers write, compile and test code locally and then manually upload the package to the server. However, once the project grows bigger and more developers start to take part in it, : problems begin to appear Deployment preparation is getting more time-consuming as more time is needed for preparation. Software iteration is getting longer with every release, which results in less feedback from the client. Testing is more difficult as every team member has their own development environment. Team members need to communicate more often, increasing the risk of communication failures. The problems above can be successfully addressed by implementing a build server and deployment automation to your workflow. What does it mean for the development process? The software is built and tested in one consistent environment, avoiding dependencies on local dev boxes. You save time on setting up builds, installing required software, etc. Having one centralized build server provides easy access to code metrics, making it easier to properly cover your code with tests. Automatic deployments allow you to release software and receive feedback more often with the whole process simplified to minimum. As you can see, these are some serious benefits one shouldn’t reject easily. The following guide will tell how to use Buddy to apply Continuous Deployment to your projects so you can take advantage of all of the above. Like what you read? . Follow the full article here

How to set up CI/CD with Buddy and Azure

Flow is a popular, flexible project and task management software, used by teams in companies such as Apple, Shopify or TED. It is designed by the people behind Dribble — probably the largest community of web designers. Software Stack The Flow site is a simple & PHP app that uses DigitalOcean, Fortrabbit & AWS CloudFront for hosting: marketing Node.js We wanted a tool that could be as simple or robust as we needed it to be. Buddy was easily able to scale from a simple test runner to a full CI suite as needed. – says Dan Castello of getflow.com Pipelines Flow’s pipelines are all well-crafted and self-explanatory. The way how they keep it all organized makes it an example of well executed continuous delivery workflow. Here’s the pipeline responsible for : delivery to Production It was great to see we could easily implement something similar with minimal setup with Atomic Deploys. Makes tracking releases and rolling back super easy. Delivery to Staging looks neat as well, with the in one of the steps: application dockerized Flow also uses Buddy to and send a notification in case there’s something wrong: monitor the website for downtime Castello praised the simplicity of both the application and the onboarding process: Buddy was super simple to setup. The pre-made actions are great, especially for someone that’s new to the tool. Once we had a clear understanding of the capabilities of Buddy, we were able to fine tune the pipeline to our needs. The pipeline system is extremely clear. Onboarding a new developer to the system is as easy as walking them through each step of the pipeline. Everything you need is laid out in each step. There are no buried configs or environment variables. Last but not least, it was our support that was called the #1 feature. So proud! Probably the best thing about Buddy has been the support. Using the Intercom widget in the app is great. You guys have been super helpful! Thanks Dan, always a pleasure working with you guys! 🔥 Sign up at to automate your deployment now! 🔥 buddy.works

How Flow Project Management automates website deployments

With simplicity laying at its core, has always seemed like a perfect complement to Buddy. And so it is: over 50% of our users uses Slack action in their pipelines. Slack The most common use-case for Slack and Buddy is sending notifications on finished builds and deployments to your team channel. However, not many developers know that you can also run deployments directly from Slack: Use case: a WordPress Project Let’s imagine you have a application with the following actions: WordPress Prepare assets [Gulp] Deploy compiled assets [FTP] Notify your team of finished deployment or send message to QA that something went wrong [Slack] With Buddy, you can trigger all of the above with a simple command. run Set up a project with Buddy with your GitHub/Bitbucket account or email Sign up to Buddy Create a new project, select your Git provider, and choose your project: Set up a delivery pipeline Now let’s add a delivery pipeline that will build and deliver your project upon receiving the command: Click Add a new pipeline Set the trigger mode to ‘On click’ Select the branch from which you want to deploy Click when ready Add a new pipeline Like what your read? Check out the full guide here!

How to deploy WordPress directly from Slack

lets you manage containerized applications on a cluster of nodes. If you need to deploy and scale your application on the fly without consuming more resources that required, that’s a solution for you. Kubernetes Buddy lets you the whole delivery process to one git push to your repo. And these are the benefits: automate you don’t have to enter the commands manually every time you get precise feedback in case there’s an error in .yml files you don’t need a DevOps specialist around to update your application you can expand your delivery pipeline with builds and tests before the deployment The main objective of this article is to tell you how to do that in a series of a few simple steps. Set up a project with Buddy with GitHub/Bitbucket or email Sign up to Buddy Create a new project, select your Git provider, and choose your WP project: Configure Pipeline #1: Apply K8s deployment The first pipeline will automatically apply configuration changes to your K8s volumes and WordPress instance on a push to branch: Click and set the trigger mode to ‘On every push’ Add a new pipeline Select the branch that will trigger the execution Click Add a new pipeline Like what you read? ! Check out the full guide here

How to automate Kubernetes deployments

This guide covers creating K8s volumes and configuring a WP instance with a MySQL database in a most simple way — a perfect introduction to for newbies. Kubernetes It is a direct followup to the articles on and of projects, allowing you to introduce the power of Docker to your dev setup. Now it’s time to unleash it on a cluster of Google-powered nodes. dockerizing automating the delivery WordPress Configure a PersistentVolume in the K8s cluter Since we only have one node in the cluster we’ll use a volume. This type of volume mounts the path from the node's filesystem into K8s. hostPath Create volumes.yml apiVersion: v1kind: PersistentVolumemetadata:  name: local-pv-1  labels:    type: localspec:  capacity:    storage: 10Gi  accessModes:    - ReadWriteOnce  hostPath:    path: /k8/volume/pv-1---apiVersion: v1kind: PersistentVolumemetadata:  name: local-pv-2  labels:    type: localspec:  capacity:    storage: 10Gi  accessModes:    - ReadWriteOnce  hostPath:    path: /k8/volume/pv-2 This config will create two R/W 10GB volumes in the node paths: /k8/volume/pv-1/k8/volume/pv-2 Create your K8s volumes To create the volumes, run kubectl apply -f volumes.yml You can run the command below to check if eveything’s correct: kubectl get pvNAME       CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGElocal-pv-1 10Gi     RWO         Retain        Available                        13slocal-pv-2 10Gi     RWO         Retain        Available                        13s Like what your read? Check out the full guide here! Other posts: 1. How to Dockerize WordPress sites 2. How to automate WordPress delivery with Docker and Buddy

How to run WordPress on Kubernetes

In this article we’ll show you how to automatically deploy to servers managed by — in the easiest way possible. WordPress GoDaddy The pains of deployment Updating a website nowadays is a challenge: before uploading it to the server you probably need to run some tasks with Gulp or Grunt, bundle assets with Webpack, update media on S3, and so on, and so on. Oh, and don’t forget about flushing that cache after the deployment! You can do all of the above with DevOps tools like Jenkins, but to an average developer spending several hours on configuration seems like an overkill. Not many developers know, however, that you can easily streamline all of this stuff down to a push to your Git repository with a simple tool called Buddy. single Automation simplified Buddy lets you deploy your website on a single push to repo, on click, or automatically on a time interval. You can deploy anywhere: FTP, SFTP, DigitalOcean, AWS, Google, and so on. In this example we shall use SFTP, the secure type of protocol we always advise over regular FTP. In short, Buddy uses delivery pipelines to deploy your website. Configuration is very fast and feels like building a house of bricks: all you need to do is pick an action, configure access details, and arrange it in line. Step 1: Configure the pipeline 1. with your GitHub account and select the repository with your website sources: Sign up to Buddy 2. Create a , switch the trigger mode to , and select the to which the pipeline will be assigned. For example, if you assign the pipeline to the Master branch, it will be automatically executed on every push to Master. new pipeline on push branch 3. Now it’s time to configure the delivery. Select the action and enter the details to your GoDaddy instance (hostname, username, and password) SFTP There you can also select the remote path where Buddy will deploy the files, for example ~/html/wp-content/themes/my-theme You can find the credentials in your : click the Settings button of the managed WordPress server and Switch to the SSH & SFTP tab. GoDaddy account 4. The last part is flushing the cache after the deployment. Select the action and fill in the same connection credentials that you used in step 3. In the commands field, enter: SSH wp godaddy cache flush You can add more commands if you wish, each in a separate line: wp godaddy cache flushwp theme update --allwp core update 5. With everything in place, click to save the changes. Add new pipeline Step 2: Run the pipeline All you need to do is make a push to the assigned branch and watch Buddy automatically update your website: Step 3: Expand the pipeline The pipeline above can be easily expanded with additional actions. You can add run Gulp/Grunts before the deployment, update assets in your S3 bucket, send a notification to your Slack channel, and much more. You can also set up monitoring that will check your website for downtime and let you know to your mobile: All of a sudden, this whole DevOps thing doesn’t seem so bad, does it? :) Automate now! If you’d like to learn more about handling WordPress deployments, you can check out our , or reach out via the live-chat on the site. The service has a 14-day trial with 1 project always free, which makes it perfect for updating your side project. guides section Thanks for reading!

How to deploy WordPress from GitHub to GoDaddy web hosting

Disclaimer: Buddy.Works is a tool that helps developers automate tests and deployments of their applications. In this article we’d like to compare the most common delivery workflows for PHP projects—and try to figure out which one is the best. PHP delivery overview Each single application differs one from another, just like the delivery process. The most frequent steps for delivery usually look like this: PHP Test app Download dependencies ( ) Composer Compile assets (Gulp/ / ) Webpack Grunt Deploy to server Of course, more actions can be undertaken here. For instance, you may want to migrate the databases or restart your server via SSH — all of it depends on the project specifications and hardware that is used. 2 important things Before we go further, there are two things that should be highlighted every single time the word “deployment” comes into play: I. Keep everything in version control! Application source, configuration files, documentation, db migration scripts —you should keep all of it safe and sound in the repo. Of course, there are exceptions to every rule (especially in IT), which brings us to the second rule: II. Never keep dependencies and compiled apps in version control! We explained the reasons why this shouldn’t be done . Let’s call in the reason that frightens the developers the most (apart from being treated like a by their family). here 24/7 IT service If you want to find out more, check our guide at: Buddy Guide - 5 ways to deploy PHP applications

5 ways to deploy PHP applications

Creating a Hello World website with Node.js We’ll start with creating a simple application, just like we usually do. The subsequent part of this article will explain how to write, run, and automate tests with BuddyWorks. Node.js Install Node.js If that’s the first time you work with Node.js, install the npm manager first: nodejs.org/en/download/package-manager Install NPM and Mocha Create a directory for the application: mkdir myapp && cd myapp Now, npm should be initialized. We’ll use it in order to create a with the framework: package.json Mocha npm init You will be asked for the application’s details. Type the following: name: hello-world entry point: app.js test command: This framework will be used for testing the application ./node_modules/.bin/mocha Confirm the rest of the values by hitting enter. Create Hello World with Express framework Express Node.js web application framework will be used for building the app: npm install express --save Details of Hello World Once you already have everything installed, let’s create an file with a simple HTTP server that will serve our Hello World website: app.js //Load express module with `require` directivevar express = require('express')var app = express()

//Define request response in root URL (/)app.get('/', function (req, res) {  res.send('Hello World')})

//Launch listening server on port 8080app.listen(8080, function () {  console.log('App listening on port 8080!')}) Run the app Now, the application is ready to launch: $ node app.js Go to: in your browser to view it. http://localhost:8080/ Configuring unit tests with Mocha and Chai Each single application should be tested before the deployment to the server, especially, if it’s a welcome site that creates the first impression. Here, we will use Mocha as the test running framework, and Chai as the assertion library. Install Mocha and Chai Make sure to add Mocha and Chai packages to the : package.json npm install mocha --savenpm install chai --save Add a test file Now, it’s time for defining our first test… Like what you read? ! Check out the full guide here

How to run Mocha/Chai unit tests on Node.js apps

With this article you’ll learn how to prepare a image of a application, push it to the registry, and use Docker in Continuous Delivery. Docker Laravel Introduction Laravel Laravel is used to build web applications of any type you want. This framework is surprisingly fast, user-friendly, and very well documented. As you can learn from its official introduction, Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Laravel attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching. Docker Docker, on the other hand, is a virtualization method that eliminates the “works on my machine” issues when cooperating on code with other developers. Due to the Docker’s slightly different approach to the virtualization architecture it’s also: faster and less resource-consuming than regular VM’s easier to set up and modify easy to reuse: you can pick an existing Docker image and install any missing libraries and packages (similar to class inheritance) shareable: you can push images to Docker registries and pull them on other machines, just like you push and pull code from Git Dockerizing Laravel application In this guide we’ll use a simple calculator written with the Laravel framework. Make sure to fork from our GitHub profile and run it with . github.com/buddy-works/laravel-first-steps php artisan serve Please mind we use `php artisan serve` for test purposes only. For production you should use an image with Apache or Nginx. The calculator should be launched in a Docker container. What we need is a Dockerfile with the description of the Docker image that will run the Docker container. Think it’s complicated? Don’t worry, we’ll walk you through the process and describe everything in detail. The full version of the guide is available for free on our website: Laravel in Docker.

Laravel in Docker

Introduction The explained the process of creating unit and feature tests, and showed you how to automate them with Buddy. With this guide, you’ll learn how to run tests by using Dusk. previous article E2E Laravel Laravel Dusk is simply one of the kind of browser tests introduced in Laravel in v5.4. The tests use the ChromeDriver by default, but you can also configure them to use Selenium in a different browser. Test project If you have no idea how to add the tests, we’ll guide you through the process using the example of a simple calculator. In , you can see how to create a calculator like that. this guide At the beginning, make sure to fork and clone the project github.com/buddy-works/laravel-first-steps Then, you can check the application immediately by running: $ laravel-first-steps$ composer install$ php artisan serve NOTE: If you have any trouble, check if you installed . all required things Install Dusk If you want to install Dusk, just follow the steps: Install Laravel Dusk and add it to the project’s dependency: $ composer require laravel/dusk Register DuskServiceProvider. Open and add the namespace: app\Providers\AppServiceProvider.php use Laravel\Dusk\DuskServiceProvider; Register the provider in the method by adding: register if ($this->app->environment('local', 'testing')) {     $this->app->register(DuskServiceProvider::class);    } The entire file should look like this: AppServiceProvider <?php

namespace App\Providers;

use Illuminate\Support\ServiceProvider;use Laravel\Dusk\DuskServiceProvider;

class AppServiceProvider extends ServiceProvider{    /**     * Bootstrap any application services.     *     * @return void     */    public function boot()    {        //    }

    /**     * Register any application services.     *     * @return void     */    public function register()    {        if ($this->app->environment('local', 'testing')) {            $this->app->register(DuskServiceProvider::class);        }    }} Lastly, install Dusk by executing $ php artisan dusk:install Writing first Dusk test At first, the exemplary test should be removed or it will return errors: $ rm tests/Browser/ExampleTest.php Once done, make sure to add our first test by executing the command. Then… artisan Want to learn more? . Follow the full article here

How to run and automate E2E tests using Laravel Dusk

Objectives of this guide is a set of tools frequently used for testing applications: it fires up a page in the web browser and examines its contents paying special attention to errors. It can also bring on an interaction with the page checking the contents later. Selenium After reading this guide you’ll be able to: Write Selenium tests in Node.js Run test locally on the Selenium Server Automate your testing processes using Buddy CI/CD Writing the first Selenium task Let’s set a task that will fire up Buddy website in Chrome browser and take a screenshot. At the beginning, though, you should … install Node.js Want to learn more? . Follow the full article here

How to write Selenium tests in Node.js with WebDriverIO

This article will show you how to configure npm modules in a proper way and use Buddy to automatically test and publish your packages Objectives of this guide This guide will show you how to: Create an npm package the package in the registry Publish testing and publishing of the npm package thanks to Buddy Automate Requirements The first thing you need to do is to install the following things: GIT Node and npm Creating an npm package Begin with creating a folder and initializing a Git repository so that your package remains safe under version control: mkdir my_first_npm_modulecd my_first_npm_modulegit init Next, add which will contain the details of your module. You can easily do that by running this command: package.json npm init You will be asked to provide the information about your package: name version (usually set to ) main value index.js Once done, check the contents of . It should look like this: package.json { "name": "buddy-demo-package", "version": "1.0.3", "description": "",

 "main": "index.js", "scripts": {  "test": "echo \"Error: no test specified\" && exit 1"  },  "author": "",  "license": "ISC"} In the functions should be provided as a property of the object. Here's an example: index.js exports exports.printMsg = function() {console.log("My first package message");} Once everything is set, make sure to commit your files to the repo… Like what you read? . Follow the full article here

How to automate publishing npm packages to the registry

This article will explain you the process of introducing the Continuous Deployment approach to your .NET projects with Buddy and help you automate build and delivery activities. Objectives of this guide With this guide you’ll be able to: Familiarize with Buddy’s workflow. Set up a new project. Buddy Set up a Git version control for the project. Understand the concept of the pipeline. Set up a pipeline that on every push to the repository: Builds and tests the C# application. Deploys the application to the server. Why should you actually read this text? Firstly: it takes five minutes, the guide is free and chances are we can contribute to your current CI/CD workflow — we like to share the experience. Secondly: if you don’t get familiar with CI/CD, we strongly encourage you to have a closer look at the concept. You know for sure the agile approach, which aim is to shorten the development cycle time to the minimum. The reason for that is obvious: the faster the software moves to the next stage of the development process, the faster you get the feedback and will be able to develop and deliver the improved and enhanced version. Sounds cool, but if you want to give CI/CD a try, you’ll have to automate your work and this is what this guide is about — it shows how to drop the boring, time-consuming, error-generating manual tasks everyone hates and allow Buddy to complete them for you. Like what you read? . Follow the full article here

How to Build and Deploy .NET Projects

This guide describes how to use branches, branch permissions and merge requests to improve source code quality with Buddy. Objectives of this guide With this guide you’ll be able to: Get familiar with and understand the link between this approach and quality assurance processes. Git workflow Understand the concept of a branch, branch permission and merge request and their role in workflow. Git Find out how to employ the above tools in your project to improve the quality of your . code Learn how to easily set up branches and run merge requests to follow the industry standards and improve your development process. Code review — the right tool to improve quality Code reviews allow you to: Detect errors faster, at an early stage of the development process. Improve code transparency and consistency. Follow industry standards and best practices concerning the code. Educate the development team and spark the collaboration. When should you schedule your code review? Before you introduce any major change into the application. And this is where branches come in handy. Branches and merge requests in Buddy Every new feature or smaller change, every bug fix you’re working on, should form a separate branch, ready to access and review by someone responsible for marking your code as “checked and approved” and integrating it with the application. With Buddy you can work with any number of branches, at different development stages and with different access rights (permissions) and coordinate the merging process using merge requests. Like what you read? . Check out the full article here

How to properly use Git branches to improve code quality

This is a 5-minute guide on how to put your code under and its deployment. version control automate Import an existing website to a new Buddy project Working with Buddy is based on projects which consist of: The Git repository with the source code of the website. The delivery automation pipelines. Create a new project and use the import from an FTP server option. You are required to enter the FTP server information and the path, and Buddy will download the files and move them into the repository. Below you can see how to do it: Setting Up a New Project Like what you read? . Check out the full article here

Quick Start with Version Control and Continuous Delivery

This guide will explain how to use Docker in everyday work and move on with Continuous . Development Objectives of this guide This guide will: Explain you the basics of . Docker Show you how to use Docker throughout the development process. Illustrate the automation of the deployment process with BuddyWorks and Docker. The contents of this guide require basic Git knowledge— . you can learn Git here Why should you care about Docker? As a developer, you probably know that before you can run an application (for example, a website) on your machine you need to configure its environment first. The list of tasks required to do that may be pretty long and include: Installing database version xx.xxx Installing file server version yy.yyy Installing package a version xy.zzz and so on… Environment management is cumbersome and expensive Every change in the environment, like database version change, adding a new package or any other dependency, means that: Every developer has to introduce this particular change to his machine Upon release all the changes have to be introduced to the Production server It’s hard to keep track of dependencies without proper tools. And still, with or without them, configuration-related problems tend to emerge unexpectedly and are hard to debug and fix. This is why over the years we’ve tested various methods of ruling them out. Like what you read? . Check out the full article here

Introduction to Docker

The main idea of Continuous Delivery is to allow developers to build, test and deploy software faster and more frequently. This tutorial will explain you how to optimize your workflow so that your application is automatically tested and pushed to on every push to the Master branch using Buddy CI/CD. Please keep in mind you’ll need a Heroku account with one empty application to use it in your Buddy pipeline. Heroku Initializing version control for your project First we need to import your project to Buddy and put it under version control. For this presentation we should use a simple servlet-based web application. Java Create a , choose as the Git provider, use the option and paste the link to the Java project: new project Buddy Import ZIP archive https://assets.buddy.works/guides/buddy-simple-java-project.zip Importing project to Buddy NOTES: If you’re a GitHub user, you can fork the sample project from , select GitHub as the provider, and select the project from the list upon integrating our profile If you’re not familiar with Git, will help you get started this guide Like what you read? . Check out the full article here

Stories, News & Mentions about BUDDY

Buddy’s Stories on HackerNoon