Replies: 2 comments
-
I am definitely a big proponent of the "daggerverse repo". I like that we're experimenting with different models; and I like that we can accomodate them all; but definitely think the daggerverse repo model is superior, and will gain popularity. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I agree with Solomon. In fact that's a model we use today with our Jenkins
shared libraries. All the functions are in the same repo. I think that's
will suit companies who want to maintain a single repo for all their
internal dagger modules.
Honestly with that, both models are supported as you could technically have
a single module per repo if you want.
…On Fri, Sep 22, 2023, 17:09 Solomon Hykes ***@***.***> wrote:
I am definitely a big proponent of the "daggerverse repo". I like that
we're experimenting with different models; and I like that we can
accomodate them all; but definitely think the daggerverse repo model is
superior, and will gain popularity.
—
Reply to this email directly, view it on GitHub
<#5818 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACYJ6FRNRPE5RJUNRZ7HDM3X3YEAXANCNFSM6AAAAAA5DSSCBI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There are experiments happening around the repos structure for Zenith modules.
A couple of popular patterns are:
https://github.com/shykes/daggerverse
https://github.com/kpenfound/dagger-modules
with many modules under one repo
and
https://github.com/jpadams/dagger-module-trivy
with one module per repo
1 repo has many modules
PRO
CON
1 repo has 1 module
PRO
CON
Beta Was this translation helpful? Give feedback.
All reactions