[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-4983":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":16,"stars30d":17,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":18,"rankGlobal":9,"rankLanguage":9,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":20,"hasPages":20,"topics":22,"createdAt":9,"pushedAt":9,"updatedAt":38,"readmeContent":39,"aiSummary":40,"trendingCount":15,"starSnapshotCount":15,"syncStatus":41,"lastSyncTime":42,"discoverSource":43},4983,"earthly","earthly\u002Fearthly","Super simple build framework with fast, repeatable builds and an instantly familiar syntax – like Dockerfile and Makefile had a baby.","https:\u002F\u002Fearthly.dev",null,"Go",12038,454,55,690,0,1,17,42.97,"Mozilla Public License 2.0",false,"main",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"build","build-automation","build-system","build-tool","ci","ci-cd","cicd","container-builder","docker-images","dockerfiles","framework","hacktoberfest","hacktoberfest2020","hacktoberfest2021","reproducible-builds","2026-06-12 02:01:06","\u003Ch1>Earthly\u003C\u002Fh1>\n\n**Please note that Earthly is no longer actively maintained.** [Read more](https:\u002F\u002Fearthly.dev\u002Fblog\u002Fshutting-down-earthfiles-cloud).\n\n\u003Cdiv align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fearthly.dev\">\u003Cimg src=\"img\u002Flogo-banner-white-bg.png\" alt=\"Earthly\" width=\"700px\" \u002F>\u003C\u002Fa>\n  \u003Cbr\u002F>\n  \u003Cem>It’s like Docker for builds\u003C\u002Fem>\n\u003C\u002Fdiv>\n\u003Cbr\u002F>\n\n[![GitHub Actions CI](https:\u002F\u002Fgithub.com\u002Fearthly\u002Fearthly\u002Fworkflows\u002Fstaging%20release\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fearthly\u002Fearthly\u002Factions?query=workflow%3A%22staging%20release%22+branch%3Amain)\n[![Join the chat on Slack](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fslack-join%20chat-red.svg)](https:\u002F\u002Fearthly.dev\u002Fslack)\n[![Docs](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fdocs-git%20book-blue)](https:\u002F\u002Fdocs.earthly.dev)\n[![Website](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fwebsite-earthly.dev-blue)](https:\u002F\u002Fearthly.dev)\n[![Install Earthly](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fv\u002Frelease\u002Fearthly\u002Fearthly.svg?label=install&color=1f626c)](https:\u002F\u002Fearthly.dev\u002Fget-earthly)\n[![Docker Hub](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fdocker%20hub-earthly-blue)](https:\u002F\u002Fhub.docker.com\u002Fu\u002Fearthly)\n[![License MPL-2](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-MPL-blue.svg)](.\u002FLICENSE)\n\n[![Open in GitHub Codespaces](https:\u002F\u002Fgithub.com\u002Fcodespaces\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fcodespaces\u002Fnew?hide_repo_select=true&ref=main&repo=246903803)\n\n**🔁 Repeatable Builds** - *Write builds once, and run them anywhere – on your laptop, remote, and in any CI.*\n\n**❤️ Super Simple** - *Instantly recognizable syntax – like Dockerfile and Makefile had a baby.*\n\n**🛠 Compatible with Every Language, Framework, and Build Tool** - *If it runs on Linux, it runs on Earthly.*\n\n**🏘 Great for Monorepos and Polyrepos** - *Organize your build logic however makes the most sense for your project.*\n\n**💨 Fast Builds** - *Build caching and parallel execution makes builds fast automatically.*\n\n**♻️ Reuse, Don't Repeat** - *Never write the same code in multiple builds again.*\n\n---------------------------------\n\n🌎 [Earthly](https:\u002F\u002Fearthly.dev\u002F) is a versatile, approachable CI\u002FCD framework that runs every pipeline inside containers, giving you repeatable builds that you write once and run anywhere. It has a super simple, instantly recognizable syntax that is easy to write and understand – like Dockerfile and Makefile had a baby. And it leverages and augments popular build tools instead of replacing them, so you don’t have to rewrite all your builds no matter what languages you use.\n\n\u003Cbr\u002F>\n\u003Cdiv align=\"center\">\u003Ca href=\"https:\u002F\u002Fearthly.dev\u002Fget-earthly\">\u003Cimg src=\"docs\u002Fimg\u002Fget-earthly-button.png\" alt=\"Get Earthly\" title=\"Get Earthly\" \u002F>\u003C\u002Fa>\u003C\u002Fdiv>\n\n---------------------------------\n\n\u003Ch2 align=\"center\">Table of Contents\u003C\u002Fh2>\n\n* [Why use Earthly?](#why-use-earthly)\n* [Where Does Earthly Fit?](#where-does-earthly-fit)\n* [How Does It Work?](#how-does-it-work)\n* [Installation](#installation)\n* [Quick Start](#quick-start)\n* [Features](#features)\n* [FAQ](#faq)\n* [Contributing](#contributing)\n* [Licensing](#licensing)\n\n\n\u003Ch2 align=\"center\">Why Use Earthly?\u003C\u002Fh2>\n\n### 🔁 Repeatable Builds\n\nEarthly runs all builds in containers, making them self-contained, isolated, repeatable, and portable. This allows for faster iteration on build scripts and easier debugging when something goes wrong – no more `git commit -m \"try again\"`. When you write a build, you know it will execute correctly no matter where it runs – your laptop, a colleague’s laptop, or any CI. You don’t have to configure language-specific tooling, install additional dependencies, or complicate your build scripts to ensure they are compatible with different OSs. Earthly gives you consistent, repeatable builds regardless of where they run.\n\n\n### ❤️ Super Simple\n\nEarthly’s syntax is easy to write and understand. Most engineers can read an Earthfile instantly, without prior knowledge of Earthly. We combined some of the best ideas from Dockerfiles and Makefiles into one specification – like Dockerfile and Makefile had a baby.\n\n\n### 🛠 Compatible with Every Language, Framework, and Build Tool\n\nEarthly works with the compilers and build tools you use. If it runs on Linux, it runs on Earthly. And you don’t have to rewrite your existing builds or replace your `package.json`, `go.mod`, `build.gradle`, or `Cargo.toml` files. You can use Earthly as a wrapper around your existing tooling and still get Earthly’s repeatable builds, parallel execution, and build caching.\n\n\n### 🏘 Great for Monorepos and Polyrepos\n\nEarthly is great for both monorepos and polyrepos. You can split your build logic across multiple Earthfiles, placing some deeper inside the directory structure or even in other repositories. Referencing targets from other Earthfiles is easy regardless of where they are stored. So you can organize your build logic however makes the most sense for your project.\n\n\n### 💨 Fast Builds\n\nEarthly automatically executes build targets in parallel and makes maximum use of cache. This makes builds fast. Earthly also has powerful shared caching capabilities that speed up builds frequently run across a team or in sandboxed environments, such as Earthly Satellites, GitHub Actions, or your CI.\n\nIf your build has multiple steps, Earthly will:\n1. Build a directed acyclic graph (DAG).\n2. Isolate execution of each step.\n3. Run independent steps in parallel.\n4. Cache results for future use.\n\n\n### ♻️ Reuse, Don't Repeat\n\nNever have to write the same code in multiple builds again. With Earthly, you can reuse targets, artifacts, and images across multiple Earthfiles, even ones in other repositories, in a single line. Earthly is cache-aware, based on the individual hashes of each file, and has shared caching capabilities. So you can create a vast and efficient build hierarchy that only executes the minimum required steps.\n\n\n\u003Ch2 align=\"center\">Where Does Earthly Fit?\u003C\u002Fh2>\n\n\u003Cdiv align=\"center\">\u003Cimg src=\"docs\u002Fimg\u002Fintegration-diagram-v2.png\" alt=\"Earthly fits between language-specific tooling and the CI\" width=\"700px\" \u002F>\u003C\u002Fdiv>\n\nEarthly is meant to be used both on your development machine and in CI. It runs on top of your CI\u002FCD platform (such as [Jenkins](https:\u002F\u002Fdocs.earthly.dev\u002Fci-integration\u002Fvendor-specific-guides\u002Fjenkins), [Circle CI](https:\u002F\u002Fdocs.earthly.dev\u002Fexamples\u002Fcircle-integration), [GitHub Actions](https:\u002F\u002Fdocs.earthly.dev\u002Fexamples\u002Fgh-actions-integration), and [GitLab CI\u002FCD](https:\u002F\u002Fdocs.earthly.dev\u002Fci-integration\u002Fvendor-specific-guides\u002Fgitlab-integration)). Earthly provides the benefits of a modern build automation system wherever it runs – such as caching and parallelism. It is a glue layer between language-specific build tooling (like maven, gradle, npm, pip, go build) and CI, working like a wrapper around your build tooling and build logic that isolates build execution from the environments they run in.\n\n\n\u003Ch2 align=\"center\">How Does It Work?\u003C\u002Fh2>\n\nIn short: **containers**, **layer caching**, and **complex build graphs**!\n\nEarthly executes builds in containers, where execution is isolated. The dependencies of the build are explicitly specified in the build definition, thus making the build self-sufficient.\n\nWe use a target-based system to help users break up complex builds into reusable parts. Nothing is shared between targets other than clearly declared dependencies. Nothing shared means no unexpected race conditions. In fact, the build is executed in parallel whenever possible, without any need for the user to take care of any locking or unexpected environment interactions.\n\n> **ℹ️ Note**\n> Earthfiles might seem very similar to Dockerfile multi-stage builds. In fact, the [same technology](https:\u002F\u002Fgithub.com\u002Fmoby\u002Fbuildkit) is used underneath. However, a key difference is that Earthly is designed to be a general-purpose build system, not just a Docker image specification. Read more about [how Earthly is different from Dockerfiles](#how-is-earthly-different-from-dockerfiles).\n\n\n\u003Ch2 align=\"center\">Installation\u003C\u002Fh2>\n\nSee [installation instructions](https:\u002F\u002Fearthly.dev\u002Fget-earthly).\n\nTo build from source, check the [contributing page](.\u002FCONTRIBUTING.md).\n\n\n\u003Ch2 align=\"center\">Quick Start\u003C\u002Fh2>\n\nHere are some resources to get you started with Earthly\n\n* 🏁 [Getting started guide](https:\u002F\u002Fdocs.earthly.dev\u002Fbasics)\n* 👀 [Examples](.\u002Fexamples)\n  * [Go](.\u002Fexamples\u002Fgo)\n  * [JavaScript](.\u002Fexamples\u002Fjs)\n  * [Python](.\u002Fexamples\u002Fpython)\n  * [Java](.\u002Fexamples\u002Fjava)\n  * [Rust](.\u002Fexamples\u002Frust)\n  * [TypeScript (Node)](.\u002Fexamples\u002Ftypescript-node)\n  * [C++](.\u002Fexamples\u002Fcpp)\n  * [C](.\u002Fexamples\u002Fc)\n  * [dotnet (C#)](.\u002Fexamples\u002Fdotnet)\n  * [Ruby](.\u002Fexamples\u002Fruby)\n  * [Scala](.\u002Fexamples\u002Fscala)\n  * [Elixir](.\u002Fexamples\u002Felixir)\n  * [COBOL](.\u002Fexamples\u002Fcobol)\n  * [Monorepo](.\u002Fexamples\u002Fmonorepo)\n  * [Multirepo](.\u002Fexamples\u002Fmultirepo)\n  * [Multiplatform Builds](.\u002Fexamples\u002Fmultiplatform)\n  * [Integration Tests](.\u002Fexamples\u002Fintegration-test)\n* 🔍 Explore [Earthly's own build](https:\u002F\u002Fdocs.earthly.dev\u002Fdocs\u002Fexamples#earthlys-own-build)\n* ✔️ [Best practices](https:\u002F\u002Fdocs.earthly.dev\u002Fbest-practices)\n\nSee also the [full documentation](https:\u002F\u002Fdocs.earthly.dev).\n\nReference pages\n\n* 📑 [Earthfile reference](https:\u002F\u002Fdocs.earthly.dev\u002Fdocs\u002Fearthfile)\n* #️⃣ [Earthly command reference](https:\u002F\u002Fdocs.earthly.dev\u002Fdocs\u002Fearthly-command)\n* ⚙️ [Configuration reference](https:\u002F\u002Fdocs.earthly.dev\u002Fdocs\u002Fearthly-config)\n\n### A simple example (for Go)\n\n```earthly\n# Earthfile\nVERSION 0.8\nFROM golang:1.15-alpine3.13\nRUN apk --update --no-cache add git\nWORKDIR \u002Fgo-example\n\nall:\n  BUILD +lint\n  BUILD +docker\n\nbuild:\n  COPY main.go .\n  RUN go build -o build\u002Fgo-example main.go\n  SAVE ARTIFACT build\u002Fgo-example AS LOCAL build\u002Fgo-example\n\nlint:\n  RUN go get golang.org\u002Fx\u002Flint\u002Fgolint\n  COPY main.go .\n  RUN golint -set_exit_status .\u002F...\n\ndocker:\n  COPY +build\u002Fgo-example .\n  ENTRYPOINT [\"\u002Fgo-example\u002Fgo-example\"]\n  SAVE IMAGE go-example:latest\n```\n\n```go\n\u002F\u002F main.go\npackage main\n\nimport \"fmt\"\n\nfunc main() {\n  fmt.Println(\"hello world\")\n}\n```\n\nInvoke the build using `earthly +all`.\n\n\u003Cdiv align=\"center\">\u003Ca href=\"https:\u002F\u002Fasciinema.org\u002Fa\u002F351683?speed=2\">\u003Cimg src=\"img\u002Fdemo-351683.gif\" alt=\"Demonstration of a simple Earthly build\" title=\"View on asciinema.org\" width=\"600px\" \u002F>\u003C\u002Fa>\u003C\u002Fdiv>\n\nExamples for other languages are available in the [examples dir](.\u002Fexamples).\n\n\n\u003Ch2 align=\"center\">Features\u003C\u002Fh2>\n\n### ⛓ Parallelization that just works\n\nWhenever possible, Earthly automatically executes targets in parallel.\n\n\u003Cdiv align=\"center\">\u003Ca href=\"https:\u002F\u002Fasciinema.org\u002Fa\u002F351678?speed=2\">\u003Cimg src=\"img\u002Fdemo-351678.gif\" alt=\"Demonstration of Earthly's parallelization\" title=\"View on asciinema.org\" width=\"600px\" \u002F>\u003C\u002Fa>\u003C\u002Fdiv>\n\n### 💾 Caching that works the same as Docker builds\n\n\u003Cdiv align=\"center\">\u003Ca href=\"https:\u002F\u002Fasciinema.org\u002Fa\u002F351674?speed=2\">\u003Cimg src=\"img\u002Fdemo-351674.gif\" alt=\"Demonstration of Earthly's caching\" title=\"View on asciinema.org\" width=\"600px\" \u002F>\u003C\u002Fa>\u003C\u002Fdiv>\n\n### 🛠 Multi-platform support\n\nBuild for multiple platforms in parallel.\n\n```earthly\nVERSION 0.8\nall:\n    BUILD \\\n        --platform=linux\u002Famd64 \\\n        --platform=linux\u002Farm64 \\\n        --platform=linux\u002Farm\u002Fv7 \\\n        --platform=linux\u002Farm\u002Fv6 \\\n        +build\n\nbuild:\n    FROM alpine:3.18\n    CMD [\"uname\", \"-m\"]\n    SAVE IMAGE multiplatform-image\n```\n\n### 🤲 Build tools that work everywhere\n\nNo need to ask your team to install `protoc`, a specific version of Python, Java 1.6, or the .NET Core ecosystem. Install once in your Earthfile, and it works for everyone. Or even better, you can just make use of the rich Docker Hub ecosystem.\n\n```earthly\nVERSION 0.8\nFROM golang:1.15-alpine3.13\nWORKDIR \u002Fproto-example\n\nproto:\n  FROM namely\u002Fprotoc-all:1.29_4\n  COPY api.proto \u002Fdefs\n  RUN --entrypoint -- -f api.proto -l go\n  SAVE ARTIFACT .\u002Fgen\u002Fpb-go \u002Fpb AS LOCAL pb\n\nbuild:\n  COPY go.mod go.sum .\n  RUN go mod download\n  COPY +proto\u002Fpb pb\n  COPY main.go .\u002F\n  RUN go build -o build\u002Fproto-example main.go\n  SAVE ARTIFACT build\u002Fproto-example\n```\n\nSee full [example code](.\u002Fexamples\u002Freadme\u002Fproto).\n\n### 📦 Modern import system\n\nEarthly can be used to reference and build targets from other directories or even other repositories. For example, if we wanted to build [an example target from the `github.com\u002Fearthly\u002Fearthly` repository](.\u002Fexamples\u002Fgo\u002FEarthfile#L17-L20), we could issue\n\n```bash\n# Try it yourself! No need to clone.\nearthly github.com\u002Fearthly\u002Fearthly\u002Fexamples\u002Fgo:main+docker\n# Run the resulting image.\ndocker run --rm earthly\u002Fexamples:go\n```\n\n### 🔨 Reference other targets using +\n\nUse `+` to reference other targets and create complex build inter-dependencies.\n\n\u003Cdiv align=\"center\">\u003Ca href=\"https:\u002F\u002Fdocs.earthly.dev\u002Fguides\u002Ftarget-ref\">\u003Cimg src=\"docs\u002Fguides\u002Fimg\u002Fref-infographic-v2.png\" alt=\"Target and artifact reference syntax\" title=\"Reference targets using +\" width=\"600px\" \u002F>\u003C\u002Fa>\u003C\u002Fdiv>\n\nExamples\n\n* Same directory (same Earthfile)\n\n  ```earthly\n  BUILD +some-target\n  FROM +some-target\n  COPY +some-target\u002Fmy-artifact .\u002F\n  ```\n\n* Other directories\n\n  ```earthly\n  BUILD .\u002Fsome\u002Flocal\u002Fpath+some-target\n  FROM .\u002Fsome\u002Flocal\u002Fpath+some-target\n  COPY .\u002Fsome\u002Flocal\u002Fpath+some-target\u002Fmy-artifact .\u002F\n  ```\n\n* Other repositories\n\n  ```earthly\n  BUILD github.com\u002Fsomeone\u002Fsomeproject:v1.2.3+some-target\n  FROM github.com\u002Fsomeone\u002Fsomeproject:v1.2.3+some-target\n  COPY github.com\u002Fsomeone\u002Fsomeproject:v1.2.3+some-target\u002Fmy-artifact .\u002F\n  ```\n\n### 🔑 Cloud secrets support built-in\n\nSecrets are never stored within an image's layers and they are only available to the commands that need them.\n\n```bash\nearthly set \u002Fuser\u002Fgithub\u002Ftoken 'shhh...'\n```\n\n```earthly\nrelease:\n  RUN --push --secret GITHUB_TOKEN=user\u002Fgithub\u002Ftoken github-release upload file.bin\n```\n\n\n\u003Ch2 align=\"center\">FAQ\u003C\u002Fh2>\n\n### How is Earthly different from Dockerfiles?\n\n[Dockerfiles](https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Freference\u002Fbuilder\u002F) were designed for specifying the make-up of Docker images and that's where Dockerfiles stop. Earthly takes some key principles of Dockerfiles (like layer caching) but expands on the use cases. For example, Earthly can output regular artifacts, run unit and integration tests, and create several Docker images at a time - all outside the scope of Dockerfiles.\n\nIt is possible to use Dockerfiles in combination with other technologies (e.g., Makefiles or bash files) to solve such use cases. However, these combinations are difficult to parallelize, challenging to scale across repositories as they lack a robust import system, and often vary in style from one team to another. Earthly does not have these limitations as it was designed as a general-purpose build system.\n\nFor example, Earthly introduces a richer target, artifact, and image [referencing system](https:\u002F\u002Fdocs.earthly.dev\u002Fdocs\u002Fguides\u002Ftarget-ref), allowing for better reuse in complex builds spanning a single large repository or multiple repositories. Because Dockerfiles are only meant to describe one image at a time, such features are outside the scope of applicability of Dockerfiles.\n\n### How do I know if a command is a classic Dockerfile command or an Earthly command?\n\nCheck out the [Earthfile reference doc page](https:\u002F\u002Fdocs.earthly.dev\u002Fdocs\u002Fearthfile). It has all the commands there and specifies which commands are the same as Dockerfile commands and which are new.\n\n### Can Earthly build Dockerfiles?\n\nYes! You can use the command `FROM DOCKERFILE` to inherit the commands in an existing Dockerfile.\n\n```earthly\nbuild:\n  FROM DOCKERFILE .\n  SAVE IMAGE some-image:latest\n```\n\nYou may also optionally port your Dockerfiles to Earthly entirely. Translating Dockerfiles to Earthfiles is usually a matter of copy-pasting and making minor adjustments. See the [getting started page](https:\u002F\u002Fdocs.earthly.dev\u002Fbasics) for some Earthfile examples.\n\n### How is Earthly different from Bazel?\n\n[Bazel](https:\u002F\u002Fbazel.build) is a build tool developed by Google to optimize the speed, correctness, and reproducibility of their internal monorepo codebase. The main difference between Bazel and Earthly is that Bazel is a **build system**, whereas Earthly is a **general-purpose CI\u002FCD framework**. For a more in-depth explanation see [our FAQ](https:\u002F\u002Fearthly.dev\u002Ffaq#bazel).\n\n\n\u003Ch2 align=\"center\">Contributing\u003C\u002Fh2>\n\n* Please report bugs as [GitHub issues](https:\u002F\u002Fgithub.com\u002Fearthly\u002Fearthly\u002Fissues).\n* Join us on [Slack](https:\u002F\u002Fearthly.dev\u002Fslack)!\n* Questions via GitHub issues are welcome!\n* PRs welcome! But please give a heads-up in a GitHub issue before starting work. If there is no GitHub issue for what you want to do, please create one.\n* To build from source, check the [contributing page](.\u002FCONTRIBUTING.md).\n\n\n\u003Ch2 align=\"center\">Licensing\u003C\u002Fh2>\n\nEarthly is licensed under the Mozilla Public License Version 2.0. See [LICENSE](.\u002FLICENSE).\n","Earthly 是一个构建框架，旨在提供快速、可重复的构建过程，并采用了一种类似于 Dockerfile 和 Makefile 结合的直观语法。其核心功能包括支持跨平台的一致性构建、通过缓存和并行执行加速构建流程以及与多种语言、框架及现有构建工具的高度兼容性。此外，Earthly 还特别适合用于单体仓库或多仓库项目中组织复杂的构建逻辑。尽管该项目已不再积极维护，但其设计理念和技术特点使其仍然适用于需要高效、统一且易于理解的持续集成\u002F持续交付（CI\u002FCD）环境的企业或个人开发者。",2,"2026-06-11 03:01:55","top_language"]