text stringlengths 0 2.67k |
|---|
**Autumn Nash:** You mentioned that you contributed to other open source projects. What other open source projects do |
you contribute to? |
**Matti Ranta:** Of course, yeah. I've contributed to drone.io, the CI/CD. There's a fork of it called Woodpecker that I've also contributed to. I maintain several Golang libraries for automation. Probably the biggest thing outside of Gitea that I do is something called xgo, that lets you cross-compile Golang binaries ... |
**Justin Garrison:** I need a link. I was trying to look it up. I've found one that was archived... But literally, I was trying to rebuild some software for i686, to run on an emulator that runs on my iPad. But yeah, that architecture is -- what they emulate there is not what I normally have on my desktop, and I think ... |
\[47:55\] The decision you have for the CI/CD, when you implemented that, and being compatible with GitHub Actions - did that impact your architecture or how you implemented it? Because it's very different than Drone, and different than GitLab and the other ones. So were you basically rebuilding or recreating GitHub Ac... |
**Matti Ranta:** Yeah, so there's a few components to our Gitea actions. One of the biggest components is already solved, and it's using the Act project, which is like just being able to execute GitHub Actions on your command line. It will execute it all in a Docker container locally. But what we wanted to do was we wa... |
So there were some decisions architecturally that we had to make, like how it was built, because with Drone, previous to version 2, it used gRPC on a different port. And Woodpecker does the same. And even like sending updates to the user, they did server-side events, which is deprecated in the browsers, and don't play ... |
So we're still doing gRPC communication between the server and runner, but we're feeding it through our router itself, instead of having a different listener on a different port. It's just talking through our Chi router, to be able to call those actions, and having those long-lived connections with the runner to be abl... |
**Justin Garrison:** I run a router behind my firewall; it connects to my Gitea instance over gRPC, and my runner is basically running the Act command as a daemon, listening for those jobs \[unintelligible 00:50:18.27\] the Act runner is the actual piece that does the GitHub Action parsing, and say like "Okay, I know h... |
**Matti Ranta:** Exactly, yeah. And we do have to have some on the server as well, because we need to know in advance which actions to call... Because if it's like a push \[unintelligible 00:50:37.29\] comment, we need to put that into our pipeline of like "Hey, here's this new task that a runner needs to pick up." And... |
**Justin Garrison:** I just want to go all the way back to the beginning here, of wrapping this up with like -- Gitea started as this very simple Git server web interface for Git, basically. I can push things to a website, and then it stores files on disk. That grew into having a lot of other features, and you wanted t... |
**Matti Ranta:** \[52:19\] Yeah, pretty much. Yeah. |
**Justin Garrison:** So you have some autoscaling groups that are just like "Hey, these need to autoscale if we have too many requests, or we're hitting a limit, or something." Cycle them out, do those upgrades, all that stuff just happens generally as an autoscaling group can do. And then you also get the benefits of ... |
**Matti Ranta:** And then also another important part of the flagship is being able to dogfood our own project. We have most of our stuff there. One remaining thing is just, with eight years of history, 30,000 issues and pull requests, and a countless number of comments, and reactions, and labels, and just getting that... |
**Justin Garrison:** Yeah, yeah. I mean, the metadata in process is the real tech debt. Those are the things that are really actually hard to migrate. A language or a framework or whatever - yeah, you've gotta invest the time. But if you're in a different mindset of how you manage the software and release the software,... |
**Matti Ranta:** Yeah. And dogfooding is also incredibly important to like even see not just like maintaining that infrastructure, but using it on a day to day, and feeding back into the development process as well. |
**Justin Garrison:** Well, thanks for bringing us down that trip of what Gitea has gone through, and kind of what it's used for... Because that's fascinating, just to see -- as someone who's run a couple of these things internally, I've never had to scale them beyond a couple hundred users, and in most cases that's lik... |
**Matti Ranta:** Thanks. Yeah. |
**Autumn Nash:** Also, it's hard to store your own code... So I can't imagine doing all of the planning to store other people's code, and not knowing the constraints that you're going to be under. That's a lot of planning, and design, and figuring out... |
**Justin Garrison:** Yeah, once you're dependent on your own software, your requirements change. |
**Autumn Nash:** Yes. I can't even imagine. It'll be a wild ride. You will learn a lot, for sure. |
**Matti Ranta:** Yeah. And a big shout out to all the people who've given me advice and helped out with with this infrastructure. Because yeah, it's -- like, I'm typing in commands, but there's a ton of people in our community that are giving feedback, and like "Hey, this is a pattern that I've used before", and all th... |
**Autumn Nash:** That's awesome. Community is the best part of open source. |
**Justin Garrison:** Thank you so much, Matti, for coming on and explaining it. We will have links to some of the stuff we talked about in the show notes, and we'll talk to you again soon. |
**Matti Ranta:** Awesom. Thanks so much. |
**Break**: \[56:35\] |
**Justin Garrison:** Thank you so much, Matti, for coming on the show and talking to us all about Gitea, and the infrastructure behind it, and kind of the challenges you faced throughout running that. That's really fascinating just to see what a public website -- that's what this podcast is all about. I want to talk to... |
**Autumn Nash:** Also, it's really interesting just the idea of -- things are kind of getting weird right now, with what happens when other people host your things, or how we were saying with like cars all of a sudden needing... Like, you're paying monthly for heated seats, or just - I don't know, the world's in a weir... |
**Justin Garrison:** You're really hung up on those heated seats, aren't you? |
**Autumn Nash:** Dude, how does that happen? How do you own a car and then they're like "Oh, by the way..." I bought my car, and then I had a Toyota app, and it was like free... And then all of a sudden they were like "You have to pay $12 a month to start your car." And I was like "I thought once you bought a self-star... |
**Justin Garrison:** I bought my first new car in 2020, it was a Subaru... And I like it. But yeah, there was a subscription to be able to start the car remotely, and it had an app, yeah. |
**Autumn Nash:** That's wild to me. I feel like if they make it harder and harder to be financially smart, because you can't just buy things and pay it off, because now they're like -- |
**Justin Garrison:** You can't own things, right? |
**Autumn Nash:** Yeah. |
**Justin Garrison:** There's no ownership. You're like "I have this weird partnership with my car company." |
**Autumn Nash:** Yes. Like, I get that you have to maintain an app and stuff and all that good stuff, but it is wild, the way that they've changed -- |
**Justin Garrison:** But we used to have remote starters on cars. |
**Autumn Nash:** That's what I'm saying. |
**Justin Garrison:** I installed remote starters on cars back in the day, and it was just a button on my remote, and it would start the car. And you don't have to have a web service. |
**Autumn Nash:** Yeah. You pay like $1,000 and you get this remote key, and then you start your car. And then also, do you know how much it sucks when your Wi-Fi is messed up or something, and you can't start your car, and then you have to like switch back to -- that's wild. |
**Justin Garrison:** My first four cars cost $1,000, each one. I would buy -- it was $1,000, I would fix it up, I would sell it for $1,000, and I'd buy the next one. And I did that for four cars, and it was great. |
**Autumn Nash:** The price of cars now is just wild. But I think that all this is gonna change the way that we have finances, too. Back in the day when I started art school you would buy a version of Adobe Photoshop, usually with like student loans or whatever, your first money, and then you'd use it until you had a fe... |
**Justin Garrison:** Hey, if you want to own some software, check out Gitea, right? I mean that was the whole -- that's like literally this model. |
**Autumn Nash:** Yeah, that's what I'm saying. No, but it was almost a solution that I know we needed. You never know how that's going to -- like, maybe that makes things better, or I don't know. Something that we didn't know we needed. |
**Justin Garrison:** There is definitely value in knowing what is good enough, right? Because you don't need Photoshop, whatever version. Like, I have the old Photoshop, and I would use that one. And it was good enough for my skill level and what I needed out of the tool. |
**Autumn Nash:** Also it's wild that you can get Photoshop on your phone now, for free. |
**Justin Garrison:** Sure. I bought Procreate on my iPad. I love Procreate. It's a great drawing app, and I paid the $20 for it, and I own it. |
**Autumn Nash:** And they have like Canva, too. So it's just wild -- I do think that when some things get kind of crappy for customers, it's always a good time for innovation. Another company will pop up and be a solution for a problem. So I guess there's that too, but it's just... It's wild. You can't really pay thing... |
**Justin Garrison:** Yup. Life costs money. Anyway... |
**Autumn Nash:** So much money...! |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.