is it possible to share github repository with demo code? great demo and pretty cool discussion! seems to be cool tool to start writing pipelines in :)
Hi Folks! Really loved what you're doing there at Dagger! I have a conceptual question though: you say one of the appeals to dagger it the ability to be "platform agnostic" in the sense that I'm able to basically run the same code locally or on any platform. How is this different then scripting my entire pipeline in bash for example, and then having different platforms run those scripts for me? What's special about dagger in that regard, other than the fact you get other languages in an SDK?
I think the biggest difference would be that Dagger runs everything in containers, so all dependency management is handled that way. So you could probably achieve something similar using Bash and Docker. But then you have both Bash scripts and Dockerfiles to manage, and I think a big part of the Dagger USP is that you can work within whatever language you wrote the rest of your app in. So if you write a Go application, you can keep using Go for the pipeline definitions, instead of adding Bash and Docker to the mix. And add to that many optimizations and guardrails that Dagger adds, for example enhanced cache management and traces, and it starts to look pretty compelling I think.
Hi All! Jeremy from Dagger here. I've posted links to these repos on here a couple of times, but the comments have been deleted, perhaps by an automated system. I'll work to get them into the Dagger examples repo on GitHub this week. Thanks!
Great job and an awesome demo! I would also like to stress that we need that demo git repository code because dagger documentation doesn't have that yet. :plz:
is it possible to share github repository with demo code?
great demo and pretty cool discussion!
seems to be cool tool to start writing pipelines in :)
Would second a request for a repo - the content in this does not appear to be in the dagger docs guides.
Hi Folks! Really loved what you're doing there at Dagger!
I have a conceptual question though: you say one of the appeals to dagger it the ability to be "platform agnostic" in the sense that I'm able to basically run the same code locally or on any platform.
How is this different then scripting my entire pipeline in bash for example, and then having different platforms run those scripts for me?
What's special about dagger in that regard, other than the fact you get other languages in an SDK?
I think the biggest difference would be that Dagger runs everything in containers, so all dependency management is handled that way. So you could probably achieve something similar using Bash and Docker. But then you have both Bash scripts and Dockerfiles to manage, and I think a big part of the Dagger USP is that you can work within whatever language you wrote the rest of your app in. So if you write a Go application, you can keep using Go for the pipeline definitions, instead of adding Bash and Docker to the mix. And add to that many optimizations and guardrails that Dagger adds, for example enhanced cache management and traces, and it starts to look pretty compelling I think.
Hi All! Jeremy from Dagger here. I've posted links to these repos on here a couple of times, but the comments have been deleted, perhaps by an automated system. I'll work to get them into the Dagger examples repo on GitHub this week. Thanks!
Great job and an awesome demo!
I would also like to stress that we need that demo git repository code because dagger documentation doesn't have that yet.
:plz: