Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Earthly v0.6

earthly.dev

Post reply on HN
Print view View original

31–38 of 38 posts

Re: Show HN: Earthly v0.6

#31

Post by andyonthewings »

honkycat wrote: post #8

I tried using Earthly, great product. Unfortunately, we rejected it at our organization due to how verbose the commands are. I want my users to be able to say `earthly plan-stage` for a terraform repo, and for it to work. But you cannot. You cannot have earthly automatically use environment variables from your env, you have to explicitly list the commands yourself using flags: $ earthly \ --build-arg AWS_ACCESS_KEY_I…

That's my biggest complain about earthly as well. There is `.env` support that ease the problem a bit: https://docs.earthly.dev/docs/earthly-command#environment-va...

Worth watching the reported issue at https://github.com/earthly/earthly/issues/707

Re: Show HN: Earthly v0.6

#32

Post by andyonthewings »

adamgordonbell wrote: post #10
honkycat wrote: post #8

I tried using Earthly, great product. Unfortunately, we rejected it at our organization due to how verbose the commands are. I want my users to be able to say `earthly plan-stage` for a terraform repo, and for it to work. But you cannot. You cannot have earthly automatically use environment variables from your env, you have to explicitly list the commands yourself using flags: $ earthly \ --build-arg AWS_ACCESS_KEY_I…

You may want to use secrets like this: earthly \ --secret-file config=/home/user/.aws/config \ +build But yes, Earthly optimizes for reproducibility, so implicitly pulling in ENVs is not something it does.

The required build arg and env var names are already listed in the Earthfile as `ARG` and `RUN --secret ...`. So I think specifying it in the commandline is redundant.

Re: Show HN: Earthly v0.6

#33

Post by adamgordonbell »

jazzdan wrote: post #5
cmckn wrote: post #3

I love earthly! It has been a joy to use. One thing I haven’t gotten right is caching. Some of my builds have targets they depend on that are very expensive but rarely change, and I haven’t been able to make sense of when those targets are (re)computed and when they aren’t. This results in many builds taking a long time, when the targets could be reused from a cache. Earthly is also missing something that I find to b…

+1 on `earthly ls`. I've also thought it would be valuable to have "public" and "private" targets. When looking at a new codebase it can be hard to know which targets I should use when developing, and which are purely for internal use. Good docs help with this too, but they are not always there.

We have a PR for the ls feature up:

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

Re: Show HN: Earthly v0.6

#34

Post by adamgordonbell »

andyonthewings wrote: post #31
honkycat wrote: post #8

I tried using Earthly, great product. Unfortunately, we rejected it at our organization due to how verbose the commands are. I want my users to be able to say `earthly plan-stage` for a terraform repo, and for it to work. But you cannot. You cannot have earthly automatically use environment variables from your env, you have to explicitly list the commands yourself using flags: $ earthly \ --build-arg AWS_ACCESS_KEY_I…

That's my biggest complain about earthly as well. There is `.env` support that ease the problem a bit: https://docs.earthly.dev/docs/earthly-command#environment-va... Worth watching the reported issue at https://github.com/earthly/earthly/issues/707

We do love getting all this input. Finding a way to make most use-cases ergonomic while still being reproducible is very important to us.

Thumbs-ups on tickets and comments help us prioritize features.

We already have a PR up for the `earthly ls` feature.

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

Re: Show HN: Earthly v0.6

#36

Post by f0e4c2f7 »

I haven't tried the product but looks interesting.

I've actually been looking into nixos to generate docker containers after that repl post the other day.

Aside from the software itself I wanted to compliment you on this image.

https://earthly.dev/blog/assets/images/earthly-v0-6/earthly-...

I really appreciate how much context is added there for what earthly actually does or is trying to do. I'll probably save that just to have it as an example to ask people to recreate when I'm baffled by their landing page.

Re: Show HN: Earthly v0.6

#37

Post by TekWizely »

politician wrote: post #14
vladaionescu wrote: post #4

Earlier quoted context omitted.

The `earthly ls` idea is great. We do have shell autocompletions but that is not quite the same thing. 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 he…

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).

Just a quick drive-by to say thanks for the call-out - I hope you're finding run to be a useful tool and would love to hear more about how you're using it!

Re: Show HN: Earthly v0.6

#38

Post by cmckn »

vladaionescu wrote: post #4
cmckn wrote: post #3

I love earthly! It has been a joy to use. One thing I haven’t gotten right is caching. Some of my builds have targets they depend on that are very expensive but rarely change, and I haven’t been able to make sense of when those targets are (re)computed and when they aren’t. This results in many builds taking a long time, when the targets could be reused from a cache. Earthly is also missing something that I find to b…

The `earthly ls` idea is great. We do have shell autocompletions but that is not quite the same thing. 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 he…

I didn't know about the autocomplete, that is really helpful; and I'm excited to see `ls` PR'd! Huge thanks to the contributors.

I think some of my cache misses were a rookie mistake: I was building a few expensive targets on a `FROM ...:latest` base. The base image changed often enough to make the cache misses annoying, but infrequent enough to make me think it was GC. My builds are much happier now! :)

Post reply on HN