#I have a large monorepo with a lot of
1 messages · Page 1 of 1 (latest)
What programming language(s) are you using? What monorepo software are you using?
I'm asking, because I'm wondering why the build steps are so different across packages/ applications. Can you give some examples of the differences?
Also, you note "blueprint". Do you mean a Dagger module?
I don't use any monorepo software and this isn't even a traditional software project.
It's a set of educational materials for different topics. Many of them use container images, but the content of those images differ. The content itself is in markdown, so the rest of the pipeline is uniform.
By blueprint I mean Dagger blueprint.
Here is an example: a kubernetes tutorial, using two container images.
Rendering the content is the same for all. Since it contains two images, those need to be built and pushed when releasing.
In addition, image specific tests need to pass.
Honestly, I'd be okay with something like an abstraction that requires a module using a blueprint to implement a certain function with certain outputs.
By blueprint I mean Dagger blueprint.
I googled for Dagger blueprint and didn't find anything. Can you point me to a reference or explain what it is?
Can you also explain what it is you are doing a bit more in detail? I guess building means rendering content? It's hard for me to visualize how this could work.
Not sure if blueprints are documented yet. Looks like they've been removed from the documentation.
They are basically "parent" modules for your root module inheriting functions.
- https://docs.dagger.io/getting-started/quickstarts/toolchain/#install-a-toolchain
- https://github.com/kpenfound/blueprints/tree/main?tab=readme-ov-file
Right now it works by running a bunch of shell scripts. But the steps are basically:
- Render markdown templates
- Build container images (if any)
- Push content to iximiuz labs
- Run various tests (eg. to make sure the container image has everything, the scripts in the content work as expected, etc)