daggerverse best practices? | Dagger | Page 1

stoic tiger Jun 2, 2024, 2:37 PM

#

i see a lot of repos with 1 git repo called daggerverse, but the git repo has a bunch of modules. Is this not weird?

#

80% of the modules is via a repo someone named daggerverse.

#

just thinking about, contributrions and workflows, and triggers.

#

From the docs...

"Some like to publish each module as a dedicated repository; others like to organize all their modules together, with the git repository acting as a "catalog". These repositories are often named "daggerverse" by convention."

#

So no best practice, but a convention to squash independant modules into 1 repo? It feels odd to me

#

Just trying to think long term, if you have vendors who will author their own modules, say a big company. this doesnt seem too sane.

But i like the idea of the catalogue but not to host the specific modules

#

https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types

#

It reminds me of this

late tiger Jun 2, 2024, 3:10 PM

#

Just my POV:

There are many many modules to write, creating a repo for each and every one is toilsome
Naturally dependencies between my modules will emerge, it's convenient to just keep them all in the same repo, rather than bumping and pushing everywhere all the time
Modules can still be independently versioned while living in the same repo by putting the subpath in the semver tag (./apko tag is apko/v1.2.3), so versioning works just as well as with separate repos

But the choice is of course up to the module author. If you're a vendor and you want to put an individual module on more of a "stage" to highlight your Dagger integration, that makes total sense too.

Biggest downside so far is typing daggerverse really. Haven't run into any issues besides that. Maybe we can have shorthand one day.

stoic tiger Jun 2, 2024, 6:05 PM

#

could the dagger.json be expanded? something like "expose: true" or "daggerverse: true"?

So the only way to have a module published is via the daggerverse method?

Also 2nd thought, git submodules... could one use private module repo, and then crate a daggerverse repo of git submodules

late tiger Jun 2, 2024, 6:38 PM

#

Not sure what you mean by the Daggerverse method - you don't need to follow that pattern for it to show up at https://daggeverse.dev, it's just a naming convention for the monorepo style. Here's one that has its own repo instead: https://daggerverse.dev/mod/github.com/shykes/clickhouse@8a8ceca32643776f8e60fbea2122265b8b4fdd41

stoic tiger Jun 2, 2024, 7:14 PM

#

#

Okay, i misunderstood this

#

its just github is needed, but the other part is not needed

late tiger Jun 2, 2024, 7:16 PM

#

Oh yeah - we're fixing that soon, @onyx compass is working on it

stoic tiger Jun 2, 2024, 7:16 PM

#

I see now on the daggerverse website, ignore me

#daggerverse best practices?