Skip to main content
LawHub
Sign In
About LawHub Advantage Exploring Law Preparing for the LSAT Applying to Law School Excel in Law School Charting Your Career Podcast - I Am The Law Law School Trends Sign In
Search

Duece Configalo: Desktop Gigolo

Nov 9, 2025
Listen to this episode

We dive into your configs, the genius moves, the glorious blunders, and everything in between.

Sponsored By:

Support LINUX Unplugged

Links:

Transcript

WEBVTT 00:00:11.759 --> 00:00:16.179 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.479 --> 00:00:17.299 My name is Wes. 00:00:17.679 --> 00:00:18.759 And my name is Brent. 00:00:19.719 --> 00:00:23.899 Hello, gentlemen. Coming up on the show today, it's the sequel to the summer 00:00:23.899 --> 00:00:26.219 blockbuster, Config Confessions. 00:00:26.439 --> 00:00:30.639 We'll dive into your configs, call out the genius moves, the blunders, 00:00:30.819 --> 00:00:31.979 and everything in between. 00:00:32.219 --> 00:00:35.699 And then we'll round it out with some shout outs, some picks, and a lot more. 00:00:35.819 --> 00:00:39.799 There's so much to get into, lots of cool configs. So before we do all of that, 00:00:40.199 --> 00:00:43.079 let's say time-appropriate greetings to our virtual lug. Hello, Mumble Room. 00:00:43.959 --> 00:00:48.559 Hello. Hello. Hey, Chris. Hey, good morning. Good morning, everybody. 00:00:48.879 --> 00:00:52.979 Hello. Thank you for joining us. That is a rockin' Mumble Room, 00:00:52.999 --> 00:00:54.779 and hello up there to the quiet listening, too. 00:00:55.419 --> 00:00:59.979 And a big good morning to our friends at defined.net slash unplugged. 00:01:00.059 --> 00:01:02.859 Go meet Manage Nebula from Defined Networking. 00:01:02.979 --> 00:01:06.359 It's a decentralized VPN built on the Nebula platform. 00:01:06.599 --> 00:01:10.059 This is a project that we love. We've been following it from the very early days. 00:01:10.239 --> 00:01:14.419 It's optimized for speed, simplicity, and if you want, self-hosting. 00:01:14.539 --> 00:01:16.559 It's great for a home lab. It's also great for an enterprise. 00:01:17.039 --> 00:01:21.979 It started in 2017 right there in the thick of it to connect all of Slack's 00:01:21.979 --> 00:01:24.839 global infrastructure. You can imagine the back end Slack must have. 00:01:25.619 --> 00:01:29.199 Wow. And they needed a way to securely connect all the global infrastructure. 00:01:29.359 --> 00:01:32.719 And Nebula was engineered for scale and performance from day one. 00:01:32.719 --> 00:01:36.819 But the thing that I have really learned to appreciate is I've built out and 00:01:36.819 --> 00:01:41.579 used all of these different types of mesh and decentralized VPNs, 00:01:41.639 --> 00:01:45.519 including standard VPNs like WireGuard and way back in the day, OpenVPN and others. 00:01:46.379 --> 00:01:51.039 There's always a tradeoff when it comes to hosted infrastructure, except with Nebula. 00:01:51.439 --> 00:01:55.519 Nebula lets you control the entire thing. They offer a managed platform and 00:01:55.519 --> 00:01:58.279 you can go to a self-hosted platform and you can use a managed platform. 00:01:58.939 --> 00:02:03.199 Everything. It's not like a thing that they're resisting. It's how the product was built. 00:02:03.439 --> 00:02:06.819 And when you are creating your infrastructure, you're building out your infrastructure, 00:02:06.819 --> 00:02:07.859 you want something to last for years. 00:02:08.099 --> 00:02:11.919 I think that really matters, even for an enterprise or a home lab. 00:02:12.039 --> 00:02:15.739 So they align with the way I think about things and the way I want my infrastructure to be built. 00:02:16.640 --> 00:02:19.420 You know, there's other ways you can do it, of course, but I really like the 00:02:19.420 --> 00:02:23.600 way they're building up both the company and the project and the product. 00:02:23.780 --> 00:02:27.460 So check it out at define.net slash unplugged. Redefine your VPN experience. 00:02:27.580 --> 00:02:31.460 Get it for 100 hosts absolutely free and support the show. And if you get to 00:02:31.460 --> 00:02:33.280 the point where it's like, OK, it's time to self-host. 00:02:33.920 --> 00:02:38.580 Nebula is killer. Nobody beats Nebula at that. The resiliency, the robustness. 00:02:38.760 --> 00:02:42.020 And I'm talking mobile device, battery life, all that kind of stuff. 00:02:42.220 --> 00:02:46.320 Nobody beats Nebula. Check it out at defined.net slash unplugged. 00:02:47.080 --> 00:02:51.320 And a big thank you to defined.net for sponsoring this here unplugged program. 00:03:05.620 --> 00:03:10.120 All right. This time it's config confessions in space, the linting. 00:03:10.320 --> 00:03:15.480 And we're back for another round. We asked you to send in your configs, and you've done it. 00:03:16.020 --> 00:03:21.740 And there's a nice batch this week. And if you want to catch the first version, it's episode 634. 00:03:22.440 --> 00:03:26.620 You can find that at linuxunplugged.com slash 634. So here we are. 00:03:27.520 --> 00:03:32.700 Now it's the fall time, and we're back for round two. And I got to start with 00:03:32.700 --> 00:03:35.160 the hardest one, I think, to pronounce here. I'm going to give it a shot. 00:03:35.600 --> 00:03:39.680 Wait, wait. I think before we dive right into the first one, which... 00:03:39.680 --> 00:03:39.980 Okay. 00:03:40.440 --> 00:03:41.720 Impressive. I mean... 00:03:43.231 --> 00:03:47.351 Shouldn't we all confess a little bit? Like, how much have we looked at this stuff? 00:03:47.431 --> 00:03:51.351 Because, you know, people have been sending them in, and then you did the hard 00:03:51.351 --> 00:03:55.511 work to, like, you know, gather them all up and try to find them. 00:03:55.911 --> 00:03:58.591 Brent's been doing the hard work at driving, so I think there might be a little 00:03:58.591 --> 00:04:01.971 confessing around, like, are we looking at these for the first time? 00:04:02.071 --> 00:04:03.931 Do we, you know, let's just be transparent. 00:04:04.531 --> 00:04:07.891 Okay, that's good, that's good. Some of us might be coming in cold, 00:04:08.131 --> 00:04:10.871 like in the snow, you might say, on this. 00:04:12.071 --> 00:04:17.291 Yeah, I did have a chance. I went through, you know, I took in the flavor of 00:04:17.291 --> 00:04:22.211 it, of each one, sort of got in their headspace the best I could and made some 00:04:22.211 --> 00:04:23.331 notes for us to chew through. 00:04:23.511 --> 00:04:30.051 So I think we're going to have a nice combination of clean cold takes and fully 00:04:30.051 --> 00:04:32.451 immersed takes. How do you feel? Does that work? 00:04:32.851 --> 00:04:34.711 That's perfect, yeah. I'm down with that. 00:04:35.511 --> 00:04:39.331 And it's not all Nix. We had some people send in their Ansible configs. 00:04:39.371 --> 00:04:44.351 We had a GUX config sent in. We had some Mac systems sent in. 00:04:44.431 --> 00:04:45.671 So we have some interesting ones. 00:04:46.571 --> 00:04:50.651 And I'm going to say, do you think it's Yeechul? Yeechul is perhaps how you say their name. 00:04:51.031 --> 00:04:54.731 They say, please roast my NixOS config. It's an opinionated Hyperland-based 00:04:54.731 --> 00:04:57.191 config with the same design and productivity-based setup. 00:04:57.531 --> 00:05:01.571 Oh, that's why it got first billing. Yeah, I see this now. 00:05:03.031 --> 00:05:05.431 No, it was chronological. 00:05:06.011 --> 00:05:06.671 It was chronological. 00:05:06.671 --> 00:05:10.131 Cool um so i noticed that uh 00:05:10.131 --> 00:05:13.171 first of all it's it's you know everybody has a 00:05:13.171 --> 00:05:16.031 bit of their own design style uh for 00:05:16.031 --> 00:05:19.071 their repo and each one here starts with a nice 00:05:19.071 --> 00:05:22.571 screenshot of course of fast fetch you got to get the fast fetch screenshot 00:05:22.571 --> 00:05:26.771 in there so that's a classic and then he breaks it all down uh the kernels cache 00:05:26.771 --> 00:05:33.191 eos has support for tpm and uh waybar is in there you got sway sink in there 00:05:33.191 --> 00:05:39.191 kitty neo vim uh and then one of the things that i always like to see, 00:05:40.396 --> 00:05:43.396 Is a get started real quick. And even if it's just for yourself. 00:05:44.216 --> 00:05:48.316 For future you. And they have that right here. A get started real quick script. 00:05:48.536 --> 00:05:50.996 And then a post installation couple of tasks to run. 00:05:51.376 --> 00:05:55.856 So those are my initial. That was my initial impression. I like this screenshot. 00:05:56.276 --> 00:06:01.036 Get started real quick approach. I think it's really good for restoring a system. 00:06:01.036 --> 00:06:02.456 On the quick and things like that. 00:06:02.716 --> 00:06:06.836 And they're actively committing. They got 444 commits. And as just a couple 00:06:06.836 --> 00:06:09.456 of days ago. They were updating their flake. 00:06:10.116 --> 00:06:14.636 How are you missing that? Four days ago was last updated, and there's 444 commits. 00:06:14.736 --> 00:06:16.096 What's going on with four here? I don't know. 00:06:16.816 --> 00:06:17.756 Yeah, you're right. 00:06:17.976 --> 00:06:24.076 But, I mean, you called it out there, but cache EOS kernel. Are you picking up that? 00:06:24.096 --> 00:06:25.116 I'm liking that. I'm liking that. 00:06:25.116 --> 00:06:29.876 So if you go in and take a look at dots slash nix slash boot dot nix, 00:06:29.936 --> 00:06:33.896 you'll see packages.linuxpackages testing commented out. 00:06:34.996 --> 00:06:38.576 Packages.linuxpackages zen, what we're both using, commented out. 00:06:39.076 --> 00:06:43.056 This is telling a story to me because what is left uncommented is linux packages 00:06:43.056 --> 00:06:46.916 underscore cache EOS which I did not realize was just an option that we could 00:06:46.916 --> 00:06:48.916 do so I think we have to try that. 00:06:49.676 --> 00:06:55.916 I do like that programs.nix is an interesting file I think he's turning on some app images I see zoom, 00:06:57.816 --> 00:07:00.876 I'm not quite sure what really threw me for a loop and I kind of wanted to get 00:07:00.876 --> 00:07:05.896 your eyes on this one was I made a note in our notes here, 00:07:07.227 --> 00:07:11.407 Yeah, okay. I think he's installing Pinchflat on his desktop system, 00:07:11.947 --> 00:07:13.527 if I'm understanding this correctly. 00:07:13.807 --> 00:07:17.027 Because in this config, he's also defining his power management, 00:07:17.267 --> 00:07:23.847 his system DNS, and all of the keyboard layout stuff, turning on pipewire. 00:07:24.047 --> 00:07:30.107 So it's kind of like a system configuration, but then he has Pinchflat installed there. 00:07:30.547 --> 00:07:33.047 I love Pinchflat, but on the desktop? 00:07:33.347 --> 00:07:38.527 Well, I see it in services.nix, So it might depend on where that's all sourced. 00:07:38.687 --> 00:07:42.827 Yeah, that's why I couldn't tell for sure. I do think it's a very solid layout. 00:07:43.207 --> 00:07:45.267 A lot of Lua, 40% Lua in there. 00:07:46.247 --> 00:07:49.827 I was like, okay. Some host modules in here too, I'm seeing. 00:07:50.487 --> 00:07:53.747 And it uses a settings.nix file to set the username, the system description, 00:07:53.787 --> 00:07:56.667 and the system type. So like x86 or ARM. 00:07:56.787 --> 00:07:59.847 So he's got one file where he can go in there and just... 00:08:01.218 --> 00:08:02.898 Set that. Sort of as an override. 00:08:03.378 --> 00:08:06.558 I think you're also missing... Did you see the contributor count on this thing? 00:08:06.858 --> 00:08:07.638 Yeah, I know. 00:08:08.358 --> 00:08:10.338 59 people have worked on this. 00:08:11.238 --> 00:08:12.038 It's insane. 00:08:12.738 --> 00:08:13.878 How's he getting 59... 00:08:13.878 --> 00:08:17.218 Like, this is more serious of a Nix config than any of us have put together. 00:08:17.558 --> 00:08:21.398 I know. How's he getting 59 people? That's awesome. 00:08:21.618 --> 00:08:23.198 That's a great question. 00:08:24.318 --> 00:08:28.278 There's a lot to look here in, you know, because you can tell it's, like, really well used. 00:08:28.438 --> 00:08:31.058 I don't know if you noticed, but there's, like, separate Home Manager configs 00:08:31.058 --> 00:08:34.618 for like if you're going with a window manager environment or if you're going 00:08:34.618 --> 00:08:39.358 in a TUI environment, I guess, or there's modules for both anyway. So love to see that. 00:08:39.758 --> 00:08:39.938 Yeah. 00:08:40.558 --> 00:08:45.098 And quite the flake, you know, like there's all kinds of inputs going on. There's fanciness. 00:08:45.318 --> 00:08:49.778 I don't know what Nick's cats is, but I assume it's a category theory thing 00:08:49.778 --> 00:08:52.658 or just cute cat pictures. Either way, I like it. 00:08:52.778 --> 00:08:52.958 Yeah. 00:08:53.658 --> 00:08:57.358 Oh, maybe it's for NeoVim. I see. Yeah, a lot of NeoVim stuff too, which is great. 00:08:57.758 --> 00:09:03.078 I see in the config folder here, linux-enable-ir-emitter. 00:09:03.738 --> 00:09:06.058 Any guesses on what that's being used for? 00:09:07.738 --> 00:09:09.238 Sounds like something Wes should look at. 00:09:09.678 --> 00:09:10.338 You're right. 00:09:10.498 --> 00:09:13.678 It looks like he's defining a PCI device, right? Is that what he's doing? Interesting. 00:09:14.198 --> 00:09:20.038 Yeah, this is great. This kind of stuff, if you can have this just redeployed 00:09:20.038 --> 00:09:23.778 when you set up your system and these kinds of devices so your IR blaster just 00:09:23.778 --> 00:09:26.218 works, that's getting it dialed in, buddy. 00:09:28.158 --> 00:09:31.338 I'm not sure if we wanted to score these but I'm kind of feeling like this is 00:09:31.338 --> 00:09:33.778 a 4 out of 5 I just have a couple of gripes, 00:09:35.476 --> 00:09:40.416 In my opinion, it's a little sprawly, just a little bit, but not bad, not bad. 00:09:40.556 --> 00:09:44.296 So I can't give it a full five out of five, but I do want to give it a four 00:09:44.296 --> 00:09:46.136 out of four or a four out of five, I think. 00:09:46.396 --> 00:09:48.776 I don't know. How do you feel? Is that a fair? Should we adjust? 00:09:49.036 --> 00:09:50.116 I'm, I'm open to the committee. 00:09:50.616 --> 00:09:54.916 Are there not enough like initialization scripts for you? Is that your problem? 00:09:55.656 --> 00:09:56.296 You bastard. 00:09:56.496 --> 00:10:00.676 Yeah. The activation script, seriously underdeveloped in this one. 00:10:00.756 --> 00:10:03.776 I just can't get five out of five if you don't get that. 00:10:04.136 --> 00:10:06.176 Look, if you're not creating a tilde directory, I don't want to. 00:10:06.196 --> 00:10:07.576 Oh, wait, I'm roasting the wrong person. 00:10:08.856 --> 00:10:11.376 Yeah, yeah, we're roasting their config. 00:10:11.536 --> 00:10:11.696 Ooh, sorry. 00:10:12.796 --> 00:10:16.416 I think, I just don't know if it's a five out of five, but I think it's really close. 00:10:16.736 --> 00:10:21.936 I could be argued up or down if anybody wants to make the case. 00:10:22.016 --> 00:10:25.556 I mean, I think the contributor count, like, okay, maybe it's a little sprawling 00:10:25.556 --> 00:10:28.396 or maybe it's a lot if you're just trying to use it for like one or two systems. 00:10:28.396 --> 00:10:32.196 But I feel like that contributor count says that a lot of the functionality 00:10:32.196 --> 00:10:36.976 in here is probably being used, imported, like, more than just, 00:10:37.536 --> 00:10:41.476 you know, this is not just a single person's config for their, like, laptop at home. 00:10:41.696 --> 00:10:43.996 There's a lot more work and polish in here. 00:10:43.996 --> 00:10:47.256 Okay. All right. So you've got the contributors. Also, I'm talking myself into 00:10:47.256 --> 00:10:50.576 making it a 5 out of 5 because, like, as we'll see as we go along, 00:10:50.756 --> 00:10:53.936 some of these, they kind of go too far. Right? This is a nice balance. 00:10:54.716 --> 00:10:58.256 A lot of things that are solved, problems like those PCI devices, things that are solved. 00:10:58.396 --> 00:11:03.056 But we're not going like nutso with it. You know, you can take it too far. 00:11:03.176 --> 00:11:05.616 So I'm kind of talking myself into a five out of five now. 00:11:06.898 --> 00:11:07.578 Lock it in. 00:11:08.038 --> 00:11:13.018 All right. Okay, so that, hopefully I got anywhere close to your name, 00:11:13.358 --> 00:11:14.818 Ichil, but thank you for sending that in. 00:11:15.178 --> 00:11:18.518 Nice to see the Hyperland setup. Love seeing those. 00:11:18.618 --> 00:11:22.578 And I like seeing Lanzibu, TPM stuff. There's just a lot to like, so thank you. 00:11:22.758 --> 00:11:26.918 Yes, the Lanzibu was cool. All right, our next one is Shane's budget config. 00:11:27.118 --> 00:11:29.438 He says, I've attached a Nix config for you guys to analyze. 00:11:29.838 --> 00:11:33.378 Don't hold back. Tell me how bad it is. My goal with this config is to make 00:11:33.378 --> 00:11:36.378 a working config that uses flakes, although I don't really know what they are 00:11:36.378 --> 00:11:40.898 still, and allows me to add programs from either stable or unstable by choice. 00:11:41.218 --> 00:11:44.518 So after many hours of back and forth with failed configs and hallucinations 00:11:44.518 --> 00:11:48.098 at times, insults towards the stupid bot, we have a working config. 00:11:48.358 --> 00:11:50.338 Now it's probably jank. I don't know. 00:11:50.698 --> 00:11:54.738 But it does seem to work. And so he supplied us with a flake, 00:11:54.978 --> 00:11:58.018 a package.nix, and a configuration.nix. 00:11:58.438 --> 00:12:03.198 And I wanted to get your eyes on that flake there, Wes, and see if you had any 00:12:03.198 --> 00:12:06.678 editor's notes for Shane's budget flake. 00:12:06.898 --> 00:12:09.578 Yeah i mean i think you're you're doing well shane you're well 00:12:09.578 --> 00:12:12.458 on your way to getting a flake system right like going from 00:12:12.458 --> 00:12:15.578 the first sort of configuration.nix setup with channels getting 00:12:15.578 --> 00:12:18.918 into the flake mindset that's a that's a lot to do um 00:12:18.918 --> 00:12:22.838 so we kind of see a pretty clean flake here we've got nix packages and right 00:12:22.838 --> 00:12:26.998 as shane was alluding to also nix packages unstable the first one's pinned to 00:12:26.998 --> 00:12:31.478 a regular release and unstable and then you can see here they have they have 00:12:31.478 --> 00:12:36.418 a let block where they're setting up both unstable and regular packages and then, 00:12:37.263 --> 00:12:42.803 Let's see here. Ah, so then they're using a Nix module that they can feed in 00:12:42.803 --> 00:12:48.063 both manually as a, so they do like an import call to load in their packages.nix file. 00:12:48.463 --> 00:12:53.143 That gets them all the packages they want from either collection of upstream Nix packages. 00:12:53.583 --> 00:12:59.103 And then they use an in-place module in the flake to inject that into the config. 00:12:59.263 --> 00:13:03.223 That's pretty, that's pretty clever. There might be easier ways ultimately depending 00:13:03.223 --> 00:13:05.883 on how you want to do it, but I mean, it definitely works. 00:13:05.883 --> 00:13:10.403 Okay so it's got the west pane approval i wasn't sure i did wonder if there 00:13:10.403 --> 00:13:14.443 was some redundant package assignments in there but that's a pretty minor quibble 00:13:14.443 --> 00:13:19.403 i think uh i think that got a that got a more resounding west pane approval 00:13:19.403 --> 00:13:21.363 than i expected so i'm not gonna argue with that, 00:13:22.083 --> 00:13:28.183 the packages.nix is interesting here it's a it's a pretty well laid out here 00:13:28.183 --> 00:13:30.923 i'll pull it up i hosted these by the way these will be linked in the show notes 00:13:30.923 --> 00:13:33.343 if people listening want to look at these as we're talking about them. 00:13:33.663 --> 00:13:38.503 They are linked over at linuxunplugged.com slash 640 if you'd like to check them out. 00:13:38.783 --> 00:13:43.383 And he has, you know, I think he has a couple of apps that are like his staples, 00:13:43.843 --> 00:13:46.543 that he's pulling from the Nix stable repository. 00:13:47.223 --> 00:13:49.623 And if you're looking, if you look at the packages.nix, and then he's got a 00:13:49.623 --> 00:13:52.283 handful of like, you know, rock and roll apps that he pulls from Unstable, 00:13:52.443 --> 00:13:57.643 like Waybar, WL Roots, those types of things Shane's pulling from Unstable. 00:13:57.783 --> 00:14:01.863 And I think that is, listen to me now, audience, 00:14:03.223 --> 00:14:08.443 other distros can do it nobody does it like NICS right so if you never want 00:14:08.443 --> 00:14:11.203 your NeoVim to get changed out from underneath you you pull that from Staple, 00:14:12.283 --> 00:14:15.383 or your Android tools is another example in here or you know Romania, 00:14:17.722 --> 00:14:21.262 Your launcher, WoFi, your Waybar, why not? 00:14:21.402 --> 00:14:24.182 Why not? Those are pretty rapidly developed. Why not pull those from unstable 00:14:24.182 --> 00:14:26.562 if it works for you? And you could do both. 00:14:27.022 --> 00:14:29.722 Well, and, right, you can swap them, right? So in this case, 00:14:29.842 --> 00:14:32.682 because Shane's got this single file, it's pretty easy to just, 00:14:32.902 --> 00:14:37.082 you know, remove Waybar from unstable and move it back up to stable if that's 00:14:37.082 --> 00:14:37.882 where you want to get it from. 00:14:37.922 --> 00:14:40.302 So I think that is one aspect that this works really well. 00:14:40.942 --> 00:14:44.362 Like, it can be tricky figuring out how you inject both. 00:14:44.502 --> 00:14:46.982 Like, everything's kind of set up. If you do it the normal way, 00:14:47.522 --> 00:14:51.022 like you get your one version of Nix packages and you give that to your module 00:14:51.022 --> 00:14:54.282 and like you just kind of inherit that as packages inside your module. 00:14:54.422 --> 00:14:55.622 It's all easy to access there. 00:14:55.802 --> 00:14:59.062 And then there's multiple different mechanisms for like how do you actually 00:14:59.062 --> 00:15:03.202 thread unstable packages or, you know, how do you thread an additional set of 00:15:03.202 --> 00:15:04.962 Nix packages through your entire config? 00:15:05.462 --> 00:15:08.682 A lot of people use like special args, which can totally work. 00:15:09.182 --> 00:15:12.862 Shane's using a clever, I think, Nix forward approach here. And you can also 00:15:12.862 --> 00:15:17.982 use, which is, this is like halfway to, I think, like using the module interface 00:15:17.982 --> 00:15:19.102 to pass that through as well. 00:15:19.422 --> 00:15:24.162 But I like that, especially for a small config like this, it's really easy to 00:15:24.162 --> 00:15:25.702 switch where you're pulling stuff. So that's great. 00:15:26.042 --> 00:15:31.022 Now, Brent, can I call upon you to give Shane just a quick elevator GitHub talk here? 00:15:31.122 --> 00:15:36.182 Because he sent these as attachments to email because he's not using Git to manage these. 00:15:36.922 --> 00:15:39.002 Seems like that could be an area maybe he could improve on. 00:15:39.002 --> 00:15:41.922 Well, you're assuming he's not using Git to manage these. 00:15:42.042 --> 00:15:46.202 Maybe he's just doing a local Git and doesn't have these necessarily publicly 00:15:46.202 --> 00:15:48.602 available, which I am a big fan of. 00:15:48.762 --> 00:15:52.282 I don't know. I think he said he wasn't, but in the email, I just didn't put 00:15:52.282 --> 00:15:53.962 that in the doc. But I might be wrong. All right. All right. 00:15:54.122 --> 00:15:59.422 Well, if not, I would say, come on, history is great because it keeps track 00:15:59.422 --> 00:16:03.322 of every single mistake or fix that you ever made to your configs. 00:16:03.382 --> 00:16:07.222 And you can go back and look at them or have at least some peace of mind for rollbacks. 00:16:07.822 --> 00:16:10.062 There's really little downside. You should use Git. 00:16:10.302 --> 00:16:10.842 There you go. 00:16:11.823 --> 00:16:15.063 Only took Chris, what, eight months to be convinced? But we're trying. 00:16:15.383 --> 00:16:19.343 You had, again, again, I'm not the one you're, I'm not the one. I'm not. 00:16:20.043 --> 00:16:23.863 If you bother to go with flakes and you don't go with gate, you're just like 00:16:23.863 --> 00:16:26.563 totally losing out on half of the value proposition. 00:16:26.743 --> 00:16:27.083 Oh, yeah. 00:16:27.403 --> 00:16:31.683 There you go. Yeah, yeah, there you go. There you go. I do dig that on his systems, 00:16:31.703 --> 00:16:35.183 he's using systemd boot. Didn't see that across all of the configs. 00:16:35.823 --> 00:16:39.703 And, you know, I say have systemd do all the things, including boot the system. 00:16:40.023 --> 00:16:43.743 So, well done, sir. You thought we'd be mean, but we were pretty impressed. 00:16:44.003 --> 00:16:46.903 Yeah, well, you're going to want SystemD to do apps next, huh? 00:16:47.423 --> 00:16:48.843 Yeah, SystemD app to you, buddy. 00:16:49.363 --> 00:16:52.703 Looks like Shane is from Australia, too, so kudos. 00:16:54.836 --> 00:16:59.116 Ephraim came in. He says, I'm not a Nix user, but I'm a GUX user. 00:16:59.276 --> 00:17:03.556 I figured I'd send you my GUX config, which he did. 00:17:03.596 --> 00:17:06.636 I've been a GUX user and contributor for about 10 years now. 00:17:06.676 --> 00:17:10.016 And I have a small build farm at home, three RISC64 machines, 00:17:10.636 --> 00:17:15.656 three ARCH64, AA ARCH64, so ARM64 machines, two iBook G4s. 00:17:16.376 --> 00:17:19.376 Oh, that's fun. Those iBook G4s were fun. 00:17:19.976 --> 00:17:24.656 And about an even mix of systems running GUX or GUX on top of Debian. 00:17:25.576 --> 00:17:32.696 This this was in this i've seen basic guics examples before but this was some 00:17:32.696 --> 00:17:38.416 guics wizardry and i really really appreciate the eframe sent this in because this gave me exposure, 00:17:39.076 --> 00:17:43.656 to like somebody who knows what the hell they're doing with guics you know it 00:17:43.656 --> 00:17:45.736 really helped me kind of understand it a bit better i. 00:17:45.736 --> 00:17:47.996 Believe it's pronounced geeks um. 00:17:47.996 --> 00:17:51.396 Yeah you're right you're right it is i'm sorry that's an old habit it is pronounced 00:17:51.396 --> 00:17:52.936 geeks but you're right like. 00:17:52.936 --> 00:17:57.416 We've I've seen it. I've been curious about it. I've tried a little bit, because it's like Nix. 00:17:57.656 --> 00:18:03.296 They share a lot, except Nix rolled its own... Nix makes it super confusing 00:18:03.296 --> 00:18:06.696 because you get Nix OS the OS. You get Nix packages the packages. 00:18:07.736 --> 00:18:11.336 You get Nix as a build tool. And, of course, that build tool also decided that 00:18:11.336 --> 00:18:15.396 they would ship with their own programming language the Nix language, or Nixlang. 00:18:16.196 --> 00:18:20.856 Whereas Geeks used Scheme, which is a type of Lisp, as their language, 00:18:21.076 --> 00:18:24.796 along with their own tooling and libraries and standard lib and all that kind 00:18:24.796 --> 00:18:26.696 of stuff on top of it. So it's sort of like a... 00:18:27.664 --> 00:18:30.844 A sibling in the Knicks family, if you will. But yeah, you're right. 00:18:30.924 --> 00:18:35.684 Like I've never, I've not yet had the chance to really appreciate a fully used 00:18:35.684 --> 00:18:37.784 Geeks config that wasn't just managing some packages. 00:18:38.524 --> 00:18:43.144 Yeah. Yeah. And also across multiple architectures too. The, 00:18:43.144 --> 00:18:45.464 you know, the Pine 64 is in here. The ARM system's in here. 00:18:46.284 --> 00:18:51.244 Rock 64, I think. It's so cool. And I saw like he had a system in there for his kids. 00:18:51.584 --> 00:18:52.684 It hasn't been updated for a 00:18:52.684 --> 00:18:57.424 little bit, but he can pull in like these profiles and that's a neat idea. 00:18:58.084 --> 00:18:59.884 Profiles for different systems there's. 00:18:59.884 --> 00:19:02.644 Also i don't know if you noticed vm config that's kind of neat. 00:19:02.644 --> 00:19:03.324 Yeah you. 00:19:03.324 --> 00:19:06.224 Can see like there's some stuff in here to define an operating system with the 00:19:06.224 --> 00:19:09.904 host name time zone like it looks the bootloader config a lot of this even though 00:19:09.904 --> 00:19:13.704 the syntax is a little different it looks a lot like a nick system it's kind 00:19:13.704 --> 00:19:16.444 of it's it's like living in a different parallel universe. 00:19:16.444 --> 00:19:21.944 I was checking out his commit history and three weeks ago he had a really 00:19:22.004 --> 00:19:25.024 interesting commit and uh it was 00:19:25.024 --> 00:19:28.264 adapting mpv to always include 00:19:28.264 --> 00:19:32.484 sponsor block so it's like pre-bundled into 00:19:32.484 --> 00:19:36.024 mvv to have i maybe he's pulling down youtube streams 00:19:36.024 --> 00:19:38.704 or something i don't know but it's an 00:19:38.704 --> 00:19:44.484 interesting application of geeks here where you can sort of build this like 00:19:44.484 --> 00:19:48.424 this and so looking through his commit history here it was pretty fascinating 00:19:48.424 --> 00:19:53.064 to see that and also just like a great idea i just love that and it's pretty 00:19:53.064 --> 00:19:56.764 powerful stuff lots of little things in there don't i mean he's managing some 00:19:56.764 --> 00:19:58.564 of the stuff at a pretty intricate level, 00:19:59.813 --> 00:20:03.853 Which seems like a little tedious to me, but the results seem to speak for themselves. 00:20:04.333 --> 00:20:07.433 Well, it seems neat, too, because I don't know if there is a Home Manager quite 00:20:07.433 --> 00:20:11.073 equivalent, but you can see, right, that came from the home.scm file. 00:20:12.713 --> 00:20:15.053 And maybe I guess that's stuff that's built in. I see, like, 00:20:15.153 --> 00:20:17.313 use module, GNU, home services. 00:20:17.893 --> 00:20:18.173 Yeah. 00:20:19.273 --> 00:20:22.093 But it kind of shows, like, clearly Geeks is pretty darn flexible, 00:20:22.093 --> 00:20:27.113 because without, at least as far as I can tell, a giant system activation script, 00:20:27.113 --> 00:20:31.273 you know they're they're managing like mpv's conf like all kinds of different, 00:20:31.853 --> 00:20:35.513 conf files that probably you would have to use something like home manager or 00:20:35.513 --> 00:20:38.073 a dot file manager or something on another system. 00:20:38.073 --> 00:20:43.473 I see you two have decided that i'm the villain of this uh of this sequel it's. 00:20:43.473 --> 00:20:44.453 Just good storytelling. 00:20:44.453 --> 00:20:48.093 This is why you want to put your stuff up on github that way your buddies can 00:20:48.093 --> 00:20:53.413 make funny all the time this is why you want to do it okay all right but very 00:20:53.413 --> 00:20:57.553 well very well done very very thought out thank you for sending that in i don't 00:20:57.553 --> 00:21:01.533 have a lot of comments um i do think it's interesting to kind of i have more 00:21:01.533 --> 00:21:03.293 questions than i like i yeah. 00:21:03.293 --> 00:21:04.553 Homework more to do really. 00:21:04.553 --> 00:21:09.893 Yeah yeah yeah absolutely all right our next config confession comes from distro 00:21:09.893 --> 00:21:14.813 stew and he says every time i have uh every time i have an alias you that updates 00:21:14.813 --> 00:21:17.953 everything oh okay regardless of my package manager and i did it this way in 00:21:17.953 --> 00:21:21.113 nix for a long time eventually started causing issues so now i've broken into 00:21:21.113 --> 00:21:22.933 more granular aliases, check it out. 00:21:23.733 --> 00:21:25.693 And he provides his config. 00:21:26.193 --> 00:21:27.673 Distro Stu, look at you. 00:21:27.953 --> 00:21:30.553 Yeah, look at his management commands here. He's got, and you know, 00:21:30.633 --> 00:21:33.033 if you're going to do this, document it, which he has done. 00:21:33.613 --> 00:21:38.573 So u-nixos pulls updates and applies to nixos configs. u-home pulls updates 00:21:38.573 --> 00:21:41.013 for the home manager and applies to nix configs. 00:21:41.353 --> 00:21:45.433 U-flatpack command updates the flatpacks on my desktop. 00:21:45.953 --> 00:21:46.793 That's pretty great. 00:21:47.013 --> 00:21:51.113 I've never done this. In all my years of Linux, I've never really got into aliasing. 00:21:51.373 --> 00:21:53.473 I always hesitate because it's... 00:21:54.478 --> 00:21:57.298 It's super convenient, obviously, for things that you run all the time. 00:21:57.678 --> 00:22:01.098 But then if you're moving to a new system that doesn't have your aliases for 00:22:01.098 --> 00:22:05.498 any reason, then will you forget how to do it the native way? 00:22:05.798 --> 00:22:09.618 It's always a fear of mine, right? How do I update NixOS again? I forget. 00:22:10.178 --> 00:22:14.018 That's why I don't do it. Okay, I got to give brownie points when I seize it. 00:22:14.138 --> 00:22:16.878 We didn't rate the last one. I think the last one was probably a five. It was hard to rate. 00:22:17.118 --> 00:22:21.298 But this always brings it up on my list. This is how you get a win with me. 00:22:21.338 --> 00:22:24.278 And it's how to get started right here in the ReadMe. 00:22:24.478 --> 00:22:29.018 A fresh system, copy these commands, run these commands, pull this in, 00:22:29.118 --> 00:22:33.838 whatever it is, just go from blank system to my full setup. 00:22:33.878 --> 00:22:40.438 When people have that and they've documented it, I'm giving it a W. 00:22:41.258 --> 00:22:46.538 I mean, so you guys got to talk me out of this, but DistressDrew here, he got a lot of points. 00:22:46.718 --> 00:22:51.218 I mean, that makes it at least a three and a half right there because he's got that. 00:22:52.758 --> 00:22:55.398 I do like it. And he's got his own commands. He's got a flake system pulling 00:22:55.398 --> 00:22:56.378 in some unstable goodness. 00:22:56.938 --> 00:23:01.378 What do you think of the nesting? You know, like, Stu pointed us at the NixOS 00:23:01.378 --> 00:23:05.258 stuff, but that's kind of only one subdir in this whole repo. 00:23:05.518 --> 00:23:08.798 I mean, it does have its own readme. So I'm not trying to take away from that. 00:23:09.358 --> 00:23:11.758 But there's a lot of others. I got, when I was looking through, 00:23:11.838 --> 00:23:16.578 I kind of got lost just because there's a lot of other interesting stuff in this total config repo. 00:23:16.758 --> 00:23:21.198 So props to you for that. Like, there's stuff here for devenv and for flocks 00:23:21.198 --> 00:23:22.698 and like flatpack scripts. 00:23:23.398 --> 00:23:28.518 So even outside of the Nix configs, Stu clearly has a lot of his computing life 00:23:28.518 --> 00:23:30.738 automated and documented, which is pretty great. 00:23:31.418 --> 00:23:34.798 Okay. I feel like that brings it up to a four. 00:23:36.418 --> 00:23:40.658 Can we get distro Stu up to a five? Brent, do you have any thoughts on how we can do that? 00:23:40.858 --> 00:23:44.518 Well, I'm seeing a couple things here. I'm seeing Disco being used. 00:23:44.778 --> 00:23:48.818 I think that gets extra points. Setting up systems using Disco is... 00:23:50.098 --> 00:23:52.858 On the expert side of things and definitely where things are going. 00:23:52.858 --> 00:23:56.798 Also successfully navigated uh 00:23:56.798 --> 00:24:00.058 there was there was a minute where some of the like the newer linux 00:24:00.058 --> 00:24:03.158 kernel latest kernel kind of broke a small test 00:24:03.158 --> 00:24:06.398 inside tailscale if you're building it anyway it 00:24:06.398 --> 00:24:09.998 caused problems that you kind of had to do an override if you're on unstable uh 00:24:09.998 --> 00:24:14.678 in nix i see that override which i think can now be removed so no there but 00:24:14.678 --> 00:24:19.018 as a positive because you know you had to go find the issue and like copy the 00:24:19.018 --> 00:24:22.318 code into an overlay and figure out where that goes in the config and like make 00:24:22.318 --> 00:24:28.798 it work so sort of a good you know nicks in practice paper cuts edition and. 00:24:28.798 --> 00:24:32.218 Like wes was saying you know stew has folders for hosts and modules and then 00:24:32.218 --> 00:24:36.558 there's a folder a directory just for files and if you go into this files directory 00:24:36.558 --> 00:24:42.818 it has just one thing and it's a sync thing ignore.txt and that's it he's like 00:24:42.818 --> 00:24:44.638 he solved that problem once, 00:24:46.258 --> 00:24:49.878 nicely done yeah and that's good you know like it for the max it doesn't sync 00:24:49.878 --> 00:24:54.438 the .ds store crap and whatnot i did see speaking of max i did see that uh distro 00:24:54.438 --> 00:24:58.718 stew has a nix config for an m series macbook which i'll link in the show notes 00:24:58.718 --> 00:25:02.738 specifically if you out there are trying to get that working nice to see did. 00:25:02.738 --> 00:25:06.278 You check more into sync thing.nix because there's i mean it's not just that 00:25:06.278 --> 00:25:08.198 ignores thing like there's a lot going on. 00:25:08.198 --> 00:25:11.158 No i should huh no i was just impressed with the ignores. 00:25:11.538 --> 00:25:15.758 Yeah, go under configs, nixOS modules, syncthing.nix. 00:25:15.938 --> 00:25:18.878 Yeah, I'm also seeing configs here for, well, it depends where you look. 00:25:19.038 --> 00:25:22.898 If you look in the hosts folder, it's a little bit less, but I saw configs for 00:25:22.898 --> 00:25:25.198 at least eight different hosts. 00:25:27.038 --> 00:25:29.978 So that's really nice to see. 00:25:30.598 --> 00:25:32.558 DistroStrew's getting himself a little mini fleet going. 00:25:32.978 --> 00:25:35.678 Mm-hmm. A couple different architectures too, so nicely done. 00:25:36.258 --> 00:25:40.118 Oh, yeah, and he's got, okay, this is a really cool syncthing.nix. 00:25:40.138 --> 00:25:46.138 Fig he's got the different systems in here and their sync thing ids oh man this 00:25:46.138 --> 00:25:50.118 is we should we should add that to the show notes that's a slick sync thing setup. 00:25:51.055 --> 00:25:53.455 I thought you'd like that. 00:25:53.735 --> 00:25:55.215 I think that brings it to a five. 00:25:55.455 --> 00:25:55.635 Whoa. 00:25:56.715 --> 00:25:57.255 Right? 00:25:57.595 --> 00:26:00.215 So we're just doing like the DoorDash rating system today. 00:26:00.535 --> 00:26:01.495 Yeah, I guess so. 00:26:01.915 --> 00:26:05.055 He's also using HomeManager. Maybe you can get inspired here. 00:26:05.415 --> 00:26:10.475 Bring it, Brent. I was actually hoping to see less HomeManager usage here. 00:26:11.955 --> 00:26:15.935 Well, maybe we can like VibeCode something that converts HomeManager configs 00:26:15.935 --> 00:26:17.535 into activation scripts or something. 00:26:18.115 --> 00:26:18.295 Okay. 00:26:21.455 --> 00:26:24.115 I just, you know what I want, really honestly would work for me, 00:26:24.135 --> 00:26:28.475 if we could somehow have Markdown converted into Home Manager. 00:26:29.255 --> 00:26:32.675 That, now we're talking, if I could just write the whole thing in Markdown. 00:26:32.875 --> 00:26:36.455 You record a voice note on your phone and then that becomes your Home Manager config. 00:26:36.635 --> 00:26:40.835 Even better, even better. Can we do that? I think, you know, 00:26:40.955 --> 00:26:42.415 DistroStu, I think you did pretty well here. 00:26:42.715 --> 00:26:47.515 Like Wes said, there is that tailscale overlay thing that you could probably fix now. 00:26:47.855 --> 00:26:52.215 But that was a good catch on your part. so i guess that makes all of these five 00:26:52.215 --> 00:26:56.515 out of fives it's the summer of it's the it's the fall i think the geeks. 00:26:56.515 --> 00:27:00.715 One we technically have to use imaginary numbers it's like a whole separate axis definitely. 00:27:00.715 --> 00:27:08.495 Negative four um 22 i don't know but yeah these are some pretty solid configs 00:27:08.495 --> 00:27:13.355 minor stuff in there real minor stuff nice to see well done everyone now we're 00:27:13.355 --> 00:27:14.455 gonna get into some tricky ones. 00:27:22.748 --> 00:27:27.008 1password.com slash unplugged. Take the first steps to better security for your 00:27:27.008 --> 00:27:30.588 team by securing credentials and protecting every application, 00:27:30.888 --> 00:27:32.108 even the ones you don't know about. 00:27:32.208 --> 00:27:36.208 Learn more at 1password.com slash unplugged. That's the number one password 00:27:36.208 --> 00:27:37.928 and it's all lowercase unplugged right there. 00:27:38.088 --> 00:27:42.188 You just go there and learn more because this is something that would have changed 00:27:42.188 --> 00:27:44.028 the game for me when I was in IT. 00:27:44.248 --> 00:27:47.648 If you're in IT, if maybe you're in security as well, Well, you know what a 00:27:47.648 --> 00:27:48.908 mountain of different assets. 00:27:49.168 --> 00:27:52.908 There's physical hardware. There's user identities. There's applications. 00:27:53.228 --> 00:27:57.868 And it's a lot, and it's always growing. Well, you can conquer this continuously 00:27:57.868 --> 00:28:02.248 growing mountain of security risk with 1Password extended access management. 00:28:02.428 --> 00:28:06.688 This is a huge issue. You're not alone. This has been identified as a major problem out there. 00:28:06.948 --> 00:28:13.308 And this is where 1Password is trying to make life better for both users, IT, and security. 00:28:13.468 --> 00:28:17.488 And they have Trellica. This is something that can discover and secure access 00:28:17.488 --> 00:28:20.168 to all of your apps, managed or unmanaged. 00:28:20.688 --> 00:28:23.948 Trellica by 1Password inventories every app and usage of your company. 00:28:24.088 --> 00:28:27.748 It has pre-populated app profiles so it can assess the different SaaS risks. 00:28:27.888 --> 00:28:31.428 It'll let you know who has access to what. You can manage that. 00:28:31.528 --> 00:28:35.168 You can optimize the spend. You can even enforce security best practices across 00:28:35.168 --> 00:28:37.268 every applications your employees use. 00:28:37.388 --> 00:28:41.208 And now you're going to know which ones they're using, even the shadow IT. 00:28:41.828 --> 00:28:45.648 I also really appreciate this because I know so many companies struggle with 00:28:45.648 --> 00:28:47.928 onboarding and offboarding employees. 00:28:48.048 --> 00:28:50.348 You have a process that lasts for a little while. 00:28:51.108 --> 00:28:54.848 This needs to be better. And this is an area where 1Password can help. 00:28:54.968 --> 00:28:56.288 It can help you meet compliance goals. 00:28:57.204 --> 00:29:01.544 It provides a complete solution for SaaS access governance. Trelica by 1Password 00:29:01.544 --> 00:29:05.144 is just one of the ways that extended access management as an entire suite helps 00:29:05.144 --> 00:29:07.684 teams strengthen compliance and security. 00:29:07.884 --> 00:29:11.964 You know about their award-winning password manager. I use it. Family members use it. 00:29:12.304 --> 00:29:15.464 It's trusted by millions of people. I was really thrilled when they came to Linux. 00:29:16.024 --> 00:29:20.044 Businesses all over the world use it. This goes way beyond that. 00:29:20.124 --> 00:29:23.864 They're securing more than just passwords with 1Password extended access management. 00:29:24.404 --> 00:29:28.004 This is something that would make life easier for me, and I think it'll make life easier for you. 00:29:28.144 --> 00:29:31.644 So take the first steps to better security for your team by securing credentials 00:29:31.644 --> 00:29:35.144 and protecting every application, even the unmanaged ones. 00:29:35.284 --> 00:29:40.444 You can learn more by supporting the show and going to 1password.com slash unplugged. 00:29:40.524 --> 00:29:41.924 They have a video there you could watch. 00:29:42.024 --> 00:29:47.284 That's the number 1password.com slash unplugged. All lowercase. Go learn more. 00:29:47.704 --> 00:29:49.964 1password.com slash unplugged. 00:29:56.204 --> 00:29:59.924 Join crowdhealth.com and use the promo code unplugged. 00:30:00.144 --> 00:30:03.884 This is something that has changed my life and my wife's life. 00:30:04.004 --> 00:30:06.464 As small business owners, both of us, we own our own business. 00:30:06.584 --> 00:30:08.664 We have really struggled with 00:30:08.664 --> 00:30:12.544 medical insurance and we just needed something that was a better deal. 00:30:12.944 --> 00:30:17.064 And honestly, something that gave us some peace of mind. And it's open enrollment right now. 00:30:17.184 --> 00:30:20.524 The season where all the health insurance companies will hope that you'll just 00:30:20.524 --> 00:30:24.464 sign on the dotted line once again for what is just ridiculously priced premiums 00:30:24.464 --> 00:30:27.744 and lots of confusing fine print where they're going to try to wiggle out of 00:30:27.744 --> 00:30:29.624 helping you. That's what I've noticed at least. 00:30:30.747 --> 00:30:33.687 You don't even take my word for it. Go trust yourself. Take control of your 00:30:33.687 --> 00:30:38.127 future with CrowdHealth. It's a health care alternative for people who make their own decisions. 00:30:38.567 --> 00:30:41.427 Don't play the insurance company's game. Go join CrowdHealth. 00:30:41.507 --> 00:30:44.307 It's a community of people funding each other's medical bills directly. 00:30:44.547 --> 00:30:47.487 No middlemen, no networks, no nonsense. 00:30:47.727 --> 00:30:52.747 It's like you have a team of people that will negotiate with the hospital on your behalf. 00:30:52.747 --> 00:30:57.827 And the process goes from feeling like you're just a number in a machine that's 00:30:57.827 --> 00:31:02.727 just getting an output probably from, I would doubt, no day in LLM. 00:31:03.187 --> 00:31:07.827 CrowdHealth makes it feel personal, direct, and like actions actually happening. 00:31:07.867 --> 00:31:10.747 And they have a great app to walk through from the very beginning of the process 00:31:10.747 --> 00:31:15.087 all the way to the end, both as you the contributor or somebody asking for a contribution. 00:31:15.467 --> 00:31:20.547 This is CrowdHealth, the health insurance alternative, healthcare for under $100. 00:31:21.007 --> 00:31:24.887 You get access to a team of health bill negotiators, low-cost prescriptions, 00:31:25.207 --> 00:31:29.747 lab testing tools, as well as a database of low-cost, high-quality doctors that 00:31:29.747 --> 00:31:31.287 have been vetted by the crowd health community. 00:31:31.587 --> 00:31:36.487 And if something major happens, you pay the first $500 and then the crowd steps in to fund the rest. 00:31:37.367 --> 00:31:41.947 This has been a mess. Health insurance has, it's just been years of a mess. 00:31:42.087 --> 00:31:44.927 And the only way we're going to change it is in the market. 00:31:45.227 --> 00:31:47.347 That's the only thing these people are going to pay attention to. 00:31:47.547 --> 00:31:50.287 And crowd health is a group of people taking care of each other. 00:31:50.667 --> 00:31:54.127 Don't stay stuck in the same overpriced, overcomplicated mess. 00:31:54.207 --> 00:31:56.587 If it's not working for you, go somewhere else. 00:31:57.267 --> 00:32:00.967 CrowdHealth members have saved over $40 million in healthcare expenses because 00:32:00.967 --> 00:32:02.587 they refuse to overpay for healthcare. 00:32:03.987 --> 00:32:08.187 Now's the time. Take your power back. Join CrowdHealth to get started for $99 00:32:08.187 --> 00:32:10.027 for the first three months. 00:32:10.227 --> 00:32:14.507 Use the promo code UNPLUGGED at joincrowdhealth.com. See why I've been using 00:32:14.507 --> 00:32:18.947 it for over three years. Join crowdhealth.com promo code unplugged. 00:32:19.607 --> 00:32:22.887 CrowdHealth is not insurance. Opt out and take your power back. 00:32:23.147 --> 00:32:28.207 This is how we win. Join crowdhealth.com and promo code unplugged. 00:32:33.675 --> 00:32:39.355 Last episode, we got a boost from our dear Olympia Mike sending in his Nixbook config. 00:32:39.675 --> 00:32:43.835 He says here, hey guys, I'd love to get in on the roast my Nixconfig action. 00:32:44.075 --> 00:32:48.355 This isn't my personal config, but the main Nix module for the Nixbook project 00:32:48.355 --> 00:32:51.435 that I've been working on for nearly a year now. 00:32:52.435 --> 00:32:57.775 Yeah, we have Nixbooks. Mike was very generous and gave us each a Nixbook, 00:32:57.775 --> 00:33:02.975 which he has essentially taken on this role of refurbishing abandoned machines 00:33:02.975 --> 00:33:10.095 and putting a Chrome OS-like experience based on NixOS onto these, hence the name Nixbook. 00:33:10.235 --> 00:33:15.355 And he's actually getting quite a fleet, and he's become known in our local area for doing this. 00:33:15.875 --> 00:33:18.835 And we call him Olympia Mike because he's from Olympia, Washington. 00:33:19.315 --> 00:33:24.075 And so what he sent us in is the configuration he's deploying to all of these people out there. 00:33:24.195 --> 00:33:29.015 And I don't know the exact number, but I know it's probably in the low hundreds. 00:33:29.195 --> 00:33:32.055 So it's quite a bit of people and it's growing all the time. 00:33:32.055 --> 00:33:34.555 When I check in with them, I always hear about more people that are deploying 00:33:34.555 --> 00:33:35.835 it or I see something on his social. 00:33:36.455 --> 00:33:41.135 So I was really looking forward to digging through Ollie Mike's next book set up. 00:33:41.635 --> 00:33:43.695 I'll start with what I liked and I'd like to hear from you gentlemen. 00:33:43.895 --> 00:33:47.735 I do have a few ideas, but I'll start with what I liked. 00:33:48.635 --> 00:33:53.075 He's got an auto update system in here and I'm a big fan of if you're deploying 00:33:53.075 --> 00:33:55.955 these systems in a way where you can roll back if something goes wrong, 00:33:56.635 --> 00:34:01.955 build them to update take some precautions which I'll get into later but I love 00:34:01.955 --> 00:34:05.595 that he has that forward thinking kind of approach to managing these systems now. 00:34:06.947 --> 00:34:11.747 I think if I would just add to that some sort of more air catching, 00:34:12.147 --> 00:34:16.247 maybe an auto stop or rollback, you know, like if somebody, for example, 00:34:16.267 --> 00:34:17.807 would be because I've had this happen to me. 00:34:18.227 --> 00:34:21.507 If I'm doing an update and I lose my internet connection, it kind of just gets 00:34:21.507 --> 00:34:24.647 stuck in like this no man's own loop, right? 00:34:24.727 --> 00:34:29.247 So some stuff around that kind of catching errors with the updates or maybe 00:34:29.247 --> 00:34:32.247 like the checkout didn't work completely or something like that, 00:34:32.247 --> 00:34:35.887 I think would make that even a little bit better of a system just from the short 00:34:35.887 --> 00:34:37.847 experience I had with it. but I like it a lot. 00:34:38.667 --> 00:34:40.907 One thing I always hesitate with, 00:34:41.812 --> 00:34:45.232 With auto-updating systems is, considering my crazy lifestyle, 00:34:45.532 --> 00:34:49.792 I'm often on a network that I don't necessarily want to pull down a ton of data. 00:34:50.172 --> 00:34:50.332 Yeah. 00:34:50.592 --> 00:34:53.312 So a little notification, I don't know, five minutes before saying, 00:34:53.412 --> 00:34:56.572 hey, five minutes from now we're going to do this. And a little, 00:34:56.572 --> 00:34:59.612 like, please no button would be really nice for my lifestyle. 00:34:59.712 --> 00:35:04.572 I don't know how easy or hard that is, but I'll just throw that out as a feature request. 00:35:05.152 --> 00:35:10.252 You know, what's funny is in my initial notes, I had like a little on-screen 00:35:10.252 --> 00:35:11.932 display that says your system's going to get updated. 00:35:12.052 --> 00:35:14.852 And I thought, I put myself in Mike's shoes for a second, and I thought, 00:35:15.032 --> 00:35:17.392 I bet he doesn't even want them thinking about it. 00:35:17.932 --> 00:35:20.792 He just wants it like a Chromebook, just all updating in the background. 00:35:20.992 --> 00:35:22.632 That's a great point. 00:35:22.912 --> 00:35:26.272 I don't know, Brent. What do you think about switching to a Knicks book for a while? 00:35:26.432 --> 00:35:30.692 Because just given the bug field and exactly what you were just saying, 00:35:30.992 --> 00:35:35.292 this might be the fastest way to get some great feedback possible. 00:35:35.292 --> 00:35:36.532 There you go i like that. 00:35:36.532 --> 00:35:39.672 Idea you know when mike gave us these he specifically said hey 00:35:39.672 --> 00:35:43.272 brent please try to break this and give me some feedback so 00:35:43.272 --> 00:35:46.652 i do have one of these nick's books on some 00:35:46.652 --> 00:35:50.392 refurbished hardware that he provided us um right 00:35:50.392 --> 00:35:53.512 above my head here in the van in the cupboard it's been the dedicated like 00:35:53.512 --> 00:35:56.452 van laptop of course when 00:35:56.452 --> 00:35:59.452 i do podcasting in here i actually have my main system but 00:35:59.452 --> 00:36:02.452 as like a pull it out and just use it for a quick thing 00:36:02.452 --> 00:36:05.832 i have been using index book for i guess 00:36:05.832 --> 00:36:08.712 it's like four or five months now i don't use it that 00:36:08.712 --> 00:36:11.552 often but it's been doing what it 00:36:11.552 --> 00:36:15.652 needs to every once in a while when i pull it out but i am going for the long 00:36:15.652 --> 00:36:21.332 term review so i think so far been okay haven't run into any huge massive bugs 00:36:21.332 --> 00:36:25.272 there is that hesitation i mentioned about the auto updating when i'm on like 00:36:25.272 --> 00:36:31.092 sketchy networks so i tend to I only want to do that when I'm connected to, like, 00:36:31.212 --> 00:36:34.152 a grid network or something like that. But otherwise, it's been okay. 00:36:34.512 --> 00:36:38.232 I got an idea about this. And I don't know, Wes, if this is... 00:36:38.772 --> 00:36:41.952 I think this is possible. So when I set up auto-update for my kids' systems 00:36:41.952 --> 00:36:44.892 for, like, five minutes, I considered... 00:36:45.936 --> 00:36:50.536 Like a bandwidth limiter of some kind, like a way to say, don't use more than 00:36:50.536 --> 00:36:53.776 X, you know, megabits or, or whatever. 00:36:53.916 --> 00:36:56.096 I don't know if it was possible because I never, like I said, 00:36:56.096 --> 00:36:57.196 I just looked into it for five minutes. 00:36:57.596 --> 00:37:00.856 Could that be something that would be achievable? Would that have to be its 00:37:00.856 --> 00:37:02.356 own separate update script? 00:37:02.956 --> 00:37:05.736 Yeah i mean you'd have to make sure that you like you 00:37:05.736 --> 00:37:08.456 could definitely apply that kind of stuff with traffic control or other 00:37:08.456 --> 00:37:12.676 setups on linux you just i think the sandboxing be would be what you need to 00:37:12.676 --> 00:37:15.876 make sure because if you're using like multi-user nix then you're actually just 00:37:15.876 --> 00:37:19.396 talking to a demon that wouldn't be running under your sandbox unless you specifically 00:37:19.396 --> 00:37:22.676 config you know or like so i think it might be kind of tricky if you didn't 00:37:22.676 --> 00:37:26.256 want to apply that rate limiting globally there. 00:37:26.256 --> 00:37:27.736 Is a way to indicate networks. 00:37:27.736 --> 00:37:34.616 True yeah you could like not do it if you can sort of detect the metadata from the system. 00:37:34.816 --> 00:37:42.856 Am I on Wi-Fi or do I do a speed test or check what ISP you're on or the actual 00:37:42.856 --> 00:37:44.576 system metadata, depending on how good that is. 00:37:45.076 --> 00:37:48.676 Okay, I have a couple of suggestions. I want to bounce off you guys. 00:37:50.485 --> 00:37:56.085 I don't know if this is creepy, but let's say Olly Mike has a fleet size of 200. 00:37:57.585 --> 00:38:02.305 And these are, I'm just guessing on numbers, but these are almost exclusively 00:38:02.305 --> 00:38:06.905 people that are using it for word processing, web browsing, email, 00:38:07.185 --> 00:38:10.785 you know, tasks that are refurbished like Dell would be perfect for. 00:38:11.905 --> 00:38:16.105 And I wonder, is it creepy? I think you'd have to get user permission. 00:38:16.685 --> 00:38:20.605 But is there a space here for some kind of monitoring 00:38:20.605 --> 00:38:23.445 like so you know which systems haven't been 00:38:23.445 --> 00:38:27.925 updated in x amount of days or maybe monitor rollbacks in the log and see which 00:38:27.925 --> 00:38:32.985 if anybody's having to roll back which would maybe indicate a problem is that 00:38:32.985 --> 00:38:37.085 what do you think i just think when when you're at five systems ten systems 00:38:37.085 --> 00:38:41.285 no big deal when you're at 200 systems, 00:38:41.765 --> 00:38:43.725 and you're doing channel-based updates, 00:38:44.805 --> 00:38:52.265 I don't know, it's like, feels like you might want some kind of observation on how that all is going. 00:38:52.325 --> 00:38:54.605 What do you think? Is there a way to do that that isn't creepy? 00:38:56.272 --> 00:39:01.072 Hmm. Yeah, I mean, as long as you're upfront about it, and maybe you provide a way to disable it. 00:39:01.652 --> 00:39:05.692 I do like the idea, like, you get little pings home as auto-updates or reboots 00:39:05.692 --> 00:39:07.572 or stuff become successful. 00:39:07.572 --> 00:39:13.072 But that said, I don't know what the support, does that create more of, 00:39:13.152 --> 00:39:16.672 like, an onus on support when you're kind of just like, look, 00:39:16.772 --> 00:39:19.792 I'm doing my best and I'm putting these out there, but hey, don't call me. 00:39:20.912 --> 00:39:21.952 I don't know what the. 00:39:21.952 --> 00:39:25.632 Level of personal support mike wants to be putting out or would you just use 00:39:25.632 --> 00:39:28.912 it as like development metrics for like oh boy that last one didn't go well 00:39:28.912 --> 00:39:29.932 i might need to tell folks. 00:39:29.932 --> 00:39:32.732 Yeah that's what i was wondering is 00:39:32.732 --> 00:39:35.792 like does mike develop this into a business one day i mean 00:39:35.792 --> 00:39:38.592 if you get enough users you could and then maybe 00:39:38.592 --> 00:39:41.252 you do want observation you know you want some sort 00:39:41.252 --> 00:39:44.092 of monitoring um and i 00:39:44.092 --> 00:39:47.552 also think feature flags because as 00:39:47.552 --> 00:39:50.692 you get more users you just you just collect all these edge cases 00:39:50.692 --> 00:39:56.332 and so you might want a really simple way like one file somebody can go into 00:39:56.332 --> 00:40:00.292 on their system and just disable certain features like maybe auto updates or 00:40:00.292 --> 00:40:04.652 flat packs or whatever like some some simple way for them to go in and just 00:40:04.652 --> 00:40:08.192 say on this system we don't want auto updates for some reason, 00:40:09.108 --> 00:40:12.488 Um, cause you're always going to have these edge cases. So I think that could be useful. 00:40:12.908 --> 00:40:17.708 Or, you know, you just accept that Mac and windows update whenever they want. So we get to, too. 00:40:18.688 --> 00:40:22.448 Uh, maybe. Okay. But the elephant in the room and he said it when he wrote in, 00:40:22.728 --> 00:40:26.488 uh, is that he's using channels, which means everything he's putting out there 00:40:26.488 --> 00:40:29.468 is hard coded to a specific version of Nix OS. 00:40:29.648 --> 00:40:31.968 In this case, 2505, which came out in May, obviously. 00:40:32.688 --> 00:40:38.468 And those do have end of life dates. So the fleet has to be migrated to the next channel. 00:40:39.408 --> 00:40:44.088 And that's kind of like doing a Fedora distro upgrade or a Debian distro upgrade in some senses. 00:40:44.308 --> 00:40:49.248 It can be a larger set of changes than a standard update. 00:40:50.348 --> 00:40:53.128 And I wonder, Wes, if this doesn't 00:40:53.128 --> 00:40:58.588 call for a solution where is Mike maybe sitting in front of that stuff? 00:40:58.748 --> 00:41:03.148 Like if he's not going to do a flake, how could he better handle a channel-based 00:41:03.148 --> 00:41:05.008 system? Or is it just use Flakes? 00:41:05.688 --> 00:41:08.228 Yeah, I'm not the person to ask. I don't use channels at all. 00:41:08.488 --> 00:41:13.228 No, I mean, I think it does mean you have more, you know, imperative stuff to manage on the machine. 00:41:13.448 --> 00:41:17.308 I do think you could get where you want to go eventually with Flakes and probably 00:41:17.308 --> 00:41:18.888 ultimately have a better time. 00:41:19.368 --> 00:41:21.528 I think you can kind of tell there's a lot here. 00:41:22.268 --> 00:41:24.948 I mean, if you just look around in this repo, right, there's a lot of different. 00:41:25.108 --> 00:41:27.668 There's update.sh, there's install.sh. 00:41:28.028 --> 00:41:32.308 And within the config, there's a lot of different scripts kind of like keeping everything together. 00:41:32.308 --> 00:41:35.768 But that you are going to do more of that composition locally 00:41:35.768 --> 00:41:38.908 with the channel because it isn't as hermetically tied 00:41:38.908 --> 00:41:41.908 together as a flake does probably mean you know 00:41:41.908 --> 00:41:44.688 mike's got to make sure he's got plenty of good test machines ready to 00:41:44.688 --> 00:41:49.828 go to like verify that everything that is possible and maybe it's more complicated 00:41:49.828 --> 00:41:53.528 if you do have too many of those feature flags like make sure all versions of 00:41:53.528 --> 00:41:57.708 your config are going to successfully be able to build with the updated channel 00:41:57.708 --> 00:42:01.008 and then like how do you stage that rollout is it just one push that you do 00:42:01.008 --> 00:42:04.208 do you some people get it before others all that kind of stuff. 00:42:05.360 --> 00:42:09.980 Yeah, staged rollouts could be helpful, too. You know, if you have a particular group of savvy users. 00:42:10.200 --> 00:42:12.640 But I don't know if there's any, like, plumbing in here for, 00:42:12.780 --> 00:42:14.700 you know, that's a lot more stuff to... 00:42:14.700 --> 00:42:17.700 I didn't see it. But I'm suggesting maybe it should be added. 00:42:18.420 --> 00:42:22.980 One thing Mike could look at, there's a lot of, like I was mentioning, a lot of scripts in here. 00:42:23.760 --> 00:42:27.960 You may or may not want this, but you're using packages.writeScript, which is great. 00:42:28.240 --> 00:42:33.640 There is also write shell application, which kind of just does, 00:42:33.740 --> 00:42:34.480 like, a little more stuff. 00:42:34.480 --> 00:42:38.780 Like in particular, there's one of these scripts in here where Mike is manually 00:42:38.780 --> 00:42:43.680 setting like a bunch of path stuff and exports and bash set dash EU. 00:42:43.980 --> 00:42:48.780 And if you use write shell application, it kind of sets some decent bash stuff for you. 00:42:48.940 --> 00:42:52.820 And it even runs shell check automatically to like make sure you're not doing 00:42:52.820 --> 00:42:55.900 anything bad or half broken in a bash script for you. 00:42:56.000 --> 00:42:57.180 Well, now you tell me. 00:42:57.620 --> 00:43:00.280 It's not always what you want, right? Sometimes you want something more minimal 00:43:00.280 --> 00:43:02.760 and that might be what's going on here. I'm not trying to say he's doing anything 00:43:02.760 --> 00:43:06.780 wrong or anything, more just say, hey, this exists if it is more convenient for you. 00:43:07.926 --> 00:43:10.126 I do like, though, like, I don't know if you noticed, like, okay, 00:43:10.206 --> 00:43:14.166 we're installing some stuff, but we're even taking the time to make a extra 00:43:14.166 --> 00:43:18.166 little desktop icon and desktop item for Zoom so that it, 00:43:18.426 --> 00:43:22.046 like, it can, I guess it's installed by a flat pack, but this makes sure that 00:43:22.046 --> 00:43:26.046 you get, like, a nice little Nix native integration for it, which is a nice touch. 00:43:26.406 --> 00:43:29.206 You can actually declare that .desktop file. You don't actually have to have 00:43:29.206 --> 00:43:30.706 a bash script creating that .desktop file. 00:43:30.806 --> 00:43:32.926 Oh, it is. It's not a bash script. It's like a Nix native. 00:43:33.066 --> 00:43:35.326 Oh, okay. Okay. All right. I thought you were saying it was a bash script. 00:43:36.306 --> 00:43:37.666 All right. That's pretty good, then. 00:43:38.146 --> 00:43:41.126 I'm feeling pretty good. Brent, how are you feeling going over this? 00:43:41.606 --> 00:43:44.746 I mean, it looks great. It's evolved quite a bit since the last time I looked 00:43:44.746 --> 00:43:46.486 at this quite several months ago. 00:43:46.926 --> 00:43:50.186 One thing I'm noticing that I didn't notice before is another script, 00:43:50.346 --> 00:43:53.886 of course, but this one's called Power Wash. Have you seen this one? 00:43:54.766 --> 00:43:55.166 Yeah. 00:43:55.166 --> 00:43:58.726 I think it does exactly what you probably think it does, which is just cleans 00:43:58.726 --> 00:44:00.546 that system in every way you could think. 00:44:00.626 --> 00:44:05.666 But he's making some, like, custom directories here and just kind of bringing 00:44:05.666 --> 00:44:09.406 the system back to an original factory state. 00:44:09.886 --> 00:44:14.186 And that might be nice for this kind of system because it could get passed from 00:44:14.186 --> 00:44:17.986 one user to another as people are done with the system. 00:44:18.146 --> 00:44:20.206 And they think, wow, this was great for me. I could give it to, 00:44:20.346 --> 00:44:25.106 I don't know, my granddaughter or a friend, something like that. So good thinking there. 00:44:25.286 --> 00:44:28.526 I'm sure he uses it when he's setting these things up quite a lot. 00:44:28.846 --> 00:44:32.986 I would like Mike to write back in and tell us where this goes in two years. 00:44:33.966 --> 00:44:39.366 Because if you think about maybe a little bit of metrics or observability and 00:44:39.366 --> 00:44:46.866 if you were to build a sprinkle of flakes and you were to build a little bit 00:44:46.866 --> 00:44:48.406 of support services around this, 00:44:48.546 --> 00:44:51.366 a guy could have a pretty good second income stream. Yeah. 00:44:52.568 --> 00:44:56.788 Obviously, they're a sponsor of the show, but I almost wonder if this wouldn't 00:44:56.788 --> 00:45:01.308 be the perfect use case for Nebula to provide the back end securely in a way 00:45:01.308 --> 00:45:03.228 that wouldn't be too hard to manage. 00:45:03.748 --> 00:45:07.368 And you could provide through that all of the things I just talked about, 00:45:07.468 --> 00:45:10.548 the observability, the monitoring, but you could also offer secure backups, 00:45:10.608 --> 00:45:11.808 assuming you wanted to get into this. 00:45:12.808 --> 00:45:15.608 You could offer more proactive monitoring if you wanted to get into that. 00:45:15.768 --> 00:45:18.968 And you could even offer like a NextCloud quote unquote secure storage that 00:45:18.968 --> 00:45:20.228 never touches the public Internet. 00:45:20.988 --> 00:45:24.608 You know, it goes from their machine over Nebula to your hosted infrastructure. 00:45:25.468 --> 00:45:28.368 I don't know if you ever want to take it that direction, but I feel like when 00:45:28.368 --> 00:45:31.028 you're getting to this amount of systems, you're going to have people that their 00:45:31.028 --> 00:45:34.128 work depends on this and they might actually be looking for that kind of support. 00:45:36.168 --> 00:45:40.088 I'm a little concerned about the channel stuff. I will just be honest with you. 00:45:40.148 --> 00:45:43.488 I just think that's going to be tricky. And then if you combine that without 00:45:43.488 --> 00:45:48.068 kind of staged rollouts or the observability of failed updates, 00:45:48.068 --> 00:45:53.308 that to me is hard to make it a five out of five, even though I love this idea, 00:45:53.568 --> 00:46:00.668 a five out of five, I'm, I'm leaning for, but I could be talked out of it if 00:46:00.668 --> 00:46:02.128 the committee has a different opinion. 00:46:02.288 --> 00:46:06.048 No, I think four is reasonable. Also, we've got cinnamon, but there's no hyperland 00:46:06.048 --> 00:46:08.808 option. So I don't think it's ready for you to use it. So that's probably where 00:46:08.808 --> 00:46:10.208 some of your motivations coming from. 00:46:12.988 --> 00:46:14.508 It's such a cool project, though. 00:46:14.848 --> 00:46:18.108 Oh, it really is. And you can tell how scrappy and just, like, 00:46:18.888 --> 00:46:22.708 how far Mike has gotten this to work, how reliable it seems to be. 00:46:22.828 --> 00:46:25.188 I mean, like, and really, if you look at it, right, like, it's not even 300 00:46:25.188 --> 00:46:27.168 lines of stuff in this file. 00:46:27.328 --> 00:46:32.988 Like, it's not super complicated. It's not a crazy thing to try to maintain. I'm very impressed. 00:46:33.308 --> 00:46:37.068 Well done. All right. So, Radek comes in with his configuration. 00:46:37.068 --> 00:46:41.648 He says it's a complete production-ready Nix OS configuration for self-hosting 00:46:41.648 --> 00:46:45.448 20-plus services with enterprise-grade security, automated backups, 00:46:45.688 --> 00:46:47.808 and zero-trust networking. 00:46:48.228 --> 00:46:53.628 Perfect for home lab enthusiasts, privacy-conscious users, and anyone wanting 00:46:53.628 --> 00:46:56.288 to self-host their digital life with minimal maintenance. 00:46:57.128 --> 00:46:59.008 Disclaimer, the entire project was Vibe-engineered. 00:47:00.008 --> 00:47:05.628 Well, one way you can tell, I don't know if it's better or worse than the one you have in YouR Repo. 00:47:06.108 --> 00:47:06.888 Oh, here we go. 00:47:07.068 --> 00:47:11.188 Well, I don't know if you noticed, there's a file in here that almost looks like a command. 00:47:11.848 --> 00:47:13.628 Yeah, I love that. That's a good sign. 00:47:13.908 --> 00:47:14.148 Yeah. 00:47:14.888 --> 00:47:17.508 That Udo one there, Udo-U Postgres. 00:47:17.528 --> 00:47:19.768 I think it might have been sudo to start with, but... 00:47:19.768 --> 00:47:19.968 Yeah. 00:47:20.168 --> 00:47:20.368 Yeah. 00:47:20.528 --> 00:47:22.728 Yeah. Yeah. That's good stuff. That was just yesterday, too. 00:47:22.848 --> 00:47:25.468 So that's easily two stars just right there for that. 00:47:26.348 --> 00:47:27.468 Oh, okay. 00:47:27.468 --> 00:47:29.908 No, no, I don't. I mean, in a good way. I'm going like adding stars on, 00:47:30.088 --> 00:47:31.288 right? That's the baseline. 00:47:31.708 --> 00:47:35.688 All right. Okay. I mean, let's talk about what's going on here. 00:47:35.968 --> 00:47:38.628 Holy crap. 20 plus services. He's not kidding. 00:47:39.168 --> 00:47:42.788 And I see some of my favorites in there, my favorite RARs and my Jellyfin. 00:47:42.988 --> 00:47:45.728 I love what I'm seeing there. He's got an architecture diagram. 00:47:46.248 --> 00:47:52.008 Oh, yeah. He's pulling in Azure for backups and DNS management to handle all of that. 00:47:52.268 --> 00:47:55.748 And I believe, I'm not positive, but I'd like your eyes on this, Wes. 00:47:55.868 --> 00:47:59.908 I think instead of installing Postgres like 20 times and Redis 10 times, 00:48:00.068 --> 00:48:03.488 he's got one instance of Postgres and one instance of Redis. 00:48:03.828 --> 00:48:05.688 And then everything's configured to use... 00:48:06.901 --> 00:48:10.661 Which is something you don't often see on people's Docker home labs. 00:48:10.801 --> 00:48:14.901 You'll often see five copies of Postgres running on somebody's system, 00:48:14.901 --> 00:48:16.621 and he solved that problem. 00:48:16.801 --> 00:48:19.141 It does make it a central point of failure, obviously. 00:48:19.501 --> 00:48:25.801 Yeah, pros and cons, but you don't actually need separate servers depending on what you're doing. 00:48:25.941 --> 00:48:27.121 So my man, I like that. 00:48:27.121 --> 00:48:28.961 Yeah, there's a lot of stuff in here. 00:48:29.961 --> 00:48:33.041 He's got weekly automatic backups, which is really great. 00:48:33.041 --> 00:48:40.081 I would challenge him to consider adding file system snapshots before his automatic 00:48:40.081 --> 00:48:45.241 updates and, you know, just have an extra or maybe kick off his automatic because 00:48:45.241 --> 00:48:46.121 he has automated backups. 00:48:46.621 --> 00:48:50.221 Maybe run that job right before you do your automatic updates. 00:48:50.441 --> 00:48:53.901 So that way you have a really nice, fresh point in time if something does go wrong. 00:48:54.241 --> 00:48:58.801 I'm impressed. The integration with SOPs, especially for a vibe coded setup. 00:49:00.001 --> 00:49:05.221 You know like getting i think getting secrets tying that together uh not leaking 00:49:05.221 --> 00:49:09.661 secrets into your repo that's yeah that is all stuff that takes time and fiddling 00:49:09.661 --> 00:49:12.881 and fuss to really validate he's. 00:49:12.881 --> 00:49:17.101 So he's got the r stack broken out audio bookshelf you know every major service 00:49:17.101 --> 00:49:20.541 like next cloud and jellyfin and image are all broken out into their own nix file. 00:49:20.541 --> 00:49:25.561 A pretty pragmatic balancing here of native nix os services as well as a lot 00:49:25.561 --> 00:49:30.641 of containers right so like here's um SearchXNG and OpenWebUI, 00:49:30.641 --> 00:49:32.161 both running as OCI containers, 00:49:32.921 --> 00:49:35.581 which is great because I think sometimes it's easy to forget that, 00:49:35.581 --> 00:49:38.161 you know, you don't have to, you can pick and choose. 00:49:38.341 --> 00:49:41.081 Like, use the Nix module if you want, run it in a container, 00:49:41.541 --> 00:49:45.801 either, you know, imperatively or declaratively. It all works great. So do what works for you. 00:49:46.121 --> 00:49:49.481 I may be aping some of this R stack. This is looking really good. 00:49:49.781 --> 00:49:51.161 I do like to see all of this. 00:49:51.541 --> 00:49:54.381 Like, I don't know if this was a deliberate choice or not, but, 00:49:54.561 --> 00:49:57.881 for instance, image is being run as a container, not through the module. 00:49:58.401 --> 00:49:59.081 Yeah. Yeah. 00:50:00.479 --> 00:50:04.759 Yeah, I wonder, and I bet you that is. I wonder if there's any hardware acceleration issues there. 00:50:05.259 --> 00:50:07.999 Probably not. I'm sure he's probably safe. Solve that. 00:50:08.279 --> 00:50:12.639 I would say, like, if you wanted, like, to unlock, like, the next level of cool 00:50:12.639 --> 00:50:17.239 for this setup would be automated restore testing into, like, 00:50:17.319 --> 00:50:20.659 a, you know, a stupid container or a throwaway VM. 00:50:21.199 --> 00:50:22.819 Because you're doing the automated backups. 00:50:23.639 --> 00:50:26.459 How do you know they work? Wouldn't that be something if you could vibe that 00:50:26.459 --> 00:50:31.259 up where once a month or something, you do a restore from your last backup? 00:50:31.459 --> 00:50:32.239 Oh, that'd be killer. 00:50:32.559 --> 00:50:36.139 And see if it actually works. Because that's, I love that you have all this. 00:50:36.439 --> 00:50:38.759 I verified you're backing up your app data. 00:50:39.239 --> 00:50:41.979 I'm pretty sure. I assume you're backing up your Postgres and your Redis. 00:50:42.199 --> 00:50:44.739 I would imagine if you're running 20 databases on those things. 00:50:44.979 --> 00:50:48.379 I didn't see you ever testing it. And that could be something you're doing manually, obviously. 00:50:48.839 --> 00:50:52.079 But why not give a shot at automating that? You're so close. 00:50:52.259 --> 00:50:53.479 You're so close with everything. 00:50:54.179 --> 00:50:58.219 I don't want to do like grading on a curve, but for a vibe set up, 00:50:59.644 --> 00:51:01.744 This is pretty top-notch for a vibe setup. 00:51:02.064 --> 00:51:06.124 There's another one we're going to see in this category as we go on here. 00:51:06.284 --> 00:51:09.044 And, you know, just with our recent episodes and everything else, 00:51:09.184 --> 00:51:13.544 it does, boy, are we at a point for vibing with Nix OS. 00:51:13.804 --> 00:51:17.024 It's really come a long way, which is great. I mean, it's just a superpower. 00:51:17.304 --> 00:51:22.404 I will say you might consider getting your vibe tool to add an auto-formatter. 00:51:22.684 --> 00:51:25.824 I notice nothing crazy, but just like in your flake, there's some stuff where 00:51:25.824 --> 00:51:28.624 some of the indentation and stuff, which doesn't break anything because it's 00:51:28.624 --> 00:51:32.644 nix not python or yaml or whatever but should be something easy for it to do 00:51:32.644 --> 00:51:36.904 to be able to you know easily format and keep everything looking pretty for you and. 00:51:36.904 --> 00:51:40.444 I also think this is why i'm not sure i want to give it a five out of five because 00:51:40.444 --> 00:51:43.384 i think there might be some dock drift which is really easy when you're moving, 00:51:43.984 --> 00:51:49.844 i do like your architecture diagram though oh this is a really tough one this is really. 00:51:49.844 --> 00:51:52.484 Yeah that is one thing you kind of have to balance too is it's really easy to 00:51:52.484 --> 00:51:55.524 get the llm to spew out a lot of the docs but. 00:51:55.524 --> 00:51:56.224 Then they drift. 00:51:56.224 --> 00:51:59.824 Keeping them keeping them up to date is a whole other challenge and so sort 00:51:59.824 --> 00:52:02.704 of like which ones are essential for like i really do want this and this is 00:52:02.704 --> 00:52:05.804 going to help me continue to build and which of these are like just dead weight 00:52:05.804 --> 00:52:09.344 that i ultimately got to carry around and i could rediscover easily yeah. 00:52:09.344 --> 00:52:12.144 I think he's got like some code examples that reference like old versions of 00:52:12.144 --> 00:52:14.964 stuff in there i mean there's just a little bit of drift so i don't know if 00:52:14.964 --> 00:52:18.664 it's a five out of five but i feel like it could be a four out of five again 00:52:18.664 --> 00:52:24.144 i mean we're being pretty generous i i don't know i think some people would knock it down. 00:52:24.144 --> 00:52:27.364 Yeah, we'll give Claude one star, and then the rest of the config gets four. 00:52:27.544 --> 00:52:31.604 Okay. All right. There you go. There you go. But better than I would have thought. 00:52:32.384 --> 00:52:34.024 I got to say, Reddick, better than I would have thought. 00:52:35.633 --> 00:52:41.513 Well done. And nicely done on focusing on a home lab with all of the essential 00:52:41.513 --> 00:52:44.113 great home lab services. 00:52:44.693 --> 00:52:48.453 Somebody listening, even if you're not interested in deploying all of this, 00:52:48.533 --> 00:52:51.813 you might want to just look through his config and get some ideas for some great home lab services. 00:52:52.633 --> 00:52:56.433 They're really good. All right. We're about to round it out. 00:52:56.573 --> 00:52:59.433 And one of our last ones comes from Brandon W. 00:52:59.753 --> 00:53:03.533 He says, I've slowly been migrating my computing life to declarative configurations. 00:53:03.533 --> 00:53:07.913 As part of that, I've switched my Mac to Nix Darwin, as well as my Homelab to 00:53:07.913 --> 00:53:09.393 Docker Compose and Nix OS. 00:53:09.773 --> 00:53:14.273 I just finished Nix OS this weekend on two of the four hosts and only locked 00:53:14.273 --> 00:53:15.773 myself out of SSH three times. 00:53:17.233 --> 00:53:21.493 Hey, under five. I've done. See? Star for that. Boom. 00:53:22.053 --> 00:53:27.833 Star for that. All right. All right. I wanted to send in my infra repo and my 00:53:27.833 --> 00:53:30.013 Nix Darwin configs for the config confessions. 00:53:30.573 --> 00:53:33.853 I'm most proud of my HomeLab deployment system using Ansible playbooks, 00:53:33.973 --> 00:53:39.513 1Password for secrets, Just, GitHub actions, and the Renovate bot for updates. 00:53:39.693 --> 00:53:42.253 Any suggestions would be appreciated, and howdy's from Texas. 00:53:42.833 --> 00:53:47.453 So yeah, he sent us two configs, the HomeLab and the Mac. So why don't we start 00:53:47.453 --> 00:53:49.153 with looking at the old HomeLab? 00:53:49.313 --> 00:53:51.653 I do like that. He's broken them out like that. 00:53:52.213 --> 00:53:56.133 Also, he was committing as of this morning when I was checking in on this. 00:53:56.613 --> 00:53:58.313 Inactive development. I love that. 00:54:00.788 --> 00:54:04.328 He's got his hosts broken out here. He's got an explanation of his tail scale 00:54:04.328 --> 00:54:06.108 and Ansible setup and secrets management. 00:54:06.328 --> 00:54:09.748 I don't see a quick getting started, but this is pretty solid documentation. 00:54:10.388 --> 00:54:14.668 You know, description of the home lab systems, the Linode. And I do like this. 00:54:14.788 --> 00:54:15.968 So this is winning a point with me. 00:54:16.308 --> 00:54:20.508 He's running a Linode exit node to forward certain critical, 00:54:20.788 --> 00:54:24.548 as he puts it, mission critical data through this Linode exit node. 00:54:24.708 --> 00:54:26.928 Love seeing that setup. That's worked really well for us too. 00:54:27.468 --> 00:54:30.888 Yeah, you can tell there's a lot. i like seeing a polygot repo 00:54:30.888 --> 00:54:33.588 like this right like there's a lot of stuff working together there's obviously 00:54:33.588 --> 00:54:38.008 nick stuff that we'll be taking a look at but also as you mentioned right we've 00:54:38.008 --> 00:54:41.568 got ansible playbooks and part of what that's doing is deploying a bunch of 00:54:41.568 --> 00:54:45.768 composed yaml files that are also in here that look really nice i mean yeah 00:54:45.768 --> 00:54:48.608 pretty well you know traffic uptemp kuma, 00:54:49.308 --> 00:54:53.268 portainer uh we got bind running like there's just there's a lot of serious 00:54:53.268 --> 00:54:56.708 networking thought that has gone into this, which is great. 00:54:58.508 --> 00:55:03.548 I think you hear that, Brandon. I think he's impressed. I think he likes it. 00:55:03.608 --> 00:55:04.888 I love seeing Image in there. 00:55:06.244 --> 00:55:09.424 Docker with traffic and using tags, it looks like. 00:55:09.704 --> 00:55:13.184 Did you notice that there's two separate domains that get routed with custom 00:55:13.184 --> 00:55:16.744 split DNS servers? There's a personal services one and the family one. 00:55:17.244 --> 00:55:19.044 He's got the split brain DNS. 00:55:19.644 --> 00:55:20.204 Fancy. 00:55:20.544 --> 00:55:21.704 But the good kind. 00:55:21.944 --> 00:55:25.864 I have an observation and question here. In the NixOS folder, 00:55:25.884 --> 00:55:27.904 I'm seeing a hardware configuration.nix. 00:55:27.944 --> 00:55:33.624 It was under my impression that you generally didn't want to version track that 00:55:33.624 --> 00:55:36.044 because it's being created. 00:55:36.244 --> 00:55:37.644 On each system independently. 00:55:38.324 --> 00:55:39.924 What are your thoughts on that, Wes? 00:55:40.384 --> 00:55:42.164 I mean, you can recreate it. I think 00:55:42.164 --> 00:55:46.464 if you do track it, there's nothing necessarily wrong with tracking it. 00:55:46.524 --> 00:55:50.024 You just need to know that, like only deploy it to the ones that are relevant 00:55:50.024 --> 00:55:54.424 and then it's on you to make sure that you update it if you are actually changing 00:55:54.424 --> 00:55:55.224 something with your hardware. 00:55:55.684 --> 00:55:56.584 Mm, fair enough. 00:55:57.464 --> 00:56:03.284 All right, so where Brandon scores a W with me is on the Mac stuff, surprisingly. 00:56:03.624 --> 00:56:06.704 He's got a command to get started right at the top of the readme. 00:56:06.904 --> 00:56:10.104 You know, so you get a new Mac or you reinstall macOS, you're not spending 10 00:56:10.104 --> 00:56:11.684 minutes, you're copying and pasting. 00:56:12.064 --> 00:56:16.204 That's a W. I know this is how it works on macOS, but it's just funny to me 00:56:16.204 --> 00:56:17.784 to see brew defined by Nix. 00:56:18.324 --> 00:56:24.184 You know, it's funny. But then what was even crazier to me was to see the Mac apps. 00:56:24.324 --> 00:56:26.364 I'm going to link this in the show notes specifically if people want to see 00:56:26.364 --> 00:56:31.064 this because it's just bonkers to see Mac apps getting installed by Nix. 00:56:31.784 --> 00:56:34.544 Chromium, Discord, Spark, Notion. 00:56:35.524 --> 00:56:42.164 Spotify, Visual Studio Code, Xcode. Huh, you can install Xcode with Nix. 00:56:44.006 --> 00:56:48.186 Would you even believe it? So that to me is the first time I've ever actually seen that. 00:56:48.286 --> 00:56:53.346 I know people, like our buddy Alex does this, but I never really dug through the config. 00:56:53.566 --> 00:56:54.866 It is pretty great what you can do. 00:56:55.006 --> 00:56:56.446 You can disable the DS stores. 00:56:56.866 --> 00:57:00.466 Yeah, right. It's one of those things where it's like, boy, I hope I don't need 00:57:00.466 --> 00:57:03.886 to do this again, but it is probably exactly what I would end up doing where 00:57:03.886 --> 00:57:05.286 I forced back onto that platform. 00:57:05.606 --> 00:57:09.286 So it's great having these in our tool chest to pull from in the future also. 00:57:09.926 --> 00:57:13.486 I'm amazed Mac OS lets you do some of this. You can set keybinds through Nix 00:57:13.486 --> 00:57:16.326 in macOS. You can set macOS keybinds. 00:57:17.606 --> 00:57:20.686 What a world. Talk about making the Mac way more manageable. 00:57:21.066 --> 00:57:24.946 So that, to me, brought this up a couple of points right there because it's well done. 00:57:26.146 --> 00:57:29.726 He's got the quick get started stuff. You know how I love that. 00:57:32.206 --> 00:57:38.266 Overall, it's the most interesting in that it's x86, it's M-Series Mac, 00:57:38.546 --> 00:57:41.706 it's Ansible, it's Nix, and it's Docker Compose. 00:57:42.746 --> 00:57:46.626 In all in one, and yet it seemingly is working really well together, 00:57:46.626 --> 00:57:51.306 and he's got not only individual workstations, but he's got a home lab setup out of it, too. 00:57:52.226 --> 00:57:53.846 So it sucks. I say one star. 00:57:56.986 --> 00:57:59.766 Too much non-mix, negative points. 00:58:00.066 --> 00:58:00.506 Right. 00:58:00.966 --> 00:58:04.486 We're going to actually ask, we're going to flag this at GitHub so they can delete it for us. 00:58:04.686 --> 00:58:06.886 Bro, was it even vibes? Bro, you know. 00:58:07.366 --> 00:58:10.286 Yeah, thoughtful, long-term development and use. 00:58:10.466 --> 00:58:13.766 Yeah, yeah. Yeah. Was committed. You were still working on it this morning as 00:58:13.766 --> 00:58:14.646 we're prepping the show. 00:58:15.226 --> 00:58:18.526 Okay. So I think when you think of it's a five out of five, I think this is a five out of five. 00:58:19.246 --> 00:58:21.266 So this is our first five out of five for the second segment, 00:58:21.266 --> 00:58:23.606 but I think, I think it's fair. It goes to Brandon. 00:58:24.586 --> 00:58:27.826 It's really neat. It's really neat to see the home lab and the Mac all broken 00:58:27.826 --> 00:58:32.026 out using, you know, some of our favorite apps, some of our favorite technology stacks. 00:58:32.726 --> 00:58:34.286 Well done, sir. Five out of five. 00:58:36.730 --> 00:58:40.970 All right, gentlemen, and our last config confession came in just last night 00:58:40.970 --> 00:58:45.050 from Bearded Tech, and he has Vibe-coded a NixOS router. 00:58:45.270 --> 00:58:49.150 He says it's a declarative NixOS configuration that transforms a standard PC 00:58:49.150 --> 00:58:53.650 into a full-featured network router with integrated secrets management. 00:58:54.250 --> 00:58:58.250 And it has multiple WAN types. It supports, obviously, being a DHCP server. 00:58:58.390 --> 00:58:59.850 It can be a PPOE server if you need. 00:59:00.530 --> 00:59:04.550 It also has PPTP support, LAN bridging to combine multiple Ethernet ports into 00:59:04.550 --> 00:59:08.870 one network. It has a DNS server, DHCP, obviously a firewall with NAT support, 00:59:09.030 --> 00:59:13.750 and then in their port 40, and like he said, secret management as well. 00:59:14.070 --> 00:59:20.670 But the thing that is really impressive is Bearded Tech has made this so approachable 00:59:20.670 --> 00:59:25.490 for anybody that just wants to take a PC and turn it into a NixOS router. 00:59:26.150 --> 00:59:31.770 He did the right thing, and he just put a curl right into Pseudo Bash in the 00:59:31.770 --> 00:59:34.310 quick start, and you can just get rocking. And you know how we, 00:59:34.410 --> 00:59:37.390 you know, always suggest you do that. Of course, I'm being ironic. 00:59:37.530 --> 00:59:39.930 But if you trust the person, he does actually tell you everything it's going to do in there. 00:59:40.750 --> 00:59:44.650 But you boot from the NixOS installer and then you just run this command. 00:59:45.690 --> 00:59:49.730 And it does everything else. And then the other thing he thought of, 00:59:49.910 --> 00:59:53.790 because this is how it is in router life, is if you come back to one of these 00:59:53.790 --> 00:59:57.230 boxes you've deployed two years down the road and it's all decrepit and out 00:59:57.230 --> 00:59:59.890 of date, he's got a quick refresher command. 01:00:00.710 --> 01:00:05.890 And you, again, slam that thing right into sudo bash and you've got a completely 01:00:05.890 --> 01:00:08.370 refreshed router. Good to go again. 01:00:09.030 --> 01:00:12.430 He's got documentation for the individual setup guide, router config, 01:00:12.630 --> 01:00:14.270 secrets management, troubleshooting the development. 01:00:14.930 --> 01:00:19.070 He tells you what you need. I mean, this is top notch. 01:00:19.290 --> 01:00:23.810 This is really a great idea, especially because I want to run a Nix OS router here at the studio. 01:00:24.070 --> 01:00:27.230 How do you feel about a vibe coded router though, Chris? 01:00:27.430 --> 01:00:27.750 Yeah. 01:00:29.490 --> 01:00:35.890 I don't love that idea. I mean, if it builds and it routes the packets, 01:00:36.830 --> 01:00:40.710 well, it's not like he's going to vibe like a backdoor into it, right? I mean, it's how. 01:00:40.710 --> 01:00:41.130 Do you know? 01:00:42.410 --> 01:00:46.970 I mean, it is one of those things that you can test it, right? 01:00:47.070 --> 01:00:50.310 Like, you know if you break it because your packets don't route anymore. 01:00:50.310 --> 01:00:53.870 To the extent that you can easily test all the stuff that your router is doing, 01:00:54.130 --> 01:00:56.270 I think it makes a pretty good use case in that sense. 01:00:56.270 --> 01:01:02.650 I don't think I see any like crazy routing stuff in terms of like custom IP 01:01:02.650 --> 01:01:05.450 tables or NF tables or anything like that. 01:01:05.590 --> 01:01:10.310 But I do see like PPOE going on and some bridges being configured. 01:01:10.450 --> 01:01:15.650 There's some nice stuff in here like router config.nix, which is just a declarative 01:01:15.650 --> 01:01:18.210 file describing the networking. I like that a lot. 01:01:18.370 --> 01:01:22.850 You might consider because if I've coded one, just impressive speed, 01:01:22.850 --> 01:01:25.970 I think it started on the 7th with the initial commit. 01:01:26.130 --> 01:01:32.270 It's the 9th as we record, and there's already been like 50-some commits or something. 01:01:32.890 --> 01:01:36.390 Although, if you're getting Vibe commits, they're kind of verbose. 01:01:36.550 --> 01:01:42.910 You might tweak your setup to follow conventional commit standards if you like that one, 01:01:42.910 --> 01:01:48.330 or just at least have a quick summary single line and then put more of the detail 01:01:48.330 --> 01:01:53.830 below just to sort of match what a lot of Git software thinks but that's like a minor minor nitpick. 01:01:53.830 --> 01:01:57.670 I was it was one of mine too it was kind of annoying looking through the and 01:01:57.670 --> 01:02:00.830 i know this problem you know they are very like just exactly what west said 01:02:00.830 --> 01:02:06.290 so i kind of agree on that and it was sort of a bit much there. 01:02:06.290 --> 01:02:10.070 It is nice so there's like a dev shell there's a formatter got sops going in 01:02:10.070 --> 01:02:11.830 here for secrets which is very forward thinking. 01:02:13.015 --> 01:02:18.375 I noticed that he recently swapped out Tectitium for Blocky DNS. 01:02:18.775 --> 01:02:20.255 I'd be curious to know more about that. 01:02:20.635 --> 01:02:23.495 Yeah, I would be curious to hear how that's working for you, 01:02:23.555 --> 01:02:25.515 which things you like or don't like about either one of them. 01:02:25.915 --> 01:02:28.595 I've looked at Blocky a little bit, although I've never actually really tried 01:02:28.595 --> 01:02:30.615 it, except like briefly. 01:02:31.835 --> 01:02:34.195 I do like that it has a lot of metrics built in, though. 01:02:34.715 --> 01:02:38.475 Yeah, and I know it also has some ad blocking and malware built in and stuff like that, too. 01:02:39.115 --> 01:02:43.395 So that's all pretty good. I don't love the way the commits. 01:02:43.515 --> 01:02:49.695 The other thing that I would love to see is I don't know how you would not pick favorites here. 01:02:51.412 --> 01:02:56.272 The VPN options are pretty 1997. You know, it's like this is, 01:02:56.512 --> 01:03:00.692 I was doing PPOE connections literally like on NT4 boxes. 01:03:01.572 --> 01:03:04.352 Not that people don't use them. I'm not saying they don't. I would also love 01:03:04.352 --> 01:03:08.812 to see some more modern options built in, you know, tail scale or a Nebula or 01:03:08.812 --> 01:03:13.092 what I would really love is some way for the user to pick. 01:03:13.632 --> 01:03:15.872 And then you just get that. Like maybe you're a network person. 01:03:15.992 --> 01:03:18.192 Maybe you're a Nebula person. And then you just go in and you say, 01:03:18.292 --> 01:03:21.152 I'm a Nebula person. And then it sets up with Nebula or whatever. 01:03:21.412 --> 01:03:27.392 Because the VPN options are, I'm never using that stuff in 2025 if I'm setting up a new router. 01:03:27.612 --> 01:03:32.412 If I am going into an organization that has a historic setup, 01:03:33.112 --> 01:03:36.992 maybe you might even call it tech debt, I can understand why they're doing it. 01:03:37.252 --> 01:03:42.192 But if I'm installing a Vibe-coded Nix OS router on my PC at home, 01:03:42.632 --> 01:03:48.312 I don't want to use PPPoE or PPTP, right? So that's just one thing I would add, maybe. 01:03:49.332 --> 01:03:53.272 I'd love to see some backups built into this too i think backups could be really good, 01:03:54.292 --> 01:04:00.172 um i mean but for like you said wes i going from zero to actual functional system 01:04:00.172 --> 01:04:05.132 in a couple of days and to have the quick start on just a you know you boot 01:04:05.132 --> 01:04:09.972 off of the nix os live system and run this script oh when you come back in a 01:04:09.972 --> 01:04:12.732 couple of years run this script to refresh it assuming that works, 01:04:14.343 --> 01:04:17.043 That's great. That's exactly what you want with this kind of stuff. 01:04:17.283 --> 01:04:21.003 I do like that, too, as a, you know, oh, no, that box died. Well, 01:04:21.163 --> 01:04:23.143 thankfully, I just run the script, clone things down. 01:04:23.363 --> 01:04:27.223 I've got my router back in, you know, 10 minutes instead of a couple of hours. 01:04:27.643 --> 01:04:30.563 All right, gentlemen, should we allow a last-minute contender in? 01:04:30.563 --> 01:04:31.203 Let's do it. 01:04:31.923 --> 01:04:37.443 Okay, all right. We've got to give Bearded Tech a score before we move on. 01:04:38.523 --> 01:04:43.463 And I'm going for, can we do points? I feel like a 3.5 or a 4. 01:04:43.463 --> 01:04:45.423 It's really close, though. 01:04:45.803 --> 01:04:49.323 I think four because there's some fancy scripts in here. 01:04:50.443 --> 01:04:53.743 All right. All right. All right, Brent, tell us about our last-minute contender 01:04:53.743 --> 01:04:54.743 that came in live on the show. 01:04:55.323 --> 01:05:00.163 Yes, we have someone in the Matrix chat, D-Drill, who said, oh, 01:05:00.303 --> 01:05:03.103 I got a config. Maybe you guys can have a look at this one. 01:05:03.943 --> 01:05:09.943 So this has been a totally fresh config for all of us. So I think we should dive in. 01:05:10.323 --> 01:05:16.223 Coming in fresh. first thing I'm noticing just right off the top well we got 01:05:16.223 --> 01:05:20.203 some systems here but I like the systems are broken into two categories do you 01:05:20.203 --> 01:05:22.743 see this Wes? you see these two categories of systems here? 01:05:24.283 --> 01:05:28.723 You got the Nix OS systems and then you have the systems that still need to 01:05:28.723 --> 01:05:31.183 be Nix there's nothing else, 01:05:32.183 --> 01:05:36.543 that's pretty good and you got the structure in here and all of that I'm also 01:05:36.543 --> 01:05:40.063 noticing just a couple of things is pretty recent commits, 01:05:41.962 --> 01:05:47.022 As of 29 minutes ago, actually, that's what are you are you listening to the show or not? 01:05:48.022 --> 01:05:49.482 It's so organized. 01:05:49.662 --> 01:05:50.242 I am. 01:05:50.622 --> 01:05:54.062 He's in the mumble room. So you're in the mumble room. 01:05:54.202 --> 01:05:55.782 Do you want to just tour us through here? 01:05:55.982 --> 01:05:57.782 Yeah. Tell us about your system. Yeah. Why not? 01:05:58.302 --> 01:06:07.082 Sure. So the most recent commits there, I made a quick read me update and flake lock action update. 01:06:07.862 --> 01:06:14.202 So if you basically jump back to the root, I essentially have things broken out. 01:06:15.102 --> 01:06:22.362 I attempted to recently do a major refactoring and make things a lot more modulized, 01:06:22.822 --> 01:06:24.922 modularized, however you say it. 01:06:25.082 --> 01:06:25.182 Right. 01:06:25.722 --> 01:06:30.042 But basically, I got hosts. Right now, I'm purely running NixOS. 01:06:30.042 --> 01:06:32.422 I don't have any Macs. But... 01:06:33.117 --> 01:06:36.857 Basically, in the host, under NixOS, I have the different configs. 01:06:36.957 --> 01:06:41.197 I have a couple special... Actually, if you want to look at the modules, 01:06:41.757 --> 01:06:48.097 there is a host spec module that I have borrowed from someone else I found online 01:06:48.097 --> 01:06:49.477 and then tweaked it to my own needs. 01:06:50.717 --> 01:06:52.877 I want to say it's actually right in the root there. 01:06:53.157 --> 01:06:55.017 Yeah, this host spec.nix there, huh? 01:06:55.137 --> 01:06:59.517 Yeah, so basically that creates a host spec and then creates just a bunch of 01:06:59.517 --> 01:07:00.917 variables that you can call throughout. 01:07:00.917 --> 01:07:05.117 This file is actually imported within 01:07:05.117 --> 01:07:09.397 each host so i can reuse a lot of the same variables without messing up any 01:07:09.397 --> 01:07:15.737 other hosts itself but starts off just with some basic specifying primary username 01:07:15.737 --> 01:07:19.537 a secondary username it's basically just myself and then a couple of the systems 01:07:19.537 --> 01:07:21.217 are also used by my wife gotta. 01:07:21.217 --> 01:07:23.037 Make sure you get a llama installed i see that. 01:07:23.037 --> 01:07:27.117 You know i have a couple you know i break it down if it's a workstation it adds 01:07:27.117 --> 01:07:31.837 a desktop interface to it if it's gaming it does another layer on top of that 01:07:31.837 --> 01:07:35.477 um couple services specified there i. 01:07:35.477 --> 01:07:40.297 Really like this i mean i'm coming in fresh but what i'm seeing i really like 01:07:40.297 --> 01:07:45.497 the way you have the modules workstation laid out the audio.nix the bluetooth.nix 01:07:45.497 --> 01:07:49.477 the fonts.nix nvidia.nix this is really well structured. 01:07:49.477 --> 01:07:53.897 Quite a lot of helpers here in the just file too like it shows you're you're 01:07:53.897 --> 01:07:57.077 definitely using this stuff and maintaining it and you've you've got commands 01:07:57.077 --> 01:08:00.757 that you actually need to run and have helpfully stashed them away, which is nice. 01:08:00.977 --> 01:08:05.177 Yeah, I borrowed that off from someone else. And honestly, I need to go through 01:08:05.177 --> 01:08:08.637 it and use it a lot more because I really don't use just the way that I should. 01:08:08.837 --> 01:08:12.377 I was curious about one of these here. I'm not sure if you're using it currently, 01:08:12.377 --> 01:08:15.977 but you have a just command for creating an ISO. 01:08:16.277 --> 01:08:19.477 It says build an ISO image for installing new systems and create a sim link 01:08:19.477 --> 01:08:23.777 for QEMU usage. Is that something you're using actively? And if so, how'd it go? 01:08:24.117 --> 01:08:28.637 I have not built that in yet. So that was actually a carryover. 01:08:28.837 --> 01:08:30.737 I've got to give credit to Emergent Mind. 01:08:31.790 --> 01:08:38.530 On that because that's part of what i had ripped off of him so it's an intention 01:08:38.530 --> 01:08:45.690 that i plan on going uh basically building a minimal iso that i can use for spinning up new systems, 01:08:46.470 --> 01:08:49.590 it'll already have some of the basic tools that i want in it rather than having 01:08:49.590 --> 01:08:54.090 to use the customer installer all the time because realistically with the with 01:08:54.090 --> 01:08:58.670 nyx if you have a config all you to do is get into a system that has nix on 01:08:58.670 --> 01:09:05.630 it whether it be a minimal iso or whatever grab your flaco to github and let it build yeah. 01:09:05.630 --> 01:09:10.910 Yeah exactly right well good the fact that you haven't used everything makes 01:09:10.910 --> 01:09:14.890 this like a real person's config because before it was almost suspiciously good so yeah. 01:09:14.890 --> 01:09:20.230 Yeah yeah okay and the raspberry pi that's on the to-do list for 2016 huh. 01:09:20.230 --> 01:09:22.410 From 2016 yeah. 01:09:22.410 --> 01:09:25.790 So I'm noticing. So not done? 01:09:26.230 --> 01:09:30.490 Well, it's my Raspberry Pi 3. I have my 4 already Nixified. 01:09:30.930 --> 01:09:34.590 So it's just a matter of actually going down in the basement, 01:09:34.790 --> 01:09:41.450 grabbing it, and putting the image on the SD card, which sounds simple enough, but it's a timing. 01:09:41.650 --> 01:09:45.650 No, no. I've got a couple from 2016. I'm going to get this running, 01:09:45.810 --> 01:09:48.290 too, on my project list. So I totally understand. 01:09:48.910 --> 01:09:53.370 But I feel like this is a top-tier setup. up even if it's not fully implemented 01:09:53.370 --> 01:09:58.290 it's well done it's well thought out it's well structured i mean do we have 01:09:58.290 --> 01:09:59.290 a reason not to give this a five 01:09:59.290 --> 01:10:03.210 out of five i defer to the committee but that's the way i'm inclined i. 01:10:03.210 --> 01:10:04.090 Thought we were going six. 01:10:04.090 --> 01:10:06.530 Oh whoa can we do that. 01:10:06.530 --> 01:10:10.590 For you know for the very last one i think we have to. 01:10:10.590 --> 01:10:13.110 Brent you'd have to co-sign i. 01:10:13.110 --> 01:10:15.990 Mean are there even rules at this contest i say go for it. 01:10:15.990 --> 01:10:19.630 All right there we go six out of five i don't know how that's possible. 01:10:21.810 --> 01:10:27.070 If you want to take a look at that lib, one of the cool things that I saw on 01:10:27.070 --> 01:10:32.850 someone else's config and borrowed is actually an importing method for those files. 01:10:33.010 --> 01:10:33.210 Okay. 01:10:33.710 --> 01:10:36.690 So without being able to rip through it often enough. 01:10:36.890 --> 01:10:40.870 So I actually have in there, I have a relative to root, I have a scan paths 01:10:40.870 --> 01:10:45.590 and a recursively import that I just recently did. 01:10:45.590 --> 01:10:50.070 I haven't built that out yet to actually utilize it in many places. 01:10:50.070 --> 01:10:57.650 But the scan paths or the relative to root is realistically kind of one of the key pieces I use. 01:10:57.790 --> 01:11:00.430 So if you actually go back into the modules and look at any of those default 01:11:00.430 --> 01:11:04.210 files, I'm sorry, those actually all use the scan path. 01:11:04.350 --> 01:11:09.790 So I'm not actually specifying all of those files by default. I'm specifying. 01:11:11.370 --> 01:11:15.150 So, I mean, even that default nix there, I'm pretty sure has it in. 01:11:15.410 --> 01:11:18.510 But when I'm importing, I'm basically doing a one line importer. 01:11:18.510 --> 01:11:21.570 Yeah third line or line 11 01:11:21.570 --> 01:11:26.630 out of there scan paths dot so and then that function has built into it filtering 01:11:26.630 --> 01:11:31.970 out to directories and dot nix files and then within each directory has a default 01:11:31.970 --> 01:11:37.690 dot nix that would run the same scan paths file again or line again and it would 01:11:37.690 --> 01:11:40.710 import all of the files that are adjacent to that that. 01:11:40.710 --> 01:11:45.250 Is great so you've got custom nix lib that see i stand by my six out of five for sure. 01:11:47.750 --> 01:11:48.150 All right. 01:11:48.210 --> 01:11:50.130 I mean, I figured if you were going to give me a six, I had to, 01:11:50.170 --> 01:11:51.850 you know, throw some extra little. 01:11:52.030 --> 01:11:55.630 You know. Well, and you know what? You didn't even, because we were impressed 01:11:55.630 --> 01:11:58.190 so much, you didn't even get docked for missing the deadline, 01:11:58.230 --> 01:11:59.450 which we didn't really set a deadline. 01:12:00.290 --> 01:12:03.170 I was going to say, I sent it, I technically sent it in Friday night. 01:12:03.290 --> 01:12:04.410 Oh, okay. Oh, okay. 01:12:04.550 --> 01:12:06.190 All right. Through the Linux Unplugged website. 01:12:06.350 --> 01:12:10.270 I see. I see how it is. All right. Well done. And we will link to these configs 01:12:10.270 --> 01:12:12.290 in the show notes if you want to get some ideas for yourself. 01:12:19.804 --> 01:12:23.864 Unraid.net slash unplugged. You want to build your dream server? 01:12:24.004 --> 01:12:28.724 Well, Unraid 7.2 makes it easier than ever. The new 7.2.0 stable is here. 01:12:28.804 --> 01:12:30.364 I've been telling you it's going to be a good one. 01:12:30.684 --> 01:12:35.704 Fully responsive web GUI, and Unraid now works beautifully across all your devices. 01:12:35.964 --> 01:12:38.384 You got your phones, you got your tablets, you got your desktop. 01:12:38.704 --> 01:12:43.664 Picture it. You're sitting there with your tablet on your couch managing your ZFS RAID, right? 01:12:43.824 --> 01:12:48.404 Like, I love that they're working on this stuff. And they didn't ask me to say this. 01:12:49.561 --> 01:12:54.101 So, so thrilled to see them roll out this open API. 01:12:54.381 --> 01:12:57.561 It's officially here. It's open source. It's fully integrated, 01:12:57.961 --> 01:13:02.561 secure, programmable access to your Unraid box. 01:13:02.781 --> 01:13:06.361 People are already using this in the community to build dashboards and automation. 01:13:06.861 --> 01:13:10.441 External apps are going to be able to use this. And there's even going to be 01:13:10.441 --> 01:13:14.421 ways to pipe into external authentication, like OIDC and stuff like that. 01:13:14.661 --> 01:13:17.701 You know, you're O-Dykes. That's not how you say it. Don't say it like that. 01:13:18.281 --> 01:13:23.361 Also, I believe in 7.20, checking my notes here, it looks like ZFS RAID Z expansion 01:13:23.361 --> 01:13:26.201 support, boom, is here. That's great to see. 01:13:26.321 --> 01:13:32.041 You can now grow your ZFS, or some say ZFS, pools without having to start over. 01:13:32.581 --> 01:13:39.021 Unraid 7.2 also introduces support for extended 2, 3, 4, and your NTFS and extended FAT. 01:13:39.341 --> 01:13:42.281 You know, the NTFS thing is nice, right? You got an old disk laying around with 01:13:42.281 --> 01:13:44.041 some family data on it. I do, actually. 01:13:44.941 --> 01:13:49.701 Grandpa's photos. Grandpa's photos are on NTFS. So I'm really happy to see Unraid support that. 01:13:50.201 --> 01:13:53.641 This is what's so nice is they just keep iterating on this. 01:13:53.801 --> 01:13:57.361 They've already had 25,000 downloads of Unraid 7.2. So that's the other thing 01:13:57.361 --> 01:14:01.161 is people are trying this, testing this, building on this. It's a really great community. 01:14:01.401 --> 01:14:05.061 Go unleash your hardware. Use what you've got today. Build your dream system. 01:14:05.421 --> 01:14:08.521 Take advantage of the applications we talk about. Their community store is packed. 01:14:09.181 --> 01:14:16.981 And get a free 30-day trial at unraid.net slash unplugged. It's the OS that grows with your skills. 01:14:17.681 --> 01:14:23.901 Unraid 7.2 with that new API, new responsive web UI. And now we can get Grampus photos. 01:14:24.261 --> 01:14:26.641 Unraid.net slash unplugged. 01:14:31.932 --> 01:14:38.612 Well we have a boost here it is a live boost and it is also a live baller boost, 01:14:42.892 --> 01:14:49.692 now derivation dingus sent in a live boost for 100 000 sats oh. 01:14:49.692 --> 01:14:51.492 Are you serious, 01:14:56.592 --> 01:14:58.092 all right thank. 01:14:58.092 --> 01:15:03.312 You that's great derivation says here i boosted in asking for this episode last 01:15:03.312 --> 01:15:08.052 time but um episode two landed on my anniversary weekend and while i've been 01:15:08.052 --> 01:15:13.692 making big changes to my configs i just ran out of time to send my config in 01:15:13.692 --> 01:15:17.472 this time so i'm listening live and loving it while doing my Sunday chores. 01:15:17.732 --> 01:15:23.292 And please consider this boost a request for Config Convessions episode three. 01:15:24.032 --> 01:15:26.692 Okay. Well, we'll have to get a few plus ones on that because, 01:15:26.752 --> 01:15:29.412 you know, we have to space it out too, but sorry you couldn't make it. 01:15:29.512 --> 01:15:31.512 That's great. Really appreciate the boost. 01:15:31.652 --> 01:15:34.852 But, uh, you know, you get at least a one or two stars for having your, 01:15:34.852 --> 01:15:37.352 your life priorities, uh, properly in order. 01:15:37.732 --> 01:15:40.252 Listen to live and boosting really brought up the average for this episode because 01:15:40.252 --> 01:15:42.892 we were kind of lagging for this episode too. So it made a big difference. 01:15:42.892 --> 01:15:44.152 Yes, happy anniversary. 01:15:44.512 --> 01:15:47.992 I meant being able to resist just messing with their next config and paying 01:15:47.992 --> 01:15:50.872 attention to their spouse and chores. Like, that's pretty impressive. 01:15:51.232 --> 01:15:54.672 Oh, okay. All right. I thought you meant he was listening to us, which is... 01:15:54.672 --> 01:15:55.972 Ah, that too, though. Yeah, you're right. 01:15:55.972 --> 01:16:03.052 That too. Thank you for that baller boost. Nykoff comes in with 22,222 sats. That's a big old McDuck. 01:16:05.272 --> 01:16:10.592 No message, just value, though, which we appreciate. Thank you very much, Nykoff. 01:16:10.592 --> 01:16:15.232 Turd Ferguson comes in with 21,000 sats. 01:16:18.851 --> 01:16:23.431 I have no config to send in. You see, boys, where I'm going, 01:16:23.631 --> 01:16:26.791 you don't need a config file. It's the future! 01:16:28.391 --> 01:16:29.131 Yeah, okay. 01:16:29.491 --> 01:16:31.071 All right, Doc Brown. Okay. 01:16:31.311 --> 01:16:36.231 Is this just, like, so post-vibe that, you know, you don't even really need to keep a static config? 01:16:36.251 --> 01:16:40.031 You just constantly revive on demand for whatever you need at any moment? I don't know. 01:16:40.051 --> 01:16:45.691 Yeah, clearly the future is dynamically vibed configs as the system boots. what can go wrong? 01:16:46.171 --> 01:16:50.831 It's like a SaaS and you pay per minute because you're live streaming your config from a cloud server. 01:16:51.291 --> 01:16:55.431 Well, you need to pre-render, right? And you want to have it globally available. 01:16:55.671 --> 01:16:58.071 That's true. Yeah, you want to fail over it. 01:16:58.471 --> 01:17:00.471 That's probably 90 bucks a month, I would imagine. 01:17:00.811 --> 01:17:08.591 Easy. But you got to pay with some sort of zero trust ERC-20. 01:17:09.131 --> 01:17:14.831 CK roll-up ERC-20 token. That'd be great. Thank you, Turd. appreciate that boost. 01:17:14.831 --> 01:17:22.911 Of course you're gonna like this next booster 4590 sats from BTC is my 401k. 01:17:26.044 --> 01:17:27.344 All right. All right. Okay. 01:17:27.384 --> 01:17:31.444 This one comes from Cast-O-Matic. Elevation boost, boosting from my mountain 01:17:31.444 --> 01:17:34.424 home. The sad amount is my current elevation. 01:17:34.944 --> 01:17:35.384 Wow. 01:17:36.244 --> 01:17:37.004 Love it. 01:17:37.324 --> 01:17:42.424 Also plus one for config confessions. I've yet to truly commit to NixOS, 01:17:42.684 --> 01:17:46.244 and these confessions help set us Nix noobs on the right path. 01:17:46.384 --> 01:17:47.404 I like hearing that. 01:17:47.484 --> 01:17:49.704 Oh, good. There's also some Ansible and geeks in there. 01:17:49.844 --> 01:17:52.844 Yes, because it can also be a little intimidating, I think, right? 01:17:52.844 --> 01:17:56.464 You see these complicated, big, well-set-up configs and be like, 01:17:56.504 --> 01:17:58.384 how am I ever going to get there? But I like that attitude. 01:17:58.524 --> 01:18:02.144 I like the like, oh, look, there's all this stuff I can copy from. 01:18:02.304 --> 01:18:06.744 And you don't have to go from zero to vibed giant config. There's lots of nice 01:18:06.744 --> 01:18:07.844 little middle grounds in the way. 01:18:08.164 --> 01:18:13.744 Also, BTC, I have a question. Your elevation boost there, is that feet or meters or furlongs? 01:18:13.804 --> 01:18:16.184 What do we got here? Four, five, nine, zero. Let us know. 01:18:16.644 --> 01:18:20.604 Yeah. And is it snowing already? I imagine at 4,000, it probably is snowing 01:18:20.604 --> 01:18:25.364 already. Because I've got friends that live at like 7,000 in Arizona, 01:18:25.404 --> 01:18:29.244 and it is already fall-on snowing for them. So I bet you're- 01:18:29.244 --> 01:18:33.324 I like this idea of an elevation boost and seeing how high can we go, right? 01:18:33.864 --> 01:18:37.204 Yeah, but some of them are like mine. Mine's like 180. 01:18:37.764 --> 01:18:40.304 Yeah, us, the C-level folks are not going to do well here. 01:18:41.044 --> 01:18:43.144 Plus or minus the error bar too, right? 01:18:44.384 --> 01:18:48.764 I guess. Oh, yeah, right? Yeah. It's got to get above 2,000 stats to get right 01:18:48.764 --> 01:18:51.164 on the air, I suppose. But thank you for that boost. That's a great idea. 01:18:51.744 --> 01:18:54.744 Sohang's here with 3,333 SATs. 01:18:57.419 --> 01:19:00.959 I bet you that's a reference. Sohang says, I'm kind of getting a bit tired of 01:19:00.959 --> 01:19:04.439 using Nix. The documentation problem doesn't seem to be making any progress. 01:19:04.639 --> 01:19:07.939 And a side effect of the drama has been that a lot of work, both around flakes 01:19:07.939 --> 01:19:09.679 and the general stuff, is stalled. 01:19:09.859 --> 01:19:14.119 I just had a situation come up where I couldn't reason about my config and there's 01:19:14.119 --> 01:19:15.619 no documentation I can look up. 01:19:16.259 --> 01:19:20.419 My three-way brain split of Nix, NixOS, and Nix packages is getting untenable. 01:19:20.539 --> 01:19:23.939 Not to mention the whole deal is a tangle of shell and Perl scripts. 01:19:24.199 --> 01:19:26.039 But alas, what alternatives do I have? 01:19:26.599 --> 01:19:29.239 Geeks is still a bit obscure, and I'm unsure of the reliability there. 01:19:29.779 --> 01:19:35.019 Getting a gosh darn PhD in comp science and Nick documentation is still too much. 01:19:35.599 --> 01:19:39.159 And I just spent a hot minute finding the non-existent boost button on the member 01:19:39.159 --> 01:19:41.059 feed. Yeah, I know. I'm sorry about that. 01:19:42.159 --> 01:19:46.919 It's a problem with private feeds versus public feeds. He says maybe we could vibe code effect. 01:19:49.979 --> 01:19:54.839 The issue is, right, it's like per app, so we have to make some PRs for a bunch of these apps. 01:19:54.839 --> 01:19:59.819 You know i do hear the complaint about the nix documentation a lot. 01:19:59.819 --> 01:20:02.699 I would be curious because you sound like 01:20:02.699 --> 01:20:05.879 you're using nix at a fairly sophisticated level 01:20:05.879 --> 01:20:08.759 and it's true that like there could be 01:20:08.759 --> 01:20:11.959 better docs or more docs but i sort of find like once i 01:20:11.959 --> 01:20:15.599 know a system to like that point i'm sort 01:20:15.599 --> 01:20:18.579 of just kind of in the code anyway so for me 01:20:18.579 --> 01:20:21.379 like the docs problem hasn't been as bad because i just 01:20:21.379 --> 01:20:24.099 assume for anything i'm going to use i'm probably going to go read at 01:20:24.099 --> 01:20:26.819 the module code maybe gets more tangled if 01:20:26.819 --> 01:20:30.399 you're like into like nix packages build time 01:20:30.399 --> 01:20:33.339 helper frameworks for dot net packages or 01:20:33.339 --> 01:20:36.099 something so i'd be curious to know like which particular areas are really 01:20:36.099 --> 01:20:39.499 falling down i do sympathize i've seen a lot of stuff on the nix os subreddit 01:20:39.499 --> 01:20:47.299 like i hate nix os but i hate it less than everything else wow that's rough 01:20:47.299 --> 01:20:50.539 i don't feel that way but like i think i can get the you know there are definitely 01:20:50.539 --> 01:20:54.819 paper cuts frustrations uh but it's also it's hard to quit once you're there. 01:20:54.819 --> 01:20:58.459 That's true that's true okay good luck keep us posted sir. 01:20:59.577 --> 01:21:03.517 Doornail 7887 comes in with a row of ducks. 01:21:05.537 --> 01:21:07.717 Albi Hub deep dive question. 01:21:07.977 --> 01:21:08.697 Oh, here we go. 01:21:08.737 --> 01:21:09.717 And it's a suggestion, actually. 01:21:09.917 --> 01:21:11.437 All right, I'm going to get my notepad out, Wes. 01:21:12.177 --> 01:21:18.377 Albi Hub deep dive suggestion. After setting it up myself, the channels thing 01:21:18.377 --> 01:21:20.457 is really still confusing to me. 01:21:20.737 --> 01:21:27.277 I was surprised to find out I had to type 150k sats just to open a channel to send a small amount. 01:21:27.857 --> 01:21:32.757 Forget the tech barrier to entry, the upfront cost seems like it might be a bigger barrier. 01:21:33.117 --> 01:21:37.237 Any advice to reduce that barrier? Maybe the JB node would be open to supporting 01:21:37.237 --> 01:21:38.677 small channels for newbies? 01:21:39.037 --> 01:21:44.837 So this is, I think, the tricky part of setting up your own node and why services 01:21:44.837 --> 01:21:47.317 like Fountain just do all of this for you, right? 01:21:47.557 --> 01:21:52.997 Is the way Lightning works is it's an open source protocol and it's a peer-to-peer 01:21:52.997 --> 01:21:55.617 system and the peers are these channels between nodes. 01:21:55.617 --> 01:21:58.737 And the reason why the liquidity gets 01:21:58.737 --> 01:22:01.457 locked up the 150k in your case is that way 01:22:01.457 --> 01:22:04.377 it's a guarantee that the amounts can be sent across those channels 01:22:04.377 --> 01:22:09.917 instantly the funds are essentially guaranteed in there so that is tricky and 01:22:09.917 --> 01:22:13.557 i agree with you and so i don't think it's for everybody i think it's for people 01:22:13.557 --> 01:22:17.837 that like to mess with computers and i think it's also for people that might 01:22:17.837 --> 01:22:21.717 use it with multiple applications if your only application is boosting i just 01:22:21.717 --> 01:22:23.497 don't know if it's worth it. 01:22:23.497 --> 01:22:28.837 It's a lot yeah it's a lot to invest both time operations in terms of all the 01:22:28.837 --> 01:22:31.877 software and running it and then yeah as you're finding out and it's very true 01:22:31.877 --> 01:22:35.977 it is like if you especially if you don't already have like a pile of bitcoin 01:22:35.977 --> 01:22:40.877 hanging around you definitely need some capital to fully fund a node's liquidity 01:22:40.877 --> 01:22:42.757 and it's worth calling that out. 01:22:42.757 --> 01:22:47.697 There are ways to buy channel liquidity for pretty cheap like you don't have 01:22:47.697 --> 01:22:49.057 to spend the entire month there are, 01:22:49.826 --> 01:22:55.006 liquidity providers and there's some included in albi that you can commit you 01:22:55.006 --> 01:22:59.126 know 15 dollars and you get 150k channel or something like that so it. 01:22:59.126 --> 01:23:02.606 Is worth noting that a lot of those some of them are single payment some are 01:23:02.606 --> 01:23:04.266 like a monthly payment and then 01:23:04.266 --> 01:23:07.046 if you do a single payment often they'll keep them open but they might. 01:23:07.046 --> 01:23:11.526 Close them if you don't use them so yeah yeah and then about the node our node 01:23:11.526 --> 01:23:16.526 uh that would not be a huge help because our node isn't particularly well established 01:23:16.526 --> 01:23:21.166 or well-connected, you really want to be connected to nodes that have a good network graph. 01:23:21.346 --> 01:23:26.006 And there's like Ambrosia and something, there's sites that help you find that network graph. 01:23:27.426 --> 01:23:32.546 The AlbiHub ecosystem is growing because Albi supports something called Nostra Wallet Connect. 01:23:33.266 --> 01:23:37.106 And it's an unfortunate name because it invokes Nostra, but what it really is 01:23:37.106 --> 01:23:39.386 is a secure way to connect into these things. 01:23:39.486 --> 01:23:42.506 And you're going to find more apps in the next couple of months that you never 01:23:42.506 --> 01:23:46.526 expected are about to announce support for that. and it's going to make Albi even more useful. 01:23:46.726 --> 01:23:49.466 So it could be worth it there. But it's a great question. 01:23:49.726 --> 01:23:53.606 And channels is, I think, one of the things we have to spend some time on for 01:23:53.606 --> 01:23:56.066 sure. Appreciate that boost. 01:23:56.626 --> 01:24:00.326 Well, we have a boost here from Mick ZP for 10,000 sats. 01:24:03.575 --> 01:24:07.815 They say, I couldn't agree more with you on AI and LLMs from last episode. 01:24:07.815 --> 01:24:13.035 I work primarily as a sysadmin at an R1 university, and I'm heavily using Claude 01:24:13.035 --> 01:24:17.135 for projects with software. I'm just not familiar with what researchers want. 01:24:17.375 --> 01:24:22.635 I also have the exact same experience regarding a NIC card that Claude was able to solve. 01:24:22.855 --> 01:24:27.815 The biggest problem in this space is its explosive growth and the fantasy money 01:24:27.815 --> 01:24:29.495 flowing between companies. 01:24:30.075 --> 01:24:35.655 Ah, the circular deals. Yeah. Yeah, I mean, I think it's pretty reasonable to 01:24:35.655 --> 01:24:38.415 expect some of that's going to fade out, maybe a lot of it. 01:24:38.535 --> 01:24:41.635 But things like the functionality you just covered will probably still stand. 01:24:43.015 --> 01:24:46.675 And I don't think we'll have to have big tech frontier models for a lot of that, 01:24:46.775 --> 01:24:47.675 which I'm really excited about. 01:24:47.755 --> 01:24:51.915 Some of the stuff you will, but that particular use case, I don't think so so much. 01:24:52.695 --> 01:24:57.915 Thanks for the field report, Nick Zip. Give us some updates on how it goes. Appreciate that. 01:24:58.835 --> 01:25:02.355 All right. Next boost comes from the Muso with 5,000 SATs. 01:25:04.002 --> 01:25:08.322 I previously had printing problems on Nix as well, and it took me ages to work it out. 01:25:08.422 --> 01:25:11.462 I could find the printer on the network, but the driver just couldn't be determined, 01:25:11.462 --> 01:25:14.642 so I couldn't print, even if I chose the driver in the UI. 01:25:14.822 --> 01:25:22.762 I solved my problem by making sure services.avahi.nsmdns4, as well as Avahi itself, was enabled. 01:25:23.022 --> 01:25:28.242 You may also need nsmdns6 if your printer uses or requires IPv6, 01:25:28.302 --> 01:25:30.082 and your network also has IPv6. 01:25:30.322 --> 01:25:32.482 Ah, yes, the old Avahi. 01:25:33.382 --> 01:25:36.422 Vahi a v a h 01:25:36.422 --> 01:25:43.062 i is what apple used to call bonjour sort of auto dns discovery where things 01:25:43.062 --> 01:25:46.382 find each other and a lot of devices use it now so you should probably have 01:25:46.382 --> 01:25:51.422 that on all your desktops if you're working with things like printers but uh 01:25:51.422 --> 01:25:54.282 thank you muso for letting us know that could be helpful for other people out there. 01:25:54.282 --> 01:25:57.062 Yeah this is one of those the i love it yeah even 01:25:57.062 --> 01:26:00.342 without a linked config you're getting next tips and then this is exactly one 01:26:00.342 --> 01:26:03.642 of those things we're like okay there's probably stuff right maybe other distros 01:26:03.642 --> 01:26:06.842 automatically enable this because they just turn printing on for you no matter 01:26:06.842 --> 01:26:10.682 what next you're gonna have to figure out that you need it but then the plus 01:26:10.682 --> 01:26:14.102 side is once you do it sticks in your config forever so you don't have to re 01:26:14.102 --> 01:26:16.502 figure that out so pros and cons yeah. 01:26:16.502 --> 01:26:20.122 Yeah that's a good one and i guarantee you like ubuntu they're just probably 01:26:20.122 --> 01:26:23.122 installing that they're just installing that just taking care of it. 01:26:23.122 --> 01:26:25.742 Fuzzy misborn comes in with a row of ducks, 01:26:27.822 --> 01:26:32.782 An Ansible repo for config confessions. I should probably go back and do some 01:26:32.782 --> 01:26:35.642 streamlining, but overall, it served me well. 01:26:36.322 --> 01:26:39.982 Ah, we didn't get this in. We did check the boost, but I checked them on Thursday. 01:26:41.262 --> 01:26:46.462 I checked them on Thursday. So, all right, we'll put this in if we do version 3. 01:26:46.762 --> 01:26:49.462 Yeah, stick it on the pile. Thank you, Fuzzy. 01:26:50.002 --> 01:26:52.282 Thank you, Fuzzy. We'll take a look at that after the show. 01:26:52.622 --> 01:26:56.582 Well, WRT54G boosted in a row of ducks. 01:26:57.962 --> 01:27:03.862 I'm sending in some of my very first sats to the show that helped me stay up 01:27:03.862 --> 01:27:08.202 to date and interested in Linux as I started my IT career. So thank you. 01:27:08.782 --> 01:27:09.682 Oh, wow. That's amazing. 01:27:09.922 --> 01:27:11.102 Oh, thank you. 01:27:11.822 --> 01:27:16.742 That's fantastic. Thank you, WRT. And yeah, stick with Fountain. 01:27:16.862 --> 01:27:19.462 You're going to see some impressive stuff coming soon. Appreciate the boost. 01:27:21.422 --> 01:27:26.562 User75 came in with 2,099 sats. Long time listener. 01:27:26.702 --> 01:27:32.282 Love the show. this is my next config oh no uh to be to be uh considered on 01:27:32.282 --> 01:27:35.382 the show also i don't want to give you my real postal code so here's one that's 01:27:35.382 --> 01:27:40.642 nearby uh-oh wes oh postal code hope you got the map hope you got the map westpain 01:27:40.642 --> 01:27:45.702 here it is the postal code nearby four one eight three zero, 01:27:48.872 --> 01:27:53.632 Dash 050 if you need it. That should be pretty easy to find on your map there, 01:27:53.712 --> 01:27:55.632 Westpain. You did bring it, right? 01:27:56.312 --> 01:27:58.692 Oh, good. I thought you didn't have it there for a second. 01:27:58.812 --> 01:28:00.392 Well, of course. I keep it in my back pocket. 01:28:00.672 --> 01:28:01.992 I have a zip code question here. 01:28:03.112 --> 01:28:03.692 Yeah, sure. 01:28:03.712 --> 01:28:07.972 I'm used to those first numbers, but what's with the dash numbers? Dash 050 is... 01:28:07.972 --> 01:28:10.912 Sometimes you need a little more accuracy sometimes. 01:28:11.332 --> 01:28:15.632 What? Was this like some kind of add-on or 2.0 or something? 01:28:16.772 --> 01:28:19.232 You don't have that up in the Canucks? Because you don't have a little extra 01:28:19.232 --> 01:28:20.232 sometimes when you're shipping? 01:28:20.252 --> 01:28:25.432 No, no. We use alphanumeric so you have enough precision. 01:28:27.172 --> 01:28:31.512 Why would you want to go mixing letters and numbers when you could just have nice clean numbers? 01:28:31.512 --> 01:28:34.052 It's actually really annoying to type into fields whenever you need to fill 01:28:34.052 --> 01:28:35.172 in your address, I've got to say. 01:28:35.612 --> 01:28:40.092 I can bang that out on a 10 key in two seconds. Boom, boom, boom, boom. Right? 01:28:40.792 --> 01:28:44.832 Okay, well, I'm going to guess here. And I did have to pull out my unfortunately 01:28:44.832 --> 01:28:53.172 little used uh southern map module okay but i believe this is a brazilian postal 01:28:53.172 --> 01:28:59.532 code uh located in the patuba neighborhood of salvador in the state of bahia eh. 01:28:59.532 --> 01:29:05.652 Really wow that's i hope that's right because that's super neat thank you user 75. 01:29:05.652 --> 01:29:11.732 Where it's currently 81 degrees um with the wind from the east 16 miles per hour. 01:29:11.732 --> 01:29:15.792 Oh man that map of yours A nice little breeze. Yeah. 01:29:15.812 --> 01:29:16.252 That's got features. 01:29:16.252 --> 01:29:20.012 That's a good point. That's really impressive. Very impressive. 01:29:20.312 --> 01:29:22.432 Can we get a little map check for you there, Brent? 01:29:23.720 --> 01:29:31.000 Oh, where am I? Let me just pull out my map here and try to locate myself. 01:29:31.860 --> 01:29:35.360 Can we get, do you hear my map? I don't know if you can hear my map. 01:29:35.500 --> 01:29:37.940 I don't, I don't hear it. You put up. Yeah, there you go. Get it closer to the mic. 01:29:38.020 --> 01:29:39.520 Oh yeah. It might take a little bit. 01:29:39.960 --> 01:29:41.800 Is that like a Mylar map? What is that made out of? 01:29:42.300 --> 01:29:44.020 Yeah. It's like what they make their money out of. 01:29:44.540 --> 01:29:45.160 It's colored. 01:29:46.620 --> 01:29:49.820 Yeah, it is pretty colors. That's for sure. It just doesn't feel real in the hands. 01:29:50.240 --> 01:29:52.300 What? How can you feel that? I'm way over here. 01:30:01.700 --> 01:30:06.340 Okay all right okay okay i don't have an exact postal code but i have a near-ish 01:30:06.340 --> 01:30:11.100 leave postal code for you if that works so are you all right do you have more than just a 10 key. 01:30:12.260 --> 01:30:14.260 Just no just tell us your weather brent for. 01:30:14.260 --> 01:30:16.400 God's sakes oh i thought you wanted, 01:30:19.480 --> 01:30:20.200 So angry. 01:30:20.400 --> 01:30:23.320 All right. GLA comes in with 3,600 sats. 01:30:24.160 --> 01:30:24.900 Wait, it's snowing. 01:30:25.000 --> 01:30:27.480 Hello, everyone. Long time listener here. It's snowing. There you go. 01:30:27.760 --> 01:30:30.360 Love all the JB shows. Although I'm boosting for my Albi Hub. 01:30:30.480 --> 01:30:31.700 I can't wait for that Albi Hub special. 01:30:31.840 --> 01:30:36.120 Cheers from Mexico to my known postal code multiply by 10. Oh, 01:30:36.220 --> 01:30:37.620 my gosh. Another postal code. 01:30:37.680 --> 01:30:41.140 Whoa. I'm going to have to get out the analog mechanical calculator for my men. 01:30:41.480 --> 01:30:47.200 You take the 3,600 and then you multiply it by the 10 and you have well it would 01:30:47.200 --> 01:30:52.400 have been a really great boost but you also have his zip code I don't know if you've got oh okay good, 01:30:58.189 --> 01:31:01.309 There you go. Careful. God, careful, please. 01:31:02.209 --> 01:31:03.349 I know, sharp edges. 01:31:03.589 --> 01:31:07.609 I don't get workers' comp. Could you imagine trying to explain that? 01:31:08.029 --> 01:31:11.429 Yeah. Telling the doctor, how'd you get this injury? Well, you see, 01:31:11.489 --> 01:31:15.869 my buddy Wes was unfolding this map because somebody boosted in their zip code. Yeah, that, yeah. 01:31:16.789 --> 01:31:21.009 Yeah. Okay, I believe I have located, I had to do some scanning. 01:31:21.169 --> 01:31:27.229 I got my paper cut myself here on the, on the stupid meat slicing module. 01:31:27.229 --> 01:31:34.389 But this would be a postal code in Guanajuato where it is in Mexico where it's 01:31:34.389 --> 01:31:38.529 a pleasant 77 degrees with less wind at 11 miles per hour. 01:31:38.889 --> 01:31:39.829 That is great. 01:31:39.829 --> 01:31:42.129 Also from the east though. We're getting a lot of east wind today. 01:31:42.629 --> 01:31:45.049 Thank you. Thank you and it's nice to hear from you out there. 01:31:45.129 --> 01:31:46.969 I love it. We're getting some around the world boosts. 01:31:47.149 --> 01:31:50.429 Thank you for listening. It really makes us feel special. 01:31:51.409 --> 01:31:54.349 Yes and taking the time to get the boost stuff set up. I know it can be a bit 01:31:54.349 --> 01:31:57.589 of a journey and I'd love to see how many of you are taking on the LB Hub Challenge 01:31:57.589 --> 01:31:59.029 because you really get a sense. 01:31:59.309 --> 01:32:01.929 You get a sense of what the challenges are, but then it starts to click too 01:32:01.929 --> 01:32:04.929 the more you use it. And then, of course, thank you everybody who streamed sats 01:32:04.929 --> 01:32:06.989 or boosted under our 2,000 sat cutoff. 01:32:07.489 --> 01:32:11.469 We did have 28 of you stream sats as you listened, and you collectively all 01:32:11.469 --> 01:32:15.389 together stacked 23,876 sats for the show. 01:32:15.569 --> 01:32:18.089 When you combine it with our boosters, and of course we had that baller boost 01:32:18.089 --> 01:32:21.449 that brought up our average, our total stats for this episode, 01:32:21.569 --> 01:32:26.989 episode 640 of your Unplugged program, stacked 203, $1,639. 01:32:28.129 --> 01:32:28.829 Thank you, everybody. 01:32:30.509 --> 01:32:33.889 If you would like to support the show with a boost, Fountain FM makes it easier, 01:32:33.969 --> 01:32:37.889 and it's going to get even easier really soon. Not that I know, but I'm just saying. 01:32:38.469 --> 01:32:42.309 Also, you can set up an Albi Hub, and then there's a whole ecosystem of applications 01:32:42.309 --> 01:32:45.129 you can plug it in and boost the show with open source money. 01:32:58.003 --> 01:33:01.383 A huge thank you to our members, our Jupyter Party, and our core contributors 01:33:01.383 --> 01:33:04.663 who put that support on Autopilot and support us every episode. 01:33:04.803 --> 01:33:07.743 You are our foundation, and we appreciate you. 01:33:08.523 --> 01:33:10.963 Details at linuxunplugged.com slash membership. 01:33:12.143 --> 01:33:17.803 All right, gentlemen, we do have some picks before we go. And one of our first 01:33:17.803 --> 01:33:19.263 picks is from the community. 01:33:20.203 --> 01:33:25.003 Sultros now has Sultros OS and a website. His Immutable Linux is designed for 01:33:25.003 --> 01:33:26.183 gaming and development. 01:33:26.183 --> 01:33:30.123 He's got a couple of release tracks now, an LTS that follows Fedora's stable 01:33:30.123 --> 01:33:33.703 releases, and then an unstable that tracks upcoming features, 01:33:34.103 --> 01:33:37.823 you know, beta, alpha channel stuff, with still some guardrails in place. 01:33:38.543 --> 01:33:44.063 And it has a beautiful website. Now, he's really, I think, really knocked it out of the park. 01:33:45.043 --> 01:33:48.423 And I tried this for a little bit on my Knicks book and loved it. 01:33:48.423 --> 01:33:54.303 He's got a cosmic version, plasma version, Gnome, and a hyper-vibed Hyperland 01:33:54.303 --> 01:33:55.723 version coming very soon. 01:33:56.583 --> 01:34:01.223 As well as a plasma big screen and enlightenment yeah that. 01:34:01.223 --> 01:34:03.483 Is this is becoming a full-time thing it sounds like. 01:34:03.483 --> 01:34:05.983 It is he's also working on the server edition, 01:34:07.216 --> 01:34:10.896 Uh, I mean, wow, really watching them go here. It's really something. 01:34:11.076 --> 01:34:15.456 So check it out at Soltros. That's S-O-L-T-R-O-S dot dev. 01:34:16.416 --> 01:34:19.576 It's pretty neat to see one of our community members working on something like 01:34:19.576 --> 01:34:19.936 that and watching it grow. 01:34:19.936 --> 01:34:21.776 Nice looking website too. This is slick. 01:34:21.936 --> 01:34:22.356 I echo that. 01:34:22.556 --> 01:34:23.156 He's done so good. 01:34:23.276 --> 01:34:23.776 Six out of five. 01:34:23.836 --> 01:34:27.476 I think, I mean, I think this is ahead of Hypervibe now and I don't mean to 01:34:27.476 --> 01:34:30.236 be, you know, I mean, I feel a little personally responsible because I've been 01:34:30.236 --> 01:34:32.496 helping, but Soltros OS for the lead. 01:34:32.996 --> 01:34:36.796 For sure. Definitely. Okay. Now a couple of different picks. 01:34:37.216 --> 01:34:39.716 To help you do the same job, depending on the scale that you need. 01:34:39.896 --> 01:34:42.336 The first one we're going to mention is Parabolic. 01:34:42.636 --> 01:34:46.656 And Parabolic lets you download Vidya and Adya from the web. 01:34:46.936 --> 01:34:51.456 And it's a nice graphical front end to the YouTube DLP client. 01:34:51.696 --> 01:34:56.256 And it gives you some options and features, also helps you support multiple 01:34:56.256 --> 01:35:00.176 downloads at the same time, makes it really easy to pick if you want an MP4 01:35:00.176 --> 01:35:03.436 or a WebM or an Opus or a Flack or whatever it is that they might have. 01:35:03.956 --> 01:35:09.076 And it also will help you grab the metadata and subtitles if you need that for the video as well. 01:35:09.336 --> 01:35:14.156 And it's available as a package, and it's also available on Flathub. It's called Parabolic. 01:35:14.356 --> 01:35:18.216 That's the part that stood out to me, is the sub. Not all of these tools make 01:35:18.216 --> 01:35:20.256 the subs and that kind of stuff super easy. 01:35:20.476 --> 01:35:24.376 So this seemed like, I mean, you don't have to be like me, who constantly runs 01:35:24.376 --> 01:35:28.396 YTDLP from Nix packages on Stable without even caching it locally. 01:35:28.696 --> 01:35:32.876 So if you want an easier time, use Parabolic. Plus, isn't that a cute name? 01:35:32.876 --> 01:35:36.256 I know it's a little silly, but just like a parabolic dish. It's like receiving 01:35:36.256 --> 01:35:38.496 all of your content from the internet. I like it. 01:35:38.516 --> 01:35:44.196 Good icon too. Makes for a good icon. And it's GPL 3. So nice and easy. 01:35:44.336 --> 01:35:47.736 Mostly C++. We don't get too many of those, but there you go. Should be fast. 01:35:48.216 --> 01:35:52.576 Interesting. Now, so that's on the desktop scale. Maybe you're a little more 01:35:52.576 --> 01:35:54.316 industrial scale on your needs here. 01:35:54.396 --> 01:35:58.496 And this is where, and you can tell what they're trying to invoke with this 01:35:58.496 --> 01:36:01.776 name, YouTube R or UTAR comes in. 01:36:01.776 --> 01:36:05.076 It's a self-hosted web app that automates downloading, organizing, 01:36:05.096 --> 01:36:08.036 and scheduling YouTube channel content with support for Plex, 01:36:08.156 --> 01:36:11.556 Cody, Embi, and Jellyfin info. And, um... 01:36:12.517 --> 01:36:15.497 I think what stands out to me is unlike Pinchflat, which I use for a similar 01:36:15.497 --> 01:36:19.497 task, you could have a web UI on your network and you could just grab one-off 01:36:19.497 --> 01:36:21.997 videos or you could do automated stuff. 01:36:22.517 --> 01:36:28.537 And it can do channel archiving. There is also, I think, a really nice option 01:36:28.537 --> 01:36:32.617 here for parents that are trying to curate the YouTube experience for their kids. 01:36:32.977 --> 01:36:37.777 There's some family-friendly curated options in here that I think are a really great option. 01:36:37.937 --> 01:36:40.857 And then you just play the videos back through Jellyfin or Plex. 01:36:41.437 --> 01:36:42.797 And they never go on YouTube. 01:36:43.477 --> 01:36:47.497 And it is designed to download all of the extra info you need so that way you 01:36:47.497 --> 01:36:50.977 have all of the nice-looking display in your media player of choice. 01:36:51.697 --> 01:36:55.277 It's a really, really nice UI, too. I think the UI is top-notch. 01:36:55.857 --> 01:36:58.797 Pinchflat's pretty great, but it does work a little better as sort of infrastructure 01:36:58.797 --> 01:37:01.777 where it's like, well, I know I have these channels that I always want you to 01:37:01.777 --> 01:37:06.357 populate, whereas this does seem a little more friendly for ad hoc stuff that maybe you want to grab. 01:37:06.377 --> 01:37:08.557 A couple of videos you don't want to follow them, you don't need to download 01:37:08.557 --> 01:37:10.877 all the last three weeks, that kind of thing. 01:37:10.877 --> 01:37:13.877 Yeah or maybe like one live stream you know is coming up and you want to grab 01:37:13.877 --> 01:37:22.457 it yeah this is great for that this will do that so it's U-T-A-R-R Y-O-U-T-A-R-R U-T-A-R, 01:37:23.477 --> 01:37:27.177 and did I grab the license for that one I made a note of it's. 01:37:27.177 --> 01:37:28.577 The I-S-C license. 01:37:29.866 --> 01:37:32.126 There you go. I did not make a note of it, but thank you for grabbing that. 01:37:32.786 --> 01:37:35.266 Yeah, it looks like it's a lot of JavaScript and TypeScript, 01:37:36.006 --> 01:37:37.946 and then a little bit of Docker and a little bit of ShellScript. 01:37:38.726 --> 01:37:41.946 Yeah, they do have some Docker Compose example files, so that's probably the 01:37:41.946 --> 01:37:44.146 easiest way to get started if you do want to give it a try. 01:37:45.366 --> 01:37:50.266 Indeed. We'll have links to that in our show notes. Again, linuxunplugged.com slash 640. 01:37:51.066 --> 01:37:53.526 Now, if you made it this far, you might already know, but Wes, 01:37:53.666 --> 01:37:57.226 we have some pro features for people that maybe they're going to revisit an 01:37:57.226 --> 01:37:59.986 episode or maybe there's a topic they want to replay or a topic they want to 01:37:59.986 --> 01:38:02.486 skip, we have it already for them, 01:38:02.746 --> 01:38:07.726 either in the podcasting 1.0 client or even more so in the two clients. Tell them all about it. 01:38:08.266 --> 01:38:15.086 Yeah, that's right. We use the Apple-approved podcasting 2.0 tags in our feed, 01:38:15.086 --> 01:38:18.146 and that means we have both transcripts and chapters. 01:38:18.366 --> 01:38:21.926 So chapters for the high granularity, skip around at the high-level content, 01:38:22.806 --> 01:38:27.226 transcripts for when you want to know exactly what we said and when we said it. 01:38:27.546 --> 01:38:31.866 So the reference Wes is making there is Apple announced they're adopting yet 01:38:31.866 --> 01:38:36.266 another podcasting 2.0 feature, which I think this is like the third one that they've onboarded now. 01:38:36.506 --> 01:38:40.546 And so the chapters and the transcript standards that we have been using now 01:38:40.546 --> 01:38:45.486 for a couple of years are being adopted by one of the largest podcast clients in the world. 01:38:46.126 --> 01:38:49.666 And all of our episodes for the last few years are just going to have all of that information. 01:38:49.926 --> 01:38:54.126 They'll just be turned on for Apple podcast listeners when they get their app updated. 01:38:54.586 --> 01:38:57.226 And there's a bunch of great apps, new podcast apps, if you want to switch to 01:38:57.226 --> 01:39:01.026 a 2.0 app, so that way you can listen to us live and you get all the stuff Wes 01:39:01.026 --> 01:39:03.566 was just talking about and instant updates when we update. 01:39:04.226 --> 01:39:08.046 Expect more from your podcasts, from your podcast apps, and from your podcast 01:39:08.046 --> 01:39:10.906 feeds. We can do better. And we try every week. 01:39:11.046 --> 01:39:14.126 We try. We'd love it if you joined us live next Sunday. We'll do it live. 01:39:14.126 --> 01:39:16.986 It's a Tuesday on a Sunday at 10 a.m. Pacific, 1 p.m. Eastern. 01:39:20.908 --> 01:39:24.808 All right, everything we talked about today, linked at linuxunplugged.com slash 640. 01:39:25.148 --> 01:39:28.108 Mumble Room info is over there. Matrix info membership, contact, 01:39:28.288 --> 01:39:30.708 all of that. Thanks so much for joining us. See you next week.
Previous episode Next episode

Search

Search

Listen on

Apple Podcasts Spotify RSS feed