#Pipeline functions questions
1 messages · Page 1 of 1 (latest)
Hi 👋 a bunch of folks traveling today, but if you drop questions here we can answer async
Wait are you the person who makes the videos on the dagger channel?
Haha that’s awesome
So im looking into the dagger documentation pretty much every day to get started but i got confused on importing dagger/dagger.io in my main file with my main function compared to doing dagger init —sdk=go where there’s the sdk included through the other folders to make use of Dagger
So when I do that I don’t see the import dagger/dagger.io in the main.go file?
hey @faint kiln! I'm in for a quick audio chat here if that helps getting you blocked / giving clarification on any dagger specific topic
it's basically two ways of using Dagger. It's explained here: https://docs.dagger.io/api/sdk
You can pretty much use "Modules and Function" or "Custom applications".
Modules and functions is generally what works for most users to deliver a great Dagger experience. "Custom applications" is a more advanced approach where the module primitives might not be necessary while still being able to make use of some Dagger internals
Oh is there any room for audio chats?
Thank you so much for this
I noticed you can use the same functions in both cases? What’s the customizing aspect here?
it's the same underlying Dagger core API. What changes is that by using Modules and functions you have another set of powerful primitives that provides a better composable and organizational model for your software workflows. There's more information about this in our Functions press release from last year (https://dagger.io/blog/introducing-dagger-functions)
Oh so for custom applications, you can’t really access those functions that’s shown in the go sdk documentation?