earthly VS cuetorials.com

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

I have a website I maintain, many people tell me it has helped them

https://cuetorials.com

CUE(lang), because devops & yaml engineering has gotten out of hand

I maintain https://cuetorials.com and am heading up the CUE sig-infra group for the time being

If you need help with CUE(lang), we maintain https://cuetorials.com and have experience helping others adopt it at their companies

email is in my HN profile, same handle on GitHub and X

If you are more focused on the devops part, and not implementing a static site generator, then go with Python. For our static sites we use Hugo + GH Actions + Kubernetes (since we have a cluster anyway). There is not really any code involved here (example: https://github.com/hofstadter-io/cuetorials.com)

I'm personally interested to try https://docs.dagger.io/sdk/python/ for something. I used the CUE sdk, but it is effectively deprecated at this point. I use a mix of base, make, python, and CUE fro most devops / devex stuff now. Dagger makes it so local & CI stuff runs the same.

yup, I'm betting the proverbial ranch on CUE :]

I also maintain https://cuetorials.com

I also maintain https://cuetorials.com, bet the farm on CUE or something like that :]