#Using dagger on existing project
dapper seal
Hi there! At the moment each project has its own custom entrypoint to using Dagger, usually via a custom cli or script. This makes it difficult to quickly get a sense for the end user experience, like you’re trying to do.
Think of Dagger as a library which gives a project’s scripts superpowers.
We are planning to add a standardized entrypoint into any Dagger project, exactly as you expected. Discussion started here: https://github.com/dagger/dagger/issues/4414
And we are developing the solution here: #daggernauts
shadow beacon
got it ... i saw someone mention that you test the dagger project using dagger. is that documented ? i just need to make one run on a fairly interesting project. Also i really want to see how the new tui looks. any large example is good
dapper seal
got it ... i saw someone mention that you test the dagger project using dagger. ...
Yes, here are a few resources for how we use Dagger to ship Dagger 🙂
Our own custom script lives in https://github.com/dagger/dagger/tree/main/hack
You can see how we call that script from CI, for example this github actions workflow to run our tests: (look for the invocations of hack/make):
https://github.com/dagger/dagger/blob/main/.github/workflows/test.yml
shadow beacon
ok that did it .. thanks !!! this is what i was dying for dagger run ./hack/make sdk:go:test
i feel that could be part of the onboarding docs. this is an example of a dagger run. i love tui so maybe its just me !
shadow beacon
actually thnaks to you for jumping on this !!! really appreciated your help