#Hi Just found dagger and I love it and

1 messages · Page 1 of 1 (latest)

rapid depot
#

An explanation is great, but a link to some documentation may also suffice 🙂

brazen yoke
#

Hi @rapid depot , the only difference should be the UI. dagger run should be just as fast. If not, it’s a bug.

rapid depot
# 
go run ./ci  1.05s user 0.96s system 32% cpu 6.101 total
dagger run go run ./ci  1.78s user 1.24s system 44% cpu 6.798 total
#

I suppose it's the same! Ok so it's just a difference in UI then?

vital token
#

Yeah precisely. The TUI that the dagger CLI offers (i.e. dagger run) is new functionality. Both methods will continue to be supported.

In the near future you will be able to execute interesting things like modules (for more info see:#daggernauts) with the dagger CLI without necessarily needing to write your own pipeline from scratch.

rapid depot
#

Awesome. All the current documentation instructs you to run dagger pipelines via dagger run. I think it would be good to have a small blurb about the difference between running the SDKs directly or via a dagger session, and the conditions when one is more appropriate than the other (or if dagger run is always most recommended)

vital token
#

Thanks for the feedback, I agree its worth documenting this better in a high level overview.

vital token
# rapid depot Awesome. All the current documentation instructs you to run dagger pipelines via...

I just filed this issue, please add any additional comments if I missed something 🙂 https://github.com/dagger/dagger/issues/5903

GitHub
Make it more clear when to use SDK vs CLI · Issue #5903 · dagger/d...

What is the issue? It would be great to have a better high level overview of the differences between the CLI and the SDK to invoke dagger and when to use one or the other. Right now we have this in...

rapid depot
#

That's perfect! Thank you!

brazen yoke
#

@rapid depot the dagger run method is recommended unless you specifically want to develop a custom tool that embeds Dagger.

#

We’ll continue to support both as Lev said, but we consider the embedded method to be very niche, which is why we don’t advertise it everywhere in the docs

rapid depot
#

So... I am confused. Running a "script" whether it be a small javascript script, or a small Go Binary that calls the SDKs works as is. Using dagger run runs the script/binary but in the context of a dagger session which provides other niceties such as TUI and may provide future features like running project zenith shared components.

Please tell me if I got anything wrong above.

I don't understand the language around "embedding dagger" and what is wrong or niche around simply running the CI Binary without using dagger run (not that I am opposed to it)