42： Don't Panic _transcript.txt

[0.00 --> 3.28]  Episode 42, the title can mean only one thing.
[3.58 --> 6.24]  Yes, it is a Hitchhiker's Guide to the Galaxy reference.
[6.64 --> 8.34]  Oh, and I didn't bring my towel.
[8.66 --> 9.62]  Oh, well, don't panic.
[10.04 --> 11.04]  Hello, people.
[11.42 --> 11.90]  Wake up.
[12.10 --> 13.34]  Chris and the Badger.
[13.72 --> 14.20]  Mornings.
[14.20 --> 15.94]  All right, let's go, let's go, let's get up.
[16.06 --> 17.76]  Or whenever you happen to listen to it, I guess.
[18.00 --> 19.56]  On self-hosted.show.
[20.28 --> 21.52]  Oh, we're bringing that back, are we?
[21.62 --> 22.28]  Okay, cool.
[23.48 --> 24.52]  I'm going in with this.
[24.58 --> 25.34]  I love this.
[25.34 --> 25.80]  We are.
[26.00 --> 28.90]  I think you and I would have a great AM morning show.
[28.90 --> 30.70]  We need to lean into that a bit more, yeah.
[30.82 --> 31.16]  We do.
[31.46 --> 37.02]  We'd be doing the traffic on the 15s, and we'd also be taking people's tech questions and
[37.02 --> 42.24]  discussing the news of the day, and we'd have a movie review segment and a TV review segment.
[42.36 --> 49.92]  I know you're going to give us a surprise TV review later in the show.
[50.30 --> 50.54]  Yeah.
[51.22 --> 54.76]  I might have interrupted an interview with an impromptu movie review, yes.
[56.80 --> 58.24]  It just makes me laugh.
[58.24 --> 58.98]  I love it, Alex.
[59.40 --> 61.28]  But, you know, I think we'd have a great morning show.
[61.42 --> 63.36]  And we'd have our friends on, right?
[63.44 --> 67.28]  Like, we'd call Alan on and we'd give him a hard time about FreeBSD.
[67.60 --> 68.38]  That'd be pretty great.
[68.82 --> 69.14]  Yes.
[69.64 --> 71.76]  That would be rather awkward at the moment, wouldn't it?
[72.00 --> 72.34]  Yeah.
[72.52 --> 72.76]  Yeah.
[72.76 --> 75.74]  We'd ask him if he's got WireGuard set up, so that way we could do it.
[76.00 --> 77.50]  We could do it over at WireGuard.
[79.58 --> 82.80]  We should put a link in the show notes so people don't know what we're talking about.
[82.80 --> 83.42]  Oh, yeah.
[83.52 --> 85.12]  Quick too long didn't read.
[85.84 --> 90.52]  WireGuard nearly got merged into the BSD kernel and the code was of questionable quality.
[90.78 --> 96.16]  So if you have any questions about that, there is a link in the show notes to Jim Salter's Ask Technica breakdown of this.
[96.74 --> 100.26]  You will probably come away rather salty with BSD.
[100.58 --> 101.90]  Just full warning.
[101.90 --> 103.92]  So, yeah, enjoy that.
[104.22 --> 107.68]  But in the meantime, I want to say thanks to A Cloud Guru for sponsoring this here episode.
[107.82 --> 111.62]  They are the learning in cloud, Linux, and other modern tech skills.
[111.92 --> 114.12]  Hundreds of courses and thousands of hands-on labs.
[114.22 --> 114.72]  Get certified.
[114.88 --> 115.28]  Get hired.
[115.66 --> 117.96]  Get learning at acloudguru.com.
[118.38 --> 123.78]  But speaking of that post over at Ars Technica, you also had a new post over at Ars Technica.
[124.34 --> 126.38]  And this is a brilliant one.
[126.38 --> 131.54]  How to achieve smart home nirvana or home automation without a subscription.
[131.90 --> 132.70]  Also very clever.
[132.84 --> 135.02]  Were you stuck between two titles, Alex?
[135.22 --> 138.66]  And congratulations also on your first post at Ars Technica.
[139.00 --> 139.36]  Thank you.
[139.42 --> 142.50]  Yes, that was rather a life box ticked last week.
[142.78 --> 144.10]  It was a war of two titles, wasn't it?
[144.40 --> 144.92]  It was.
[145.06 --> 148.88]  Actually, I was working with their editors and they had about six titles to choose from.
[149.00 --> 155.12]  So we ended up picking two halves of two different titles that didn't belong together and then kind of like munging them together.
[155.36 --> 155.76]  Wow.
[155.84 --> 158.56]  Could you imagine having people like help us come up with titles?
[158.56 --> 163.20]  Like you and I like have to like call each other up after the show and be like, oh, what are we going to call this one?
[163.26 --> 163.98]  We completely forget.
[164.06 --> 165.86]  We walk away and don't even title the show.
[166.10 --> 166.48]  We do.
[167.00 --> 167.98]  All the time.
[169.88 --> 176.66]  Hey, so did you see in the news this week that NVIDIA have finally seen Sense and unlocked their GPU drivers for pass-through?
[176.98 --> 178.36]  I did see this in the news.
[178.42 --> 181.40]  I didn't go too far into it because I figured I'd pick your brain.
[181.52 --> 184.66]  This must be a shot in the arm for virtualization.
[184.66 --> 185.86]  I'd say so, yeah.
[186.16 --> 189.32]  To recap, you know, the high level of why this is a big deal.
[190.04 --> 198.70]  NVIDIA previously locked down their consumer graphics cards from being air quotes supported on GPU pass-through.
[198.86 --> 207.92]  So they would show an error code 43, an infamous error code 43 in the Windows device manager rather than loading and just working as normal.
[207.92 --> 217.60]  So what you would have to do is hide the fact that the VM was running as a VM from the VM, which has some minor performance implications, only minor.
[218.16 --> 222.16]  But what this does from NVIDIA is it basically says, yeah, okay, guys, cool.
[222.26 --> 228.94]  Go ahead and take our consumer level graphics cards, pass them through to, you know, guests and do gaming and what have you.
[229.04 --> 230.62]  And, you know, go nuts.
[231.06 --> 233.36]  I don't even know if I have a rig to try this on these days, Alex.
[233.38 --> 234.48]  Have you had a chance to try this?
[234.78 --> 237.10]  I don't actually run pass-through very much these days.
[237.10 --> 245.04]  I ended up basically giving up because, you know, you and I talked about this a long time ago on Linux Unplugged 308.
[245.56 --> 249.34]  And we talked about all the different rigmarole that surrounds PCI pass-through.
[249.44 --> 252.48]  And all of that still applies, even with this NVIDIA news.
[252.68 --> 253.70]  All of that still applies.
[254.64 --> 260.18]  So you're going to need a way of switching your monitor inputs, of switching your keyboard and mouse inputs and all that kind of stuff.
[260.22 --> 264.10]  And I have 144 hertz gaming monitor in front of me here.
[264.10 --> 272.46]  And trying to find a KVM switch that can support that and Thunderbolt from my MacBook Pro, it's just a pain in the bum.
[272.60 --> 276.20]  So I ended up just dual booting these days.
[276.44 --> 278.90]  You know, when I want to do some Windows stuff, I reboot.
[279.30 --> 281.70]  And when I want to do some Linux stuff, I reboot.
[282.08 --> 283.84]  And it's fine.
[283.90 --> 285.06]  It's a bit of a pain, but it's fine.
[285.06 --> 290.62]  Yeah, there is a line where you have to go, how much is it worth virtualizing versus just dual booting?
[290.70 --> 291.74]  I totally get that.
[292.28 --> 294.22]  That's a line I don't really often cross.
[294.40 --> 299.32]  Like, I'm legitimately at a loss of even – I don't know why I'd install Windows right now.
[299.36 --> 301.58]  I don't think I've installed Windows.
[302.00 --> 303.52]  I definitely haven't installed it in 2021.
[304.46 --> 306.24]  And I don't know if I installed it.
[306.86 --> 310.56]  I must have at least installed it once in 2020.
[310.78 --> 311.68]  But maybe that was it.
[312.00 --> 315.38]  I really have over the years just sort of – this is not a brag.
[315.76 --> 321.24]  I just – because I have in other places used Macs for special tools that other people probably would have used a Windows box.
[321.32 --> 322.72]  So it's not like I have some superpower.
[323.32 --> 327.90]  But it's just I have over the times just kind of migrated completely away from Windows.
[327.90 --> 336.06]  Yeah, the only things I really use it for is Fusion 360, so 3D modeling for my printing stuff, which I can also do on the Mac as well.
[336.10 --> 337.66]  So I don't really need Windows there.
[338.20 --> 342.26]  I use it for Blue Iris, as we often talk about, on a separate system.
[342.50 --> 343.28]  I could see that.
[343.50 --> 345.40]  In terms of the desktop, yeah.
[345.50 --> 348.48]  I mean, VS Code takes care of a lot of my coding stuff.
[348.66 --> 352.94]  WSL 2 takes care of a lot of the SSH type stuff.
[353.02 --> 355.40]  And the new Windows terminal is actually quite nice.
[355.40 --> 366.36]  So, I mean, I spend a lot more time in Windows than I think I admit to myself these days, even though it doesn't really feel like Windows anymore because they've basically shoehorned Linux onto the side of it.
[367.66 --> 370.16]  Okay, I feel like there's also an elephant in the room this week.
[370.76 --> 377.70]  You and I have talked about Ubiquity Gear a bit on this show, and they have been in the news in a bad way.
[378.32 --> 382.88]  Some serious security potential leaks, I guess.
[382.88 --> 407.20]  According to someone that Brian Krebs spoke to on his blog, he writes that a cybercriminal gained administrative access to Ubiquity's AWS databases via stolen credentials, perhaps like an employee's LastPass account, it looks like, and then got root admin access, that's what they say, to the AWS accounts, S3 buckets, application logs, secrets for single sign-on cookies, all databases,
[407.20 --> 411.20]  including databases that include user credentials.
[411.20 --> 424.92]  There's even, according to some people who've come forward, supposedly been backdoor software that they found, that Ubiquity IT staff found, that the situation is so serious that certain people have been fired.
[425.06 --> 426.76]  There's a lot going on.
[427.22 --> 431.64]  And I'm wondering how you feel as somebody who's, I think, running a fair amount of their gear.
[431.64 --> 432.74]  I certainly am, yeah.
[432.78 --> 434.80]  I have three access points in this house.
[434.96 --> 441.04]  I have half a dozen that I manage in England for my family across two or three different, you know, houses.
[441.96 --> 451.54]  And, you know, from that perspective, having a centralized controller where all of these devices talk back to that runs on Linode is, for me, very convenient.
[452.30 --> 458.14]  And so far as I understand it anyway, there is no risk to people who self-host the Unify controller.
[458.14 --> 458.82]  Right.
[459.34 --> 465.44]  If, however, you're running one of their cloud keys or a dream machine or something that requires you to authenticate with their cloud,
[466.04 --> 475.26]  you may well want to change some passwords and possibly even consider, you know, not using Ubiquity stuff in that manner anymore.
[475.26 --> 481.72]  Because, you know, the manner of the breach was that an employee's AWS S3 bucket key was compromised.
[481.72 --> 488.32]  So we have to assume that the attackers got access to everything stored.
[488.42 --> 494.60]  Passwords, I mean, they may well be hashed and salted, but we can break passwords with enough compute, you know.
[495.16 --> 498.82]  Application logs, databases, database credentials.
[499.30 --> 504.26]  All of that stuff that's in there, even just IP records, it's all bad.
[504.50 --> 505.60]  It's all really bad, Alex.
[505.60 --> 515.66]  And that's kind of where I was going with this is I quietly for the last couple of years have been progressively more and more disappointed with Ubiquity.
[515.90 --> 523.30]  While my friends, like you and others around me, have seemed pretty solid with them, I have been wondering if things haven't been getting a little sour.
[524.26 --> 526.92]  I don't feel like their latest batch of products have been that solid.
[526.92 --> 532.54]  I have not liked some of their answers around the controller limitations and some of their solutions.
[532.76 --> 535.28]  And it just seemed like a power grab in some circumstances.
[535.66 --> 541.12]  And it seems like this is an indication that not all is well in HQ.
[541.66 --> 543.62]  The QA has for sure been declining.
[543.78 --> 553.50]  You know, there's been several firmware upgrades for the actual APs themselves, as well as the controller software that have nuked people's databases and history and stuff like that.
[553.50 --> 560.24]  I wonder if maybe just some original people left the company a while ago and it's been in decline or if their prioritization has changed.
[560.34 --> 561.38]  But where do you go to?
[561.46 --> 562.54]  Like, what do you change to?
[562.80 --> 565.60]  Well, I actually asked Jim on Twitter what he thought.
[565.74 --> 568.28]  And he's been recommending there's a bunch of TP-Link devices.
[569.12 --> 572.44]  And Tom from Lawrence Systems just got a bunch in to review on YouTube.
[572.66 --> 577.16]  So if you're interested in some Ubiquity alternatives, they are out there.
[577.78 --> 579.98]  But I'll tell you what worries me the most about this breach.
[579.98 --> 586.30]  It's not necessarily that it happened because, unfortunately, these things are going to happen at some point to every company.
[586.84 --> 589.88]  What matters more is how a company responds.
[590.96 --> 594.90]  And Ubiquity tried to basically cover this up.
[595.36 --> 597.28]  They didn't deny, I suppose is more accurate.
[597.46 --> 598.86]  They didn't deny these claims.
[598.86 --> 610.42]  And it took them several days, more than a week, to admit responsibility and basically inform their user base that some of their stuff might be boned.
[610.84 --> 610.94]  Yeah.
[611.10 --> 620.50]  And on top of that, it seems like it's taken some insiders to come out and leak information to well-known people like Krebs to get the complete picture, which is disappointing.
[620.50 --> 622.78]  Yeah, I think you just hit the nail on the head there.
[622.84 --> 623.40]  It's disappointing.
[624.14 --> 632.90]  I mean, Ubiquity made their name through basically making people realize how crappy consumer-grade gear is.
[633.56 --> 640.06]  And, you know, they're providing Cisco-grade ideas and hardware for consumer-grade prices.
[640.06 --> 645.98]  But with these kinds of breaches and behavior as a company, I'm struggling.
[646.22 --> 655.94]  I mean, the access point that I'm looking at behind my monitor here, I first installed into a house that I lived three houses ago, six, seven years ago.
[656.06 --> 657.24]  And it's not Mr. Beat.
[657.32 --> 658.06]  It still works perfectly.
[658.96 --> 661.04]  It's had all the firmware updates and that kind of stuff.
[661.42 --> 668.94]  But there was that one issue with the controller a few months ago where I ended up having to completely rebuild my Unify controller because of poor software QA.
[668.94 --> 671.56]  It's critical infrastructure in my house.
[671.78 --> 672.76]  Okay, it's not a hotel.
[673.04 --> 676.96]  It's not a commercial setting where a lot of people do deploy Unify gear into.
[677.58 --> 680.20]  But if it happens to me, it's going to happen to those people as well.
[680.44 --> 686.34]  And it only takes one or two or three incidents before your brand name is completely trashed.
[686.34 --> 708.34]  And people are already talking about just going back to consumer-grade stuff like mesh networks like Aero and, you know, all these other, you know, not as technically accomplished solutions that have, you know, POE backhaul and stuff like that in favor of something that is possibly even more leaky because it requires more cloud connectivity.
[708.52 --> 708.86]  I don't know.
[708.86 --> 710.48]  But what's the solution?
[711.18 --> 714.52]  I'm probably just going to wait and see how this turns out for the next six months.
[714.80 --> 718.58]  But my next AP will probably not be a Unify one.
[719.00 --> 723.78]  Wouldn't it be something if the community stepped forward and built something that we could flash again?
[724.10 --> 724.64]  Mesh networks?
[725.30 --> 725.82]  Be amazing.
[726.14 --> 726.72]  Oh, it'd be cool.
[726.80 --> 727.22]  I tell you what.
[727.22 --> 739.30]  If somehow we could open these devices up, these Unify devices we already have, and then put like a Tasmota style, completely divorcing ourselves of Unify, of Ubiquity, sorry.
[740.26 --> 741.60]  You know, own the hardware.
[741.74 --> 743.24]  I keep banging on about this, don't I?
[743.30 --> 744.54]  But own the hardware.
[744.72 --> 746.50]  It's not dependent on a cloud service then.
[746.96 --> 748.94]  It does seem like that is exactly what we need.
[748.94 --> 759.58]  It's something we could reflash and load a common OS on that has a common set of standards and interfaces and a web UI, like you used to do with the old Linksys routers.
[759.64 --> 762.52]  You know, those things are still being sold today, those old Linksys routers.
[762.66 --> 763.88]  Open WRT, yeah.
[763.88 --> 770.62]  We just need a newer version of that, something more powerful with different hardware options, essentially like the Ubiquity options.
[770.96 --> 783.06]  Because you're right, you need something for folks that want to run PoE and then, you know, plug an AP at the end of a barn somewhere or at the end of a building somewhere and they can only run one cable.
[783.20 --> 784.76]  Like, you've got to have something for that solution.
[785.10 --> 793.66]  I think your use case, too, where you've got several buildings and you want to manage all of the APs with one interface is also totally legitimate and extremely common.
[793.88 --> 799.74]  It's so useful when my dad rings me up and he's like, oh, my Wi-Fi is not working in the bedroom.
[799.88 --> 804.32]  I can go in and see the AP has dropped from gigabit down to megabit, for example.
[804.52 --> 807.94]  And I'm like, oh, we just need to reboot the AP and we're good to go.
[808.26 --> 811.20]  But there's a way to do that, Alex, you know, and get that central dashboard.
[811.20 --> 816.22]  I know you don't use it much, but something we should talk about at some point on the show, maybe, is Cockpit.
[816.68 --> 823.16]  One of the things I appreciate about Cockpit is they have come up with a way to allow you to manage multiple servers.
[823.16 --> 830.16]  You can go to one UI, though, log into one web server, and you can select all your servers and manage them.
[830.58 --> 832.08]  And it has to be set up in a special way.
[832.16 --> 835.58]  And there's some security precautions you have to take, but it's a very secure setup.
[835.78 --> 837.96]  And so maybe something like that could be done.
[838.76 --> 839.08]  I don't know.
[839.10 --> 840.68]  Maybe somebody out there in the community knows.
[841.14 --> 841.22]  Maybe.
[841.22 --> 841.34]  Maybe.
[841.74 --> 854.64]  So I found out this week that a device I purchased nearly two years ago on some Black Friday sale, you know, I bought it thinking, oh, yeah, this is going to solve all my problems with my fans.
[854.64 --> 867.88]  Because quite often when you buy a server-grade motherboard, the fan control headers are designed for server-grade fans, which spin at crazy high RPMs and draw crazy amounts of current and stuff like that.
[868.48 --> 878.10]  And so when you put a consumer-grade fan on one of these motherboards, it kind of ramps up and then ramps down and ramps up and ramps down because it's not getting enough of a signal to think it's got enough RPMs.
[878.10 --> 880.02]  Anyway, it's this whole thing.
[880.36 --> 883.36]  So I bought this device called the Corsair Commander Pro.
[883.72 --> 892.56]  It plugs into a USB header on the motherboard, controls LED lighting, it controls fans, and has some temperature probes attached to it.
[893.30 --> 895.96]  But the downside was this device was Windows only.
[896.56 --> 903.46]  To my surprise and absolute delight, six months ago, this device has been added to the Linux kernel.
[903.46 --> 911.22]  There's been a driver added to the Linux kernel, so you can now natively control fans via a USB header on Linux.
[911.72 --> 912.88]  I love it when that happens.
[913.64 --> 915.32]  And you're always surprised, like, my little thing?
[915.58 --> 917.18]  The little thing that I care about?
[917.26 --> 917.80]  That's coming?
[918.18 --> 919.30]  That's always the best feeling.
[919.58 --> 921.40]  So I wrote a small blog post about it.
[921.50 --> 926.20]  It doesn't require an awful lot of elbow grease to get set up.
[926.46 --> 930.46]  But you do need to have the 5.9 or later kernel.
[930.46 --> 933.56]  And then you need to make sure you've got LM sensors installed.
[933.76 --> 938.18]  And then there's a couple of other instructions in the blog post about how you configure the PWM profiles.
[938.80 --> 941.74]  And then once you've done that, you just enable the fan control service.
[941.90 --> 946.66]  I mean, I'm using a very tiny, tiny little Arch VM on my ESXi host.
[947.42 --> 951.86]  I think it's using 256 megs of RAM, for example, and 4 gigabytes of disk.
[952.24 --> 955.44]  Perfect use case for Arch because I don't want anything else.
[955.44 --> 956.66]  And I want a modern kernel.
[957.58 --> 959.60]  And that's exactly what Arch gives me there.
[960.46 --> 963.08]  Linode.com slash SSH.
[963.18 --> 966.50]  Go there to get $100.68 credit towards a new account.
[966.70 --> 967.90]  And, of course, you support the show.
[967.98 --> 968.36]  $100!
[969.12 --> 970.04]  And that's a lot.
[970.16 --> 971.70]  You can really try out Linode.
[971.82 --> 974.44]  And you support the self-hosted podcast.
[974.62 --> 976.10]  That's like a win-win for everybody.
[976.60 --> 978.00]  Linode is our cloud server provider.
[978.14 --> 982.42]  When we're building or any kind of testing that we're doing, we do it on Linode.
[982.42 --> 987.04]  And because the price is so great, it makes it possible for a small team to have killer infrastructure.
[987.30 --> 996.62]  That's one of the things that I feel like is our secret sauce here at JB is we can have access to infrastructure that is crazy fast.
[996.70 --> 998.16]  11 data centers around the world.
[998.72 --> 1000.04]  Really fast network connections.
[1000.20 --> 1001.08]  Really fast machines.
[1001.08 --> 1004.94]  Their dedicated CPU rigs have those AMD EPYC CPUs in them.
[1005.52 --> 1010.46]  And they have been independently verified as some of the fastest CPUs in cloud computing.
[1010.80 --> 1017.28]  But one of the things I think that's great about them is when I'm building or testing something, they have a ton of distributions to choose from.
[1017.46 --> 1019.36]  Basically, all the distributions you'd want to deploy.
[1019.48 --> 1022.52]  And even some I'm not sure you'd want to deploy in production.
[1022.80 --> 1023.10]  Arch.
[1023.52 --> 1024.06]  But are there.
[1024.16 --> 1025.86]  And I extremely appreciate that.
[1025.86 --> 1029.12]  But what I really get about Linode is their love for Linux.
[1029.22 --> 1030.66]  That's what got them into this.
[1031.08 --> 1036.26]  That's why they started in 2003 is because they were in love with the technology itself.
[1036.40 --> 1040.32]  They saw where it was going, what virtualization was going to bring to the market.
[1040.50 --> 1043.20]  And so they got in before AWS or anyone else.
[1043.20 --> 1045.18]  They started so long ago.
[1045.46 --> 1048.20]  And yet they don't do like a million things.
[1048.94 --> 1051.92]  They're not like a bookstore and a movie platform.
[1051.92 --> 1057.28]  They really just focus on doing the absolute best cloud computing possible.
[1057.66 --> 1059.60]  And they're independently owned even today.
[1059.76 --> 1062.70]  And they're dedicated to offering the best virtualized cloud computing.
[1062.92 --> 1065.78]  If it runs on Linux, it runs on Linode.
[1066.12 --> 1067.52]  Also, check a link on our show notes.
[1067.62 --> 1069.78]  We'll have a link to their Top Docs talk.
[1070.10 --> 1070.46]  That's right.
[1070.52 --> 1071.48]  Top Docs talk.
[1071.90 --> 1075.48]  And they have one about the benefits of using infrastructure as code.
[1075.80 --> 1077.52]  And, you know, that's something we're big fans of.
[1077.66 --> 1079.08]  So check in the notes for that.
[1079.40 --> 1081.16]  Linode.com slash SSH.
[1081.16 --> 1084.26]  Go there, support the show, get $100 in 60-day credit.
[1084.76 --> 1088.32]  And, of course, check out all the features of Linode.
[1088.72 --> 1090.58]  Linode.com slash SSH.
[1092.16 --> 1098.26]  Well, a few weeks ago, I promised something along the lines of a self-hosted community deep dive.
[1098.68 --> 1103.44]  You know, every so often we're going to have somebody from the self-hosted community come on and chat with us
[1103.44 --> 1112.02]  and sort of talk about the apps they run, why they run them, you know, what they wish that their setup did that it doesn't currently do.
[1112.14 --> 1116.44]  And a lot of, hopefully, discussions about why they made some of the decisions that they made.
[1117.00 --> 1121.22]  Hopefully it'll be an interesting portal into some of our community members for you.
[1121.22 --> 1128.18]  And the first volunteer or the first glutton for punishment is the orange one from our Discord server.
[1128.30 --> 1129.04]  Hey, Jake, how are you doing?
[1129.64 --> 1133.28]  Hi. Yeah, I think I feel like maybe the correct term for this is victim.
[1134.24 --> 1135.14]  Ah, yes, yes.
[1135.18 --> 1137.62]  Yes. But yeah, no, it's great.
[1137.78 --> 1138.50]  It's great to be here.
[1138.66 --> 1139.70]  It's going to be good.
[1139.70 --> 1143.66]  Well, it's been interesting trying to schedule three different people in three different time zones.
[1143.78 --> 1147.60]  So thank you for joining us at, I think, what is 10.30 p.m. UK time?
[1148.24 --> 1149.68]  Yeah, it's 10.30.
[1149.72 --> 1153.72]  I've got to be up in nine hours for another seven and a half hours of work.
[1153.90 --> 1155.06]  That used to be your life, Alex.
[1155.36 --> 1156.72]  Yeah, pre-dad life, huh?
[1156.84 --> 1157.96]  Sleep is a distant memory.
[1159.58 --> 1162.00]  All right, so why don't we dive in with the first question then?
[1162.28 --> 1165.10]  And let's talk a little bit about your hardware setup.
[1165.10 --> 1169.04]  So specifically talking about the stuff you have at home and things like that.
[1169.04 --> 1170.94]  Talk us through some of the stuff you've got there.
[1171.28 --> 1174.16]  Most of my setup is at home.
[1174.28 --> 1176.50]  The sort of self-hosting life is very much.
[1176.58 --> 1179.96]  I run everything on my LAN sort of as normal.
[1181.06 --> 1188.04]  Most of my setup is a single machine because running things over the network is a bit funky.
[1188.80 --> 1193.40]  My main rig is a Ryzen 3000 series.
[1193.90 --> 1196.66]  3700X is the sort of beating heart of it.
[1197.58 --> 1198.68]  Yeah, various other parts.
[1198.68 --> 1202.96]  It runs Proxmox because virtual machines are great.
[1202.96 --> 1204.62]  Do you use VMs for a lot of stuff?
[1204.70 --> 1207.44]  Because I know you're into sort of the one big VM.
[1207.74 --> 1215.64]  We often have this discussion on Discord about the one big VM versus lots of smaller like LXC containers and Docker containers and things like that.
[1215.74 --> 1218.12]  What's your philosophy on that?
[1218.12 --> 1222.14]  If I'm running a hypervisor with VMs, I'd rather not do that.
[1222.14 --> 1233.54]  I'd rather have sort of everything nicely containerized to fully take advantage of VMs in their sort of natural habitat of what they're good for.
[1233.54 --> 1239.56]  So I think my setup is currently six VMs or so spread most of the different uses.
[1239.56 --> 1247.88]  There is still one single LXC container which runs Docker, which has most of my Docker applications in.
[1248.00 --> 1251.94]  There's probably 10 or so containers running under that.
[1251.94 --> 1258.04]  Besides that, I've got a separate one for my monitoring applications.
[1258.22 --> 1259.52]  That would be Prometheus.
[1259.70 --> 1260.94]  Again, your advice.
[1261.84 --> 1262.34]  Grafana.
[1262.76 --> 1268.00]  I've got a separate VM for Home Assistant, which runs Home Assistant OS.
[1268.00 --> 1276.22]  A couple other ones, one which deals with Ingress coming into my house, which is an interesting setup, which I'm sure we'll touch on later.
[1277.40 --> 1280.30]  And yeah, various other little things.
[1280.58 --> 1289.92]  The other place I've diverted away from what you've previously done is I've also moved the storage out of the one big VM.
[1290.08 --> 1292.62]  And so storage is handled directly on the host.
[1292.94 --> 1293.40]  Why is that then?
[1293.40 --> 1300.50]  The main reason for that is I tried running TrueNAS in a VM and it installed great.
[1300.86 --> 1302.28]  I could access all my files.
[1302.44 --> 1307.42]  The issue was that performance was horrible, absolutely horrible.
[1308.50 --> 1310.66]  I just got latency spikes everywhere.
[1310.88 --> 1312.76]  Nextcloud, ground to halt.
[1313.74 --> 1318.18]  SQ Lite over NFS is a really, really bad time.
[1318.24 --> 1319.16]  I don't recommend it to anyone.
[1319.60 --> 1321.08]  So talk us through that a little bit more then.
[1321.08 --> 1323.52]  You know, performance was bad.
[1323.62 --> 1327.58]  Were you passing through a disk controller to that VM or what were you doing?
[1328.12 --> 1338.48]  So from some advice I got from, I'm sorry, I can't remember who it was on the self-hosted Discord, suggested using an LSI HPA.
[1338.48 --> 1344.40]  That HPA I then passed in through regular PCI pass through into TrueNAS.
[1345.18 --> 1359.46]  From there, regular mounted a very small two drive ZFS pool exposed via TrueNAS' built-in NFS sharing, which was super easy to do, which is great.
[1359.46 --> 1363.06]  Mounted that as normal through Etsy FSTab.
[1363.06 --> 1371.64]  And then from there, just pointing my Docker containers at it as if it was a directory in that container thing.
[1371.72 --> 1379.14]  And because it was running entirely over the internal network inside the machine, latency-wise, it was absolutely tiny.
[1379.14 --> 1382.00]  You're talking like fractions of milliseconds.
[1382.48 --> 1385.44]  But for some unknown reason, it didn't like it.
[1385.48 --> 1392.94]  Now, that might be because I went a little bit insane and decided to run TrueNAS scale rather than TrueNAS directly.
[1393.36 --> 1399.58]  So this may be a performance regression with TrueNAS scale because at the time I ran it, it was in alpha.
[1399.58 --> 1402.88]  And we know full well, don't run alpha software.
[1403.28 --> 1405.62]  But I did anyway, just to try it.
[1406.32 --> 1410.22]  Is scale the BSD one and core is the Linux one or is it the other way around?
[1410.30 --> 1410.94]  I can never remember.
[1411.08 --> 1411.58]  Other way around.
[1411.78 --> 1416.36]  So scale is the Linux-y one, which at the time was in alpha.
[1416.72 --> 1417.70]  So I tried it.
[1417.90 --> 1420.40]  It didn't work great.
[1420.90 --> 1426.34]  Yes, I have some thoughts on BSD this week after the whole WireGuard kernel merge thing.
[1426.34 --> 1428.34]  But let's not derail your...
[1428.34 --> 1429.12]  Yeah.
[1429.58 --> 1431.54]  That's not a fun discussion.
[1431.76 --> 1432.38]  It's all embarrassing.
[1432.70 --> 1437.92]  After I tried scale out, it didn't work too well for me.
[1437.98 --> 1447.58]  And I didn't want to try porting over to the actual core version of TrueNAS because keeping going with that process,
[1447.58 --> 1455.96]  it meant I had to deal with issues where that one storage VM, as it were, would have to stay up and alive sort of all the time.
[1455.96 --> 1466.06]  And if I needed to reboot that machine, that VM even, I would have to reboot sort of everything in the entire machine, which felt a bit like a faff.
[1466.06 --> 1471.52]  And eventually I concluded, well, if I want high performance, I want things to be easy.
[1471.52 --> 1482.54]  Then if I move the storage onto the actual host hypervisor under Proxmox, Proxmox has built-in support for ZFS because the OS is on ZFS.
[1482.54 --> 1484.34]  So it just works.
[1484.34 --> 1485.96]  It means latency is nice and low.
[1485.96 --> 1496.88]  And because the majority of my applications live in LXC, there's the nice benefit of rather than using NFS to mount all of my data, I can use bind mounts.
[1497.22 --> 1498.98]  And bind mounts are...
[1498.98 --> 1507.78]  You have no network latency because it's just passing directories into containers in much the same way that you give bind mounts to Docker containers.
[1507.78 --> 1514.04]  There's no extra latency, extra overhead, extra complexity around that.
[1514.24 --> 1515.72]  It just works.
[1516.16 --> 1518.40]  So it sounds like a lot of different application uses.
[1518.40 --> 1523.76]  And it sounds like you have a pretty distinct line between what is a container and what should be a VM.
[1523.76 --> 1529.44]  When I see complexity like this, I start to wonder, like, what's your backup strategy looking like?
[1529.92 --> 1534.64]  My backup strategy at the moment is on that one Docker LXC.
[1534.84 --> 1544.40]  There is a single instance of Duplicati, which backs up because that LXC specifically has access to my entire ZFS pool.
[1545.12 --> 1550.76]  I can just take the entire pool, compress it up with Duplicati and push it up to...
[1550.76 --> 1559.68]  Currently, there's a mixture of Backblaze and S3 for various bits, depending on how much I care about it.
[1560.18 --> 1567.16]  I intend at some point in the maybe not too distant future to switch parts of that out to Restic.
[1567.60 --> 1569.42]  Ah, good man. I was just about to ask you about that.
[1570.40 --> 1572.80]  Duplicati is such a pain in the ass sometimes.
[1572.96 --> 1577.62]  And, you know, it runs fine for weeks and weeks and then you log in and have a look at it.
[1577.62 --> 1583.78]  And in the intervening time, stuff's just broken for seemingly no reason.
[1583.90 --> 1585.18]  And it breaks silently.
[1585.50 --> 1588.68]  I can only configure it through the UI, which you know how much I love that.
[1589.34 --> 1596.54]  So Restic, I think, is something I'm really going to be looking into a lot in the future with Minio, with the S3 backend as well.
[1596.76 --> 1598.78]  So you can use Restic with that.
[1598.96 --> 1601.78]  So you use Backblaze and a little bit of S3.
[1601.88 --> 1603.08]  So is that Amazon S3?
[1603.42 --> 1603.80]  Yeah.
[1603.80 --> 1605.04]  Wow, made of money, boy.
[1606.16 --> 1611.18]  There's like a couple hundred meg in there just because I was testing stuff.
[1611.66 --> 1615.12]  Like this was before when I was only backing up like the tiny bits.
[1615.26 --> 1619.80]  And I concluded, well, if I'm just backing up the tiny bits, I might as well back up everything.
[1620.26 --> 1621.90]  Well, object storage is perfect for that.
[1622.12 --> 1623.28]  Exactly. 100%.
[1623.28 --> 1626.04]  Let me ask you this then, because I'm picturing the audience.
[1626.16 --> 1628.24]  Somebody's out there building their backup strategy right now.
[1628.32 --> 1631.42]  If you were going to start again today, start fresh, how would you build it better?
[1631.52 --> 1632.66]  What would you do differently?
[1632.66 --> 1635.80]  What message would you send to a past version of yourself?
[1636.08 --> 1639.32]  Past version would definitely be install backups sooner.
[1639.88 --> 1646.62]  I'm very glad that I've never had a case where I've had to actually restore from an offsite backup.
[1646.62 --> 1658.74]  I had one case where I had to restore from an offsite backup, which I still think is sort of a bug in Docker, where I was messing around with some weird Docker stuff.
[1659.20 --> 1664.74]  And I went to log into Nextcloud a few hours later and the entire Nextcloud bind mount was empty.
[1665.44 --> 1666.42]  Completely empty.
[1666.52 --> 1668.36]  No app data, no files, no nothing.
[1668.50 --> 1669.32]  Just gone.
[1669.32 --> 1671.72]  I have no idea why it happened.
[1671.94 --> 1677.86]  Fortunately, that morning I had done an onsite backup to a disconnected hard drive.
[1678.20 --> 1686.72]  So a few hours of syncing files back, I lost, as far as I'm aware, no real data because I'd not made any changes.
[1686.84 --> 1688.50]  But that was not fun.
[1688.50 --> 1692.56]  So definitely anyone listening, I think Alan Jude says it best.
[1692.62 --> 1695.38]  If it doesn't exist in three places, it doesn't exist at all.
[1695.76 --> 1697.42]  Oh, you had to go and reference Alan, huh?
[1698.42 --> 1699.18]  Yeah, I kind of did.
[1699.24 --> 1704.04]  But it's also it's such a good point is that now my data exists on my server.
[1704.04 --> 1710.42]  It also exists using ZFS send to a random shuck hard drive sitting on my desk.
[1710.72 --> 1710.98]  Good man.
[1711.14 --> 1715.70]  And then as well, like I say, backup to Backblaze, which has been absolutely great.
[1715.78 --> 1720.98]  I did for a small amount of time decide, hey, what if I roll my own Backblaze?
[1721.84 --> 1722.86]  Would not recommend it.
[1723.08 --> 1731.06]  I had a $10 machine from Kim Sufi, which are a very cheap, dedicated server host out of France.
[1731.06 --> 1735.20]  They're a subsidiary of OVH and we all know how OVH are doing right now.
[1735.44 --> 1737.66]  Yeah, I hear their business is on fire at the minute.
[1737.90 --> 1738.54]  Oh, Alex.
[1738.80 --> 1739.34]  Too soon.
[1739.50 --> 1740.04]  Too soon.
[1740.30 --> 1740.88]  Too soon.
[1741.40 --> 1742.74]  I thought it was funny.
[1742.92 --> 1743.08]  Yeah.
[1743.12 --> 1747.04]  So I tried running that and Minio and it worked fine.
[1747.32 --> 1753.98]  But once I realized that I was backing up a server I owned to a server I owned, it was great.
[1754.28 --> 1757.04]  But it was the Kim Sufi box was a bit finicky.
[1757.04 --> 1758.10]  It was low powered.
[1758.10 --> 1765.02]  Minio, as tiny as it is, it's much more resource heavy than I would expect it to be.
[1765.80 --> 1768.70]  So should we talk a little bit about some of your favorite self-hosted apps?
[1769.00 --> 1769.72]  Top three, maybe?
[1770.22 --> 1777.36]  Oh, so I'd have to say the one I definitely use the most is TTRSS, which is an RSS reader,
[1777.56 --> 1778.90]  my RSS reader of choice.
[1778.90 --> 1783.82]  I do most of my content consumption via RSS.
[1784.16 --> 1790.56]  All of my YouTube consumption is entirely via RSS because YouTube's algorithms and suggestions
[1790.56 --> 1793.60]  and things like that are just, quite frankly, terrible.
[1794.12 --> 1794.56]  That's amazing.
[1794.68 --> 1799.52]  I think more people should do this because I watched a film the other night called The Social
[1799.52 --> 1805.70]  Dilemma, which talks about how insidious those algorithms are in controlling what you see
[1805.70 --> 1809.80]  and what you, eventually what you think and what you believe, you know, the ultimate conclusion.
[1810.44 --> 1815.04]  If anybody's on the fence as to whether, you know, Facebook and Google and Twitter and
[1815.04 --> 1820.38]  what have you are forces for good in the world or not, I recommend watching The Social Dilemma.
[1820.58 --> 1821.44]  It might change your mind.
[1821.86 --> 1822.82]  Anyway, as you were.
[1823.32 --> 1825.14]  That's definitely one for my watch list as well.
[1825.14 --> 1829.08]  Yeah, so TTRSS is definitely way up there.
[1829.32 --> 1830.58]  What clients do you use for that?
[1830.70 --> 1833.72]  I actually just entirely use the web UI mostly.
[1834.10 --> 1834.50]  Cool.
[1834.72 --> 1836.10]  It's easy and it works.
[1836.52 --> 1840.42]  Other than TTRSS, I would have to say NextCloud is currently quite far up there.
[1840.94 --> 1844.38]  That's been a really nice tool for just accessing files.
[1845.00 --> 1848.78]  It's a little bit heavy for my needs, but it is, the plugins are great.
[1848.98 --> 1850.82]  It's fast enough.
[1850.82 --> 1855.20]  And the sync clients, when they work, they work really, really well.
[1855.44 --> 1858.50]  See, everybody always says this, like, oh, the sync's a bit hit and miss.
[1858.54 --> 1861.56]  And I know, Chris, you've had some actual experience with it losing data for you.
[1861.64 --> 1865.74]  But I've used it now for, I guess, three years solid.
[1866.02 --> 1868.80]  And it's just, NextCloud's just been really, really reliable for me.
[1868.80 --> 1871.08]  So I've only had two issues with it.
[1871.16 --> 1875.12]  One is that it doesn't do partial syncs.
[1875.26 --> 1880.90]  So if you modify a small part in a very large file, it will sync the entirety of the large file.
[1881.38 --> 1891.82]  I don't deal with large files, but I suspect if you guys are pushing around very large MP3s or uncompressed media, yeah, then it can be really, really slow.
[1891.94 --> 1897.84]  The other issue I've had, or I did have, which I haven't had in a while, is it would keep forgetting who I am.
[1897.84 --> 1899.26]  Oh, no big deal, right?
[1899.62 --> 1901.84]  I know who I am, but it just forgets.
[1902.56 --> 1908.76]  And it gets very difficult to sync anything if it just forgets who you are.
[1909.10 --> 1910.60]  It just keeps logging me out.
[1910.80 --> 1919.16]  I'd love to see them add LAN sync, too, because that's a fantastic feature when you power up a laptop and it hasn't been on the internet for maybe a week or more.
[1919.50 --> 1926.42]  If you can sync from other nodes on the network directly, it's way faster and it reduces the demand on your internet connection.
[1926.42 --> 1928.40]  I love that feature about Dropbox.
[1928.72 --> 1939.86]  Also, I think Dropbox has some intelligence about the order in which they sync files and what operations sync first versus what operations can be queued, where NextCloud's CSync subsystem doesn't seem to support that.
[1939.86 --> 1947.70]  So we've had situations where the NextCloud server is kind of like processing and syncing down some directory cleanup that we've done.
[1948.52 --> 1952.36]  And maybe it's a significant amount of like just reorganizing or something.
[1952.36 --> 1963.88]  And the client has to process all of those changes and operate all of those file system operations before it will process the sync command to send the new files up to the server.
[1964.30 --> 1968.84]  And so we've literally just had editors on the other side waiting for files.
[1968.84 --> 1971.56]  And so that stunk.
[1971.66 --> 1973.50]  But what we did is we just changed the way we operate.
[1973.62 --> 1977.28]  We don't make those kinds of changes on any kind of show day anymore.
[1977.64 --> 1980.74]  We wait and we make sure we do it like with a couple of day buffer.
[1980.88 --> 1982.48]  And we've adjusted the way we operate.
[1982.70 --> 1983.76]  And we've made it work now.
[1983.82 --> 1986.46]  We've been using it for, I mean, I don't know.
[1986.64 --> 1987.42]  Alex, do you remember?
[1987.62 --> 1990.30]  Since the sprint in 2019, right?
[1990.54 --> 1991.78]  Yeah, since I appeared.
[1992.02 --> 1992.48]  Yeah, roughly.
[1992.84 --> 1993.42]  Yeah, right.
[1993.42 --> 1995.30]  Since we brainstormed and started this show.
[1996.78 --> 1998.54]  So and it's been running.
[1998.82 --> 1999.68]  But yeah, it isn't ideal.
[1999.96 --> 2001.36]  So what's your last pick then?
[2001.70 --> 2011.20]  It's a project I've been involved with a little bit in sort of contributing and writing content for, which is probably also going to be a bit of a sore subject for some people.
[2011.20 --> 2013.16]  It's an application called Plausible.
[2013.92 --> 2018.10]  Plausible is a self-hosted Google Analytics alternative.
[2018.68 --> 2020.24]  It's backed by a company.
[2020.72 --> 2022.18]  There's a hosted offering.
[2022.18 --> 2024.04]  It's really, really nice.
[2024.14 --> 2025.76]  The UI is beautiful.
[2026.48 --> 2028.58]  It's fully GDPR compliant.
[2028.72 --> 2033.22]  So it only tracks the data that it needs to do to do its job.
[2033.28 --> 2036.24]  It doesn't track things around various other places.
[2036.24 --> 2037.74]  It's entirely self-hosted.
[2037.86 --> 2042.22]  So I run my own instance, which tracks my own websites.
[2042.38 --> 2043.94]  It doesn't track anything else.
[2044.58 --> 2051.58]  And what that means is I can see which pages are getting the most traction, which ones aren't, where people are coming from.
[2051.58 --> 2053.30]  And that's about it.
[2053.30 --> 2054.60]  That looks great.
[2054.84 --> 2055.82]  Yeah, really nice.
[2056.20 --> 2057.00]  It's really nice.
[2057.10 --> 2069.28]  I highly recommend it to anyone that's got a website, especially if they're running Google Analytics and want to sort of take back some of their control from Google and various other companies like that.
[2069.28 --> 2070.34]  Uh-oh, ding dong.
[2070.42 --> 2071.00]  You said it.
[2071.54 --> 2072.62]  Take back control.
[2072.86 --> 2074.28]  That's a trigger phrase for me.
[2076.02 --> 2077.16]  Something, something Brexit.
[2077.64 --> 2077.96]  Anyway.
[2077.96 --> 2082.72]  Says the guy who's immigrated to the States to the guy who's still over there.
[2082.88 --> 2083.28]  Incredible.
[2083.96 --> 2084.32]  Uh-oh.
[2084.54 --> 2084.88]  Uh-oh.
[2085.02 --> 2085.42]  Awkward.
[2085.94 --> 2087.90]  One final question for you there, Jake.
[2088.00 --> 2090.22]  And it's the one that everybody's been waiting for.
[2090.58 --> 2092.88]  It's the how many terabytes on your land question.
[2093.26 --> 2093.62]  Oh, yeah.
[2094.18 --> 2097.24]  Oh, so this is going to be an interesting one.
[2097.24 --> 2102.02]  I'm going for the opposite record to what people are probably expecting.
[2102.70 --> 2106.58]  To have from guests on here, I'm going for the lowest result possible.
[2107.08 --> 2110.70]  So my current pool has four terabytes in.
[2110.98 --> 2111.32]  Wow.
[2111.32 --> 2115.44]  I love this idea because why the headache if you don't need it, right?
[2115.92 --> 2118.54]  It's two four terabyte Seagate drives.
[2118.68 --> 2121.46]  They've been working pretty well for my use case.
[2121.56 --> 2124.12]  There's only 200 gig on the pool.
[2124.60 --> 2126.64]  So I've got ample storage space.
[2126.78 --> 2128.84]  I've got ample space to grow.
[2129.66 --> 2131.36]  It's been working absolutely flawlessly.
[2131.56 --> 2137.54]  There is an additional single six terabyte drive, which currently houses all of my media.
[2137.54 --> 2144.66]  I need to get that into a pool of some kind as quick as possible because I can see Alex's face physically pained as I say that.
[2145.10 --> 2146.00]  Perfectmediaserver.com.
[2146.14 --> 2147.32]  Yeah, I know where to go.
[2147.76 --> 2155.86]  It's MergerFS, SnapRaid are two things reasonably high up on my list of things to do when I get a free second.
[2156.42 --> 2160.82]  But yeah, four terabytes is exactly just about enough for my needs.
[2161.02 --> 2164.60]  And I don't really have any intention of growing that anytime soon.
[2164.60 --> 2167.22]  So I'm sticking right here at the bottom of the list so far.
[2167.54 --> 2168.94]  Okay, well, there's no shame in that.
[2169.02 --> 2172.26]  I mean, you could be like the Michael Gambon of terabytes, huh?
[2172.98 --> 2176.88]  That's an old Top Gear reference for some people that don't know what I'm talking about.
[2177.26 --> 2179.28]  So thanks very much for coming on, Jake.
[2179.30 --> 2180.40]  It was really nice to talk to you.
[2180.58 --> 2187.22]  And please let us know from the audience if, number one, you would like to be one of these community spotlights that we're going to do.
[2187.60 --> 2190.18]  What you thought of the segment, let us know as well.
[2190.18 --> 2192.34]  If it's something you'd like to see us do more of, let us know.
[2192.70 --> 2196.06]  If it's something you didn't like, well, maybe keep that opinion to yourself.
[2196.38 --> 2196.48]  Wow.
[2196.48 --> 2199.36]  Is there anywhere else you'd like to send people, Jake?
[2199.46 --> 2202.66]  You know, Twitter or your personal blog that I know you write a lot of?
[2202.92 --> 2206.48]  Yeah, I believe you described me as a, quote, prolific blogger.
[2206.76 --> 2210.20]  And many people who hang out on the Discord know I write quite a lot.
[2210.52 --> 2215.36]  My website is theorangeone.net, which I'm sure will be in the show notes.
[2215.36 --> 2221.54]  My Twitter account as well is at realorangeone, which I suspect as well will be in the show notes.
[2221.54 --> 2222.40]  Well, Jake, thank you.
[2222.40 --> 2226.28]  A quick thank you to CloudGuru for sponsoring this episode.
[2226.50 --> 2230.02]  And I'd like you to know about their PowerShell Core for Linux admins course.
[2230.26 --> 2234.80]  It's an intermediate level course, and it teaches you the concepts of using PowerShell Core with Linux.
[2235.00 --> 2238.10]  This could be game-changing if you're in a multi-platform environment.
[2238.10 --> 2248.26]  And the course includes, of course, administration, installing Docker, working with the SQL server, even managing Azure instances, as well as integrating it all with Visual Studio code.
[2248.58 --> 2251.54]  There's a lot there, so you'll have to click the link in our show notes.
[2251.54 --> 2257.62]  That'll be at selfhosted.show slash 42, and you'll see the PowerShell Core for Linux admins course.
[2257.86 --> 2260.02]  And thanks to a Cloud Guru for sponsoring this episode.
[2261.70 --> 2266.32]  And, of course, a big thanks to our members over at selfhosted.show slash sre.
[2266.58 --> 2269.60]  You can go there to support the show and get a limited ad feed.
[2269.78 --> 2274.02]  We often talk as well in the post-show about some little knickknacks in our lives and things that are going on.
[2274.64 --> 2277.28]  So you get a little bonus show, a little bonus extra content.
[2277.66 --> 2279.46]  Yeah, selfhosted.show slash sre.
[2279.46 --> 2283.38]  And you can also find the contact page at selfhosted.show slash contact.
[2283.62 --> 2285.26]  That's the place to get in touch with us.
[2285.36 --> 2286.44]  I'm on Twitter as well.
[2286.50 --> 2287.12]  You can get me there.
[2287.20 --> 2288.38]  I'm at ChrisLAS.
[2288.92 --> 2290.38]  And I'm there at Ironic Badger.
[2290.54 --> 2292.64]  And don't forget the show at selfhostedshow.
[2293.06 --> 2294.42]  So thanks for listening, everyone.
[2294.58 --> 2296.76]  That was selfhosted.show slash 42.