Our great sponsors
-
earthly
Super simple build framework with fast, repeatable builds and an instantly familiar syntax – like Dockerfile and Makefile had a baby.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
funky
Funky takes shell functions to the next level by making them easier to define, more flexible, and more interactive.
-
The `earthly ls` idea is great. We do have shell autocompletions but that is not quite the same. I will add a ticket for that.
Cache misses can be a bit inscrutable. It could be the buildkit GC is running, because disk space is getting scarce, or that some arg or file change caused the cache to be considered invalid.
Caching is an area we will continue to improve. We have a proposal for extended cache mounts here[1].
Thanks for using earthly!
[1] https://github.com/earthly/earthly/issues/1399
re ls: `https://github.com/TekWizely/run` displays targets in the usage command (ie `run -h`). It might be worth looking at their output for inspiration. (Runfiles are doing something similar to Earthfiles).
could combine it with something like: https://github.com/bbugyi200/funky
Yep. An Earthfile describes your build steps in a containerized format. Because of this sandboxing it can run identically in CI or on your local. So you just describe your build in the earthfile and call it from CI. This means you can iterate locally and it also means switching CI vendors is simple.
You can see this in action with the Elixir Phoenix framework. They have an earthfile[1] and use github actions to run it for CI.
[1] https://github.com/phoenixframework/phoenix/blob/master/Eart...