text stringlengths 0 2.29k |
|---|
**Jerod Santo:** Also happy about that... |
**Gerhard Lazu:** No more CUE... No more makefiles. |
**Jerod Santo:** I was going to learn CUE. I don't have to learn CUE now. |
**Gerhard Lazu:** Exactly. You have to learn Go... |
**Jerod Santo:** No more makefiles. Zero makefiles. |
**Gerhard Lazu:** Yup. |
**Jerod Santo:** Now you got me. |
**Gerhard Lazu:** Yeah. The top one went, and the others will disappear as well from the subdirectories when we finish the migration. So there's no more top makefile. |
**Jerod Santo:** Okay, so where do I go? I look for a .go file, it's in there somewhere, to look at what's going on. |
**Gerhard Lazu:** So everything Dagger-related is in mage files. |
**Jerod Santo:** Okay. And mage is Go's version of make, or rake, or like a task runner thing? |
**Gerhard Lazu:** It's just like to invoke things, just to have like different entry points... So for example, right now we have three entry points. The first entry point is the Dagger version 0.1 legacy, where we can run the old pipeline. 0.1 is 0.3. That was one PR. So we had PR 446, where we run the Dagger 0.1 pipel... |
There's also a new - again, this is like image, so it exposes... I mean, you can think of those like subcommands. It all bundles up in a binary, and it has like different subcommands. And if you don't provide any command, it'll show you "Hey, you can run these things." That's in essence what it is. |
So we have image is a namespace runtime. So we can now build the runtime image using Dagger version 0.3. Not only build it, but also publish it to GHCR. And that is pull request 450. So now we are building and publishing the Changelog runtime image to GitHub Actions. Sorry, using GitHub Actions, or within GitHub Action... |
**Jerod Santo:** So GHCR - that's GitHub's deal, right? That's their registry. |
**Gerhard Lazu:** GitHub's Container Registry. That's it. |
**Jerod Santo:** Okay. I haven't used this before, so I'm a newb here. I'm used to Docker Hub. So this is like GitHub's version. |
**Gerhard Lazu:** Exactly. |
**Jerod Santo:** Oh, I'm looking at this Changelog runtime, and it has an emoji next to it... |
**Gerhard Lazu:** How beautiful is that? \[laughter\] |
**Jerod Santo:** Gerhard got some emoji in there... So you're already talking my language... |
**Gerhard Lazu:** Elixir version 1.14.2, so you see the description... I mean, you can see the version that we use in the actual tag... And that's what we're using in production right now. That went out this weekend. |
**Jerod Santo:** Okay. |
**Gerhard Lazu:** So we're using that runtime image. |
**Jerod Santo:** Okay. And this was built via Dagger, inside GitHub Actions? |
**Gerhard Lazu:** That's right. Yup. |
**Jerod Santo:** Okay. |
**Gerhard Lazu:** And you can also run it locally, if you want. |
**Jerod Santo:** When you run it locally, are you running it inside Dagger? What's the terminology here? |
**Gerhard Lazu:** \[26:04\] Okay, so you're running it -- so it runs Go on the outside, it provisions a Dagger engine inside Docker... Because if you have Docker, it needs to provision like the brains, if you wish, of where things will run... So by default, if you have Docker, it knows how to provision itself. When the... |
**Jerod Santo:** 'build. Elixir(). WithAptPackages(). WithGit(). WithImagemagick().' So this is like a chain of function calls that you've named nicely... |
**Gerhard Lazu:** That's it. And you can mix and match them in whichever way you want. So when, for example, we convert the rest of our pipeline to Dagger 0.3, we'll do build, we'll take Elixir, with packages, and whatever else we want. And when we want to publish the image, we can chain, again, the function calls howe... |
**Jerod Santo:** I was just going to ask that, because I'm looking at line 16, it says elixir version equals, and then it's a string, 1.14.2. |
**Gerhard Lazu:** That's it. |
**Jerod Santo:** Can I just change that string? |
**Gerhard Lazu:** That's it. |
**Jerod Santo:** And that's it?! |
**Gerhard Lazu:** That's it. Change the string, commit and push, and the CI will take care of the rest. |
**Jerod Santo:** Whooo-weee!! Now we're talking. |
**Gerhard Lazu:** Oh yeah, baby. |
**Jerod Santo:** I've asked you for this for years. Like, can I go to one place in the code and just change the version, and it'll be done? |
**Gerhard Lazu:** That's it. And there's like more and more stuff that we can add on top of that. For example, we can change the local files. You know, we still have, in contribute.md, if you go that -- by the way, that was updated as well to tell you how you change things. So that was updated to reference the new file... |
**Jerod Santo:** Meaning it's only in the readme? Like, you could have it in the readme only? |
**Gerhard Lazu:** Meaning that it will only be in the image go. That's it. When you bump it into image go, and the pipeline runs, it will update all the other places. |
**Jerod Santo:** Oh, it'll update the readme for you. |
**Gerhard Lazu:** Exactly. |
**Jerod Santo:** I was gonna say, it'd be crazy if you actually just had that version in the readme, and it read it in the image go... Which you probably could do, because it's Go code. |
**Gerhard Lazu:** It could do that. Yeah, it could do that. |
**Jerod Santo:** That doesn't sound smart, but it just would be interesting. |
**Gerhard Lazu:** \[29:45\] Yeah, no. You want it to be in code. You want it in code. And not to mention that when it's in code, by the way, we can have -- again, we still need to figure this part out, I suppose... But we could have things that automatically bump it. When a new version comes out, it bumps it in code, t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.