#Daggerverse
1 messages · Page 1 of 1 (latest)
The thing about dagger/dagger/modules is that even though anyone can use them, they're mostly serving the dagger pipelines and I'm not sure how much thought is currently being put on keeping them generic enough. I.e: I see that the gha module has a scripts folder (https://github.com/dagger/dagger/tree/main/modules/gha/scripts) with a bunch of things that are very dagger engine build specific.
seems like we could use a robots.txt for dagger modules.
silently pinging @abstract ruin and @left meadow
They're meant to be reusable, including gha. When my gha module was absorbed into dagger/dagger it was also refactored. But I think it remained equally reusable.
To me dagger/dagger/modules is an intermediary step towards a stdlib, like an incubator
I tried to use the go module but found stuff that's kind of specific to dagger pipeline like this - https://github.com/dagger/dagger/blob/main/modules/go/main.go#L370.
So there are things that dont' necessarily translate to being generic.
not by design - I wrote the first version of that module and made sure it was not dagger-specific. It might have been changed after. If it hurts reusability I consider it a bug
@summer sundial at a quick glance I don't see what's specific to dagger there
seems cleanly generic to me? but if we missed something we'll fix it
When I ran it against my app, the ListPackages didn't produce results. I didn't dig into it deep though. Maybe we have a non-standard folder structure? I ended up going with the featured go module in daggerverse. I can try test this again and see if I can spot anything specific.
👀 why is this not generic?
the ./app there is for the container defined here https://github.com/dagger/dagger/blob/main/modules/go/main.go#L93
An open-source runtime for composable workflows. Great for AI agents and CI/CD. - dagger/dagger
yeah it's weird. I had to copy and change the code because I can't directly use the wolfi module which in using the alpine module which has the registry hardcoded to docker.io. So i replaced Wolfi() with Container().From(".../alpine:3"). Also, our project doesn't produce a binary. It's a framework module so maybe that affected this too. As I said, I didn't have a ton of time to dive deep. Mark's daggerverse go module fit better for my needs so I went with that.