Gerhard Lazu
๐ค SpeakerAppearances Over Time
Podcast Appearances
The difference is that was all using Dagger and containers and, you know, it was, I mean, have you used it, Jared, apart from when we've done it?
The difference is that was all using Dagger and containers and, you know, it was, I mean, have you used it, Jared, apart from when we've done it?
There you go. Adam, have you ever run Dagger? Never. In the three years that we've had it? Never. Not one time. There you go. How many times did you have to install things locally for you to be able to develop changelog in the last three years?
There you go. Adam, have you ever run Dagger? Never. In the three years that we've had it? Never. Not one time. There you go. How many times did you have to install things locally for you to be able to develop changelog in the last three years?
So Adam might be more excited about this than I am. Pull request 5 to 1. I mean, even you, Jared, if you want to try it. I mean, if you do dry run, it has a dry run option, by the way. It won't apply anything, but it will show you all the commands that would run if you were to run them yourself, for example. And there may be quite a lot of stuff, right, when you look at it that way.
So Adam might be more excited about this than I am. Pull request 5 to 1. I mean, even you, Jared, if you want to try it. I mean, if you do dry run, it has a dry run option, by the way. It won't apply anything, but it will show you all the commands that would run if you were to run them yourself, for example. And there may be quite a lot of stuff, right, when you look at it that way.
But it's a good way to understand, like, if you were to do this locally, and if you were to configure all these things, what would it do without actually doing it? So I tried it on a brand new Mac, and I think that's the recording that I have on that pull request.
But it's a good way to understand, like, if you were to do this locally, and if you were to configure all these things, what would it do without actually doing it? So I tried it on a brand new Mac, and I think that's the recording that I have on that pull request.
That's very, very... I've been waiting for a good reason to upgrade, you know? There you go. And honestly, within five minutes, depending on your internet connection, everything should be set up. Everything is local, the Postgres, everything.
That's very, very... I've been waiting for a good reason to upgrade, you know? There you go. And honestly, within five minutes, depending on your internet connection, everything should be set up. Everything is local, the Postgres, everything.
What we don't yet have, and I think this is where we're working towards, is how do we, first of all, cleanse the data so that contributors can load a type of data locally. But I think that's like a follow-up. First of all, we want Jared to be able to do this with a single command, refresh his local data. And after I have this, the bulk of the work done, this step is really simple. How simple?
What we don't yet have, and I think this is where we're working towards, is how do we, first of all, cleanse the data so that contributors can load a type of data locally. But I think that's like a follow-up. First of all, we want Jared to be able to do this with a single command, refresh his local data. And after I have this, the bulk of the work done, this step is really simple. How simple?
Maybe half an hour at most. That's what I'm thinking. So not much.
Maybe half an hour at most. That's what I'm thinking. So not much.
I'm just curious about that change. so i mentioned it in one of the comments when i committed basically when i was installing it via asdf the problem with was with icu4c i just couldn't compile postgres from asdf correctly and since then in homebrew we can now install postgres at 16. so you can specify which major version which was not possible i think two years ago when i did this initially
I'm just curious about that change. so i mentioned it in one of the comments when i committed basically when i was installing it via asdf the problem with was with icu4c i just couldn't compile postgres from asdf correctly and since then in homebrew we can now install postgres at 16. so you can specify which major version which was not possible i think two years ago when i did this initially
so there is that now let's see let's see where this goes i'm excited about this if anyone tries it let us know how it goes for you uh if you want to contribute a changelog like how far does it get and by the way i tested this on linux as well the easiest way there's like a something hidden there in the just it's called actions runner what it does is exactly what you think it does it runs
so there is that now let's see let's see where this goes i'm excited about this if anyone tries it let us know how it goes for you uh if you want to contribute a changelog like how far does it get and by the way i tested this on linux as well the easiest way there's like a something hidden there in the just it's called actions runner what it does is exactly what you think it does it runs
a GitHub actions runner locally, for this you need Docker by the way, and it loads all the context of the repository inside of that runner. So that's the beginning of what it would take to reuse this in the context of GitHub actions. And what I'm wondering is, will it be faster than if we use Dagger? That's me challenging the status quo. The answer is either, yes, it is.
a GitHub actions runner locally, for this you need Docker by the way, and it loads all the context of the repository inside of that runner. So that's the beginning of what it would take to reuse this in the context of GitHub actions. And what I'm wondering is, will it be faster than if we use Dagger? That's me challenging the status quo. The answer is either, yes, it is.