Gerhard

Oh, man, I can see me and Jared getting together here because we need to figure out how to purge these correctly and how to do this from the app. So the application itself will know which are the pipedream or pipely instances and will send these purge requests. And we're looking at the fly IO machines, like we're running the same network, we can discover them, we have DNS.

Oh, man, I can see me and Jared getting together here because we need to figure out how to purge these correctly and how to do this from the app. So the application itself will know which are the pipedream or pipely instances and will send these purge requests. And we're looking at the fly IO machines, like we're running the same network, we can discover them, we have DNS.

So a lot of the building blocks are there, but this is where the application needs to come together with the actual CDN runtime, in this case fly.io, to implement this purge via OBAN and like how we do things. So we don't introduce a third or an extra service. And then adding the add redirects, this is really easy because it's just basically adding more VCL config.

So a lot of the building blocks are there, but this is where the application needs to come together with the actual CDN runtime, in this case fly.io, to implement this purge via OBAN and like how we do things. So we don't introduce a third or an extra service. And then adding the add redirects, this is really easy because it's just basically adding more VCL config.

Most of it is copy paste, maybe a few adjustments. So it's very feasible. And we're talking, I would say maybe weeks of work in total, but weeks of work spread over a long period of time. That's what's hard. Like the time on my part, you know, have the time to actually go through all these things, but I can make this my focus. That is a possibility.

Most of it is copy paste, maybe a few adjustments. So it's very feasible. And we're talking, I would say maybe weeks of work in total, but weeks of work spread over a long period of time. That's what's hard. Like the time on my part, you know, have the time to actually go through all these things, but I can make this my focus. That is a possibility.

Yeah, I think Pipely is a good idea. A new city and he's born. I mean, we can see... The journey that we've been on right since January, that's when he started talking about was like the first Kaizen. This whole year. Yeah. So, you know, we have been taking all these small steps towards it. We were uncertain for a long time. You know, is this real? Should we really do this? Is it a good idea?

Yeah, I think Pipely is a good idea. A new city and he's born. I mean, we can see... The journey that we've been on right since January, that's when he started talking about was like the first Kaizen. This whole year. Yeah. So, you know, we have been taking all these small steps towards it. We were uncertain for a long time. You know, is this real? Should we really do this? Is it a good idea?

So we weren't like all in to begin with. And I think, I think that we are getting close to being all in. as in let's go for this, let's implement it, let's see how it would work in practice. Most of the problem space, I think we have discovered it. We know what are the big items, not the actual implementation.

So we weren't like all in to begin with. And I think, I think that we are getting close to being all in. as in let's go for this, let's implement it, let's see how it would work in practice. Most of the problem space, I think we have discovered it. We know what are the big items, not the actual implementation.

But this seems a lot more feasible and a lot more realistic than it was in January, for example, when it was just a question. And I think now it's not like we're building it. It's like we are, I would say, maybe a third way through, maybe a quarter through, something along those lines. And there are still challenges around, for example, like the TLS termination. That is a big one.

But this seems a lot more feasible and a lot more realistic than it was in January, for example, when it was just a question. And I think now it's not like we're building it. It's like we are, I would say, maybe a third way through, maybe a quarter through, something along those lines. And there are still challenges around, for example, like the TLS termination. That is a big one.

And that means that we can only proxy or forward request the origins. They have to be HTTP. The backends, as Manj calls them, have to be HTTP. I think that's not a problem for us. It's not a problem in the context of Fly because everything is running like we have a private network. So all the endpoints are HTTP and they're private. No one can connect to them. So I think that makes sense.

And that means that we can only proxy or forward request the origins. They have to be HTTP. The backends, as Manj calls them, have to be HTTP. I think that's not a problem for us. It's not a problem in the context of Fly because everything is running like we have a private network. So all the endpoints are HTTP and they're private. No one can connect to them. So I think that makes sense.

R2 can also be public. It's not a problem. And when it comes to pushing logs, that's the one thing which I don't know. But honestly, I don't see Varnish being the thing which will push the logs anyways. What I would use that I've been using for years is vector.dev. Vector.dev is a great tool for sending logs and metrics or anything like that anywhere.

R2 can also be public. It's not a problem. And when it comes to pushing logs, that's the one thing which I don't know. But honestly, I don't see Varnish being the thing which will push the logs anyways. What I would use that I've been using for years is vector.dev. Vector.dev is a great tool for sending logs and metrics or anything like that anywhere.

Datadog acquired them since I've been using Vector. But it's all very simple and straightforward. And even to this day, I use it in the context and we use it in the context of the Docker infrastructure. This is a very important component. And other teams are using it in their own infrastructures that we are collaborating with.

Datadog acquired them since I've been using Vector. But it's all very simple and straightforward. And even to this day, I use it in the context and we use it in the context of the Docker infrastructure. This is a very important component. And other teams are using it in their own infrastructures that we are collaborating with.

So vector seems to be the piece to pick and the tool to use in this context. Again, written in Rust, super performant, nice CLI, has a lot of things. So I think the building blocks are getting clear. Just a matter of going for it. New beginning, new year. I think that could be the focus. Let's go for it, man. Let's do it, right?

So vector seems to be the piece to pick and the tool to use in this context. Again, written in Rust, super performant, nice CLI, has a lot of things. So I think the building blocks are getting clear. Just a matter of going for it. New beginning, new year. I think that could be the focus. Let's go for it, man. Let's do it, right?