burnt wyvern
Hey all!
I'm wondering if there are best practices around the structure of daggerverse repos.
Looking around, the current convention seems to have a flat structure with every Dagger module in a directory like this:
daggerverse
├── mod1
│ └── dagger.json
├── mod2
│ └── dagger.json
├── mod3
│ └── dagger.json
├── prjA
│ └── dagger.json
└── prjB
└── dagger.json
However, it seems like two kinds of modules are arising on our end:
- Low-level building-block modules that create a library of reusable components (mod* in this example)
- High-level workflow modules that implement our business logic to build/test/publish etc.
As our list of modules grows, we are thinking about categorizing them into subfolders. For example:
daggerverse
├── lib
│ ├── mod1
│ │ └── dagger.json
│ ├── mod2
│ │ └── dagger.json
│ └── mod3
│ └── dagger.json
├── prjA
│ └── dagger.json
└── prjB
└── dagger.json
or
daggerverse
├── lib
│ ├── mod1
│ │ └── dagger.json
│ ├── mod2
│ │ └── dagger.json
│ └── mod3
│ └── dagger.json
└── project
├── prjA
│ └── dagger.json
└── prjB
└── dagger.json
As anyone found better success with a particular structure?
Are we potentially digging a hole for ourselves by adding some layers?
timid mesa