Docker

Optimizing Selective Docker Builds in a Turborepo Monorepo on GitHub Actions

Our GitHub Actions matrix containers build workflow was always building every container image in our Turborepo monorepo — even if only a few packages had actually changed. This not only resulted in increased build time but also inflated our operational cost. In this post, I’ll will outline how we tackled this issue and implementing a robust solution that leverages Turborepo’s dry-run capabilities and GitHub Actions caching to build Docker images only for the changed packages.

This is part 2 of EOS quick-start. Please refer to [ Part 1 ] Introduction for basic information on EOS.IO

Installation and configuration

In EOS.IO there are three main progreams that weare going to use througout this tutorials:

• nodeos is n EOS node daemon
• keosd is a wallet keys daemon
• cleos is a cli - command line interface tool

Option 1. Run Docker image

This is the simplest and easiest way. Just run the following command to get into EOS enabled shell:

docker run -it eosio/eos:latest /bin/bash

Option 2. Build using build script

So according to the README on https://github.com/EOSIO/eos, all I need to do to run local testnet is: