#non-zenith code calling zenith code
1 messages · Page 1 of 1 (latest)
I feel stupid for asking this. Isn't that the primary use case? Like how does a module fit into the ecosystem. Am I using this the wrong way?
Once Zenith is rolled out, the primary mode of using Dagger (we think) will be calling functions from the CLI
Embedding dagger in other tools is a wildcard: would be awesome if it ends up driving tons of usage, bring great partnerships etc. But we can’t count on it in advance, we can only make sure it works great and see what use cases pop up.
oh, so dagger call would be how people do things? 🤔 I thought that was a interesting debugging tool.
Being restricted to only people advanced enough to develop their own custom tool, is the distribution problem Zenith aims to solve in the first place: there just aren’t enough Darrens
Yeah dagger call is probably not polished enough. But dagger up, dagger shell, dagger download, and hopefully soon, dagger print should get really good
same general idea
yeah, i get it. Right now dagger entrypoing for users seems to be from their own code. They write the main. I didn't realize you were switching to a model where you are the entrypoint
then you wrap that in a shell script, makefile or github action
well I like that.
right - we have to, to avoid remaining niche
but at the same time we also want to support embedding in your own tool, there are not as many of those use cases but they tend to be very cool 🙂
i totally get it. Well I'm excited to see where the new CLI UX goes. I really digging modules. I definitely see this an something I would use. Probably not the tagline you want, but for me it's basically portable github actions that don't suck.
there's something very cool about zenith. It's like portable functions. Like docker containers put the crappy world of log lived processes into a nice package and zenith does the same with functions. I love things that allow me to take garbage and put it in a nice reusable unit.
We’re still struggling with how to position the whole thing tbh. CI, not CI… etc
yeah, it's hard. We struggle with a similar thing. Solving a real problem, in a cool way, but don't know how to explain it. And for us most pitches people have done before and failed to meet expectations. It too deceptively simple. Right now the two things we are focusing on is portability and cost. That seems to reasonate still.
I love things that allow me to take garbage and put it in a nice reusable unit.
LOL, that seems to be our specialty 😂
it's the secret to innovation
We have a super cool demo that tells the story from the zenith perspective if you're going to be at kubecon and have some time to check it out 🙂
I'll definitely stop by
maybe we should add an acorn module to the rotation 😇
I will do it. I'm looking to port our entire acorn image build system to dagger. I really want to talk to you guys a bit more indepth about this.
cc @honest bluff who will be in Chicago as well
Let's do it!!
I have a strong interest in this as well. It would help our tool tremendously.
This is something I requested as well, and @rugged hollow said that it wouldn't be too hard to implement. (calling zenith from non-zenith that is)