#Is a private "Daggerverse" Possible

1 messages · Page 1 of 1 (latest)

eternal thicket
#

When running a dagger module call e.g.
dagger -m github.com/shykes/daggerverse/hello@v0.3.0 call hello
my understanding is that this isn't actually querying github.com directly, but the URL (github.com/shykes/daggerverse/hello@v0.3.0) is the module reference on the Daggerverse.
Is that correct?
Does it then redirect to the URL in the module definition on Daggerverse to get the module code?

So if my understand is correct I can't currently use this mechanism to run Dagger Modules from a private repo (that I wouldn't want to publish on Daggerverse for intellectual property reasons).

Is there a way I could setup a private repo of modules that can be called with the module argument, or would I have to implement this differently?

craggy agate
#

Hey!

my understanding is that this isn't actually querying github.com directly, but the URL (github.com/shykes/daggerverse/hello@v0.3.0) is the module reference on the Daggerverse.
Is that correct?

it's actually querying github.com directly. https://daggerverse.dev is only a module index, it only stores metadata about the modules and serves as a search engine, it's not used at all by the dagger CLI or the engine

#

So if my understand is correct I can't currently use this mechanism to run Dagger Modules from a private repo (that I wouldn't want to publish on Daggerverse for intellectual property reasons).

pulling modules from private repositories is not currently supported but it'll be very very soon. We tried to include it for v0.12 but we couldn't make it. You can follow this PR for updates https://github.com/dagger/dagger/pull/7708

GitHub

WIP implementation of private Git support (works, just not with a generic / nice ref yet)
This is rebased on top of #7663, which adds integration tests and fixes some of the VCS logic.
Core changes...