run VS earthly

I've been using Run [0] for this purposes.

[0]: https://github.com/TekWizely/run

To the extent that posts like these evolve into discussing the merits of Make as a task runner, I would like to offer my tool for review:

* https://github.com/TekWizely/run

I built it to feel like make, but be better at managing tasks and wrappers.

If you are evaluating task runners and appreciate the simplicity of Make's syntax, I hope you'll give Run a try.

I invite you take a look at Run, a similar tool that I maintain:

* https://github.com/TekWizely/run

Support for including other Runfiles was recently introduced, with support for globbing and the ability to indicate if an error should be generated if no files are found.

Unrelated to this topic, I invite you take a look at my project which a tool purpose-built to be a better version of what your makefile became:

Run: Task runner that helps you easily manage and invoke small scripts and wrappers

https://github.com/TekWizely/run

Defining commands feels like make, but comes with a bunch of extras targeted at the needs of a task-runner.

I hope you'll check it out!

This looks like an interesting way to manage scripts globally. I could even see it able to manage n-sub-commands deep (vs usual "command sub-command" - maybe it already does?) by just trying to resolve each argument as a dir until you find a script to execute.

If you're interested in ways to better-manage small scripts and wrappers more locally, please take a look at my project, Run:

https://github.com/TekWizely/run

For those looking for a powerful task runners that feel like a makefile, please take a look at Run:

https://github.com/TekWizely/run

It's better a managing and invoking tasks and generates help text from comments.

Also CACHE keyword, for cache mounts. Makes incremental tools like compilers work well in the context of dockerfiles and layer caches.

That can extend beyond just producing docker iamges as well. Under the covers the CACHE keyword is how lib/rust in Earthly makes building Rust artifacts in CI faster.

https://github.com/earthly/earthly/issues/1399

earthly

A few of us will be around to answer questions if anyone has any. I myself worked only worked on the chmod feature which was pretty trivial.

https://github.com/earthly/earthly/pull/1821

[2] https://github.com/earthly/earthly/releases/tag/v0.7.0

# cat Makefile BIN_PATH = $(shell pwd)/bin $(shell mkdir $(BIN_PATH) &>/dev/null) EARTHLY = $(BIN_PATH)/earthly earthly: ifeq (,$(wildcard $(EARTHLY))) curl -L https://github.com/earthly/earthly/releases/download/v0.6.23/earthly-linux-amd64 -o $(EARTHLY) chmod +x $(EARTHLY) endif

I started to bring awareness to the Earthfiles goofy license, but it seems they've switched to MPL! https://github.com/earthly/earthly/releases/tag/v0.6.15

The (unfortunately named) Dagger is also an entry into that space: https://github.com/dagger/dagger#readme (Apache 2)

- https://github.com/earthly/earthly/tree/main/analytics

Another *monster* difference is that Dagger is (at least currently) Apache 2: https://github.com/dagger/dagger/blob/v0.2.4/LICENSE but Earthly went with BSL: https://github.com/earthly/earthly/blob/v0.6.12/LICENSE

That means I'm more likely to submit bugs and patches to Dagger, and I won't touch Earthly

Example build steps for a go application