Here we use the docker-install pipeline we created in the first example as a building block to a new pipeline, then we check for whether Minikube is installed and install it if it is not.ĭocker and Minikube are just examples of what Ferret can do the beauty of it is that you get to define what tools your developers need for their environments and build pipelines to make installation easy. using pipeline from aboveĭescription: install minikube locally if not installed. Let’s push the previously created pipeline to our common repo and reuse it in a pipeline for installing Minikube: stages:ĭescription: install docker locally if not installed. Then, execute your chosen pipeline: $ ferret setup -pipeline Example 2: pipeline composition In order to see a list of pipelines available, you can run $ ferret pipelinesĪnd a list of all of the pipeline files stored in your predefined repo will appear. $ ferret repository -owner=your-repo-owner -repository=repo-name -branch=master
For this to work, we will need to define a Github repository containing predefined pipelines. To do this, it fetches the pipelines from a Github repository (similar concept to Github Actions) or from a local YAML file and then executes the pipeline. If the computer is found to be missing Docker, here’s the output you would get:īut if Docker is already installed, and therefore installation is skipped, you would get this output instead: Sharing is caringįerret allows the reuse of predefined pipelines as steps inside newly created pipelines. Now let’s run the following command: $ ferret setup -f docker-install.yamlīy using a simple condition and checking the Docker version, we decide whether to install Docker or skip it. command: brew install homebrew/cask/dockerĭescription: start docker if it is not upĭescription: make sure docker server is up Let’s create a new file called docker-install.yaml with the following content: stages:ĭescription: install docker if it is not installed You are not sure whether it’s there already, but, if it’s not, you want to be sure to install it. Let’s assume you want to install Docker on a new computer, either for yourself or during IT provisioning. Once you’ve completed the installation, let’s showcase Ferret’s capabilities with a few swift examples.
Ready, Steady, Go! Note: Currently Ferret supports only MacOS and Linux (Homebrew supported Operating System) Instead of writing an instruction manual, such as a README, describing the steps needed to create your setup, you create a YAML file that describes your steps both descriptively and technically.įerret transforms the documentation into meaningful steps and executes the code, returning a clear output of the progress and status of the steps used in the pipeline itself.
No more “pesky” issuesįerret is a pipeline composition scripting framework, allowing you to create and reuse predefined scripts in one cohesive YAML file which is both readable and flexible.
Brew install docker engine code#
Imagine a world where your scripting code and documentation coincide and every change in code results in new and improved documentation.
Brew install docker engine how to#
But nowadays, especially in microservices architecture, setting up a local environment has becoming more and more complex, requiring the usage of many different tools (Docker, Shell, NPM, etc.) Documentation explaining how to set up the environment ages fast and is tedious to keep up-to-date. Running a local environment helps to speed up the development process as well as improve collaboration. What’s the first thing you do when you get a new laptop? For many engineers, it’s setting up a good development environment, which is key for developing and troubleshooting effectively.