[0.00 --> 1.34]  I knew what happened, Alex.
[1.42 --> 4.46]  I rolled the Starlink dice and it came up snake eyes.
[4.64 --> 10.92]  I came back to a location after being on the road for about three weeks, set up the Starlink
[10.92 --> 13.08]  and went to update my service address.
[13.44 --> 17.06]  And I got the dreaded no more capacity at your area.
[17.50 --> 19.38]  And this is an area I frequent a lot.
[19.46 --> 20.62]  It's like home-based territory.
[20.62 --> 24.70]  And Starlink says, sorry, no room for you.
[25.12 --> 25.82]  So what happens now?
[25.86 --> 28.18]  Are you out of luck until further notice?
[29.18 --> 30.18]  It's weird.
[30.58 --> 33.78]  I'm only like 15 miles from the other location I was at.
[34.20 --> 38.10]  It's kind of working and not well.
[38.38 --> 42.04]  It's like losing and dropping packets from time to time and connection.
[42.28 --> 45.96]  But when it works, I'm getting like 30 megabits, which is pretty slow for Starlink.
[46.14 --> 51.78]  But I did see some YouTubers reporting that Starlink seems to be testing a roaming mode
[51.78 --> 57.70]  that lets you move around and maybe use it outside your service address.
[57.70 --> 60.72]  So I'm hoping that happens to me soon.
[60.84 --> 64.38]  And I'm just going to keep checking the website every few days.
[65.12 --> 69.34]  There is a website I just found as you were talking here, satellitemap.space.
[69.82 --> 73.44]  And it seems to like divide the entire country up into hexagons.
[73.80 --> 77.82]  And then they've got the actual Starlink satellites flying in real time over the top of it.
[77.82 --> 83.08]  And it looks like the entirety of the Pacific Northwest Redmond's right at the middle of a cell.
[83.76 --> 84.34]  So I don't understand.
[84.62 --> 87.18]  You were on the coast and then you came back to the studio.
[87.28 --> 89.88]  That's not far enough to cross a boundary even.
[90.02 --> 90.52]  What's going on?
[90.84 --> 93.52]  I think it's more nuanced than that website makes it look.
[93.60 --> 95.68]  I think the cells are actually more divided.
[95.84 --> 98.38]  I've seen another website that gives you a different view.
[98.46 --> 99.80]  It's not as fancy as that one.
[100.22 --> 106.50]  It shows hexagons that are basically 20, 30 mile in sizes that overlay over the Google map.
[106.50 --> 111.50]  Either way, I knew I was rolling the dice because you're not supposed to move the Starlink.
[112.08 --> 116.60]  When you're in a service area, they provision for capacity because these require downlink stations too.
[117.16 --> 119.48]  Come on, they know exactly who's going to use this thing.
[119.84 --> 129.28]  People in rural places that have no other option or people that, you know, not connected to the real world like you that lives in the bus.
[129.28 --> 130.92]  Out there in the virtual world.
[131.02 --> 140.40]  When I reviewed Starlink on Linux Unplugged, I didn't really mention the fact that the Ethernet cable doesn't disconnect from the dish.
[140.76 --> 141.98]  It's built in.
[142.52 --> 152.18]  So every single time I tear it down in the snow, in the rain, in the mud, I have to like spool this big cable that I can't detach from the dish.
[152.20 --> 156.74]  And I have to like carry them both around soaking wet and dry them off together and load them up.
[156.82 --> 157.98]  It is the worst.
[157.98 --> 160.72]  At least you got a router with an Ethernet port.
[161.04 --> 162.00]  You can stop complaining.
[162.42 --> 162.66]  That's true.
[162.70 --> 163.36]  They're taking that away.
[163.46 --> 170.78]  But when SpaceX does come out with the Starlink designed for mobile use, which they have patents for, I'm all over it.
[171.00 --> 177.70]  I mean, I was even tempted by the $500 a month Starlink Pro, but I'm glad I didn't pull the trigger on that.
[178.44 --> 179.80]  It would be really SOL.
[180.30 --> 180.96]  Yeah, it's interesting.
[181.10 --> 186.02]  You know, like obviously it has the power to completely change the game, but so does 5G.
[186.02 --> 188.90]  Like you look at what bandwidth that's capable of.
[188.90 --> 196.16]  And, you know, the number of subscribers that a single tower can support on 5G versus LTE, significantly different proposition.
[196.94 --> 199.60]  It's going to be really interesting to see which technology wins out.
[199.72 --> 206.08]  Obviously, you know, in rural America where, you know, it's a pretty different use case to what I'm used to in England, right?
[206.08 --> 209.60]  Where everything's really dense and connected with cables pretty well.
[210.02 --> 214.96]  But like rural America, you're in the middle of the wilderness pretty quickly in America if you're not careful.
[215.28 --> 219.64]  And those places, those are the ones where Starlink will change the game.
[219.72 --> 226.66]  For people like me that work fully remotely, I think, well, I live near Raleigh right now because, you know, I have access to good schools.
[226.84 --> 228.00]  One thing for my daughter.
[228.00 --> 230.72]  But I also have access to a good job market.
[230.90 --> 238.10]  Well, that kind of thing has gone away because I could move anywhere and get a remote job I wanted in my industry.
[238.18 --> 238.68]  I'm very lucky.
[238.98 --> 246.36]  And then you think, well, Internet's another one because you start trying to look at buying 20, 30 acres worth of land in the middle of West Virginia.
[246.84 --> 250.10]  And good luck getting anything above one meg DSL.
[250.10 --> 261.96]  Yeah, I think it's a mix of all of them at once, at least for the nomadic use case, because you can't, I would imagine, ever really use Starlink Mobley because I don't think the way it works.
[262.12 --> 265.76]  I don't think you can be, say, going down the road at 60 miles per hour.
[266.00 --> 268.08]  I've seen Dwayne The Rock Johnson on a sat phone.
[268.42 --> 270.94]  You know, they could do these things in the movies.
[271.26 --> 271.84]  Maybe it could.
[272.02 --> 272.88]  Maybe that'd be awesome.
[272.88 --> 284.96]  But I imagine for quite a while it's going to be a mix of different wireless tech, LTE, 5G, and then you park when you're stationary, you go Starlink.
[285.02 --> 289.28]  Or if you're out like at a piece of property, you know, a farm, it's all kind of hit and miss.
[289.66 --> 296.08]  There's a guy I work with who is working for a government contract, and he lives on a boat off the East Coast.
[296.30 --> 299.78]  And he just sails up and down the East Coast, depending on where the weather's nice all year.
[300.38 --> 301.62]  And he's on a 4G.
[302.00 --> 302.48]  Looks great.
[302.48 --> 307.56]  I had a buddy that did that, but he gave it up, I think, when the boat just started falling apart.
[308.26 --> 309.24]  Well, they do do that.
[309.30 --> 309.90]  They're a boat.
[310.50 --> 312.36]  You know, there are two good days when you own a boat.
[312.42 --> 313.04]  You know that, Chris?
[313.18 --> 315.02]  The day you buy it and the day you sell it.
[315.12 --> 316.20]  And the day you sell it.
[316.26 --> 316.50]  Yep.
[316.88 --> 319.62]  I think that might be true for an RV, too, Alex.
[319.66 --> 328.70]  And I'm looking at what's coming down the road for Home Assistant, which I have deeply integrated into my RV, and I'm not sure what I'm going to do.
[329.38 --> 331.68]  So I had some time away from Lady Joops.
[331.68 --> 335.16]  Not recently, but this was about a month and a half ago.
[335.50 --> 337.42]  Strictly platonic time away, I hope.
[337.42 --> 337.82]  Yeah.
[337.82 --> 345.20]  When our buddy Brent was in town, we were staying at the studio to let Lady Joops defrost from a stay we had in the winter wilderness.
[345.20 --> 351.42]  I spent some time here at the studio, and I just realized how little I've integrated Home Assistant.
[351.84 --> 353.16]  It's just so much the basics.
[353.40 --> 359.18]  It's like motion sensor stuff, a couple of NFC automation tag stuff, and, you know, smart lights.
[359.26 --> 360.68]  It's really fine.
[360.74 --> 361.24]  It's fine.
[361.74 --> 363.04]  I'm not trying to denigrate that setup.
[363.04 --> 370.08]  But compared to what I've done in my primary home in Lady Joops, it's just really night and day.
[370.52 --> 375.54]  And I came to realize just how much we rely on Home Assistant.
[375.86 --> 378.50]  It is an integral part of operating our home now.
[378.50 --> 381.18]  And I don't know how to describe that.
[381.38 --> 385.28]  I describe it as important as some of the machinery in the engine.
[385.46 --> 389.98]  You know, it is an absolute critical part of the operation of the vehicle now.
[390.22 --> 397.74]  So when I see things that are coming down the pipe that are going to break Z-Wave, man, I just don't know what I'm going to do.
[397.74 --> 402.56]  So this is really for any of us out there who are on the OG Z-Wave support.
[402.70 --> 404.50]  Like I'm talking the old Z-Wave stuff.
[404.92 --> 419.98]  It seems going by the beta release notes, then in a couple of releases in the 22.4, so not the next one, but the one after, they are going to deprecate the old Z-Wave support simply because they have to move on in Python versions.
[420.82 --> 423.14]  And no one supports that old Z-Wave stuff.
[423.14 --> 427.46]  And the dev team is recommending instead that you migrate to Z-Wave.js.
[427.74 --> 429.46]  And you know, Alex, we've talked about this.
[429.76 --> 431.98]  I tried it and it went badly.
[432.12 --> 446.94]  It's one of the few times I had to hit the escape hatch and do a full restore from backup and bail out of what I had done because my migration went so poorly that just about everything from automations to timers and buttons all broke.
[447.48 --> 448.22]  Everything broke.
[448.60 --> 449.74]  How many sensors do you have?
[450.10 --> 451.44]  How many devices on that network?
[451.44 --> 453.36]  I think it's somewhere like 100 devices.
[453.76 --> 455.08]  I don't remember how many of them are sensors.
[455.08 --> 459.82]  It's tricky because each sensor actually shows up as an individual device.
[460.34 --> 464.08]  And there are like seven in each one of those little Z-Wave sensors.
[464.42 --> 469.26]  And when you migrate, do you have to repair each device one by one?
[469.48 --> 472.08]  Because I had to do that with my Zigbee thing when I changed my channel.
[472.52 --> 475.08]  I think it's actually stored in my Z-Wave controller.
[475.08 --> 484.42]  However, it seems like the new versions of Z-Wave.js, and I haven't done this for about six months, but it's like a bunch of missing devices show up.
[484.64 --> 485.82]  Like the names don't line up.
[486.12 --> 489.06]  And so I don't know exactly what went wrong when I looked at it.
[489.06 --> 497.20]  But it was, yes, it stored the pairings, but it was almost irrelevant because I'd have to wipe the slate and repair it anyways to fix everything.
[497.90 --> 503.22]  I'm not ready to go there when Matter is probably about a year away.
[503.86 --> 507.20]  And I'm going to then just start replacing all of this with Matter devices.
[507.20 --> 513.62]  And I was really hoping to hold out, just kind of hold out until Matter arrived and then just switch over.
[514.30 --> 517.92]  And it seems like I'm not going to get that opportunity because they want to move on.
[518.02 --> 520.06]  They got to get a newer version of Python in their stack.
[521.08 --> 527.06]  I'm playing devil's advocate a little bit here, but how do you propose that Home Assistant solve this problem?
[527.24 --> 529.08]  I mean, time moves on.
[529.20 --> 533.58]  Python 2 has been on the ropes for a long time now.
[533.64 --> 535.46]  I mean, it's not like this is a new problem.
[535.76 --> 536.98]  What's the alternative though?
[536.98 --> 538.52]  I'm not really sure there is one.
[538.86 --> 547.14]  Looking at it objectively, I think to myself, isn't there some way they could supply this as a container so it is unaffected by the base system?
[547.46 --> 549.48]  But these integrations are just that.
[549.54 --> 550.18]  They are integrated.
[550.62 --> 553.00]  They don't run as separately isolated containers.
[553.00 --> 556.28]  But it's a shame because right now I really wish they could.
[557.02 --> 558.34]  This is really going to screw me.
[558.44 --> 560.20]  And there is people already online, of course.
[560.26 --> 564.64]  And, of course, the Internet doesn't recommend you do what the developers suggest you do.
[564.64 --> 572.44]  The Internet wants everyone to go install Z-Wave.js to MQTT and go set up an MQTT broker and go learn all of that.
[573.54 --> 578.18]  Which perhaps is a great idea, but it's like not what the developers are recommending.
[578.18 --> 585.14]  And when something like a breaking change like this comes along and the community needs to know what to do, having all this mixed messaging just makes things worse.
[585.28 --> 586.90]  So that stuff drives me crazy.
[587.26 --> 590.14]  And what you start seeing people say they're going to do is just not upgrade.
[590.14 --> 597.58]  They're basically going to upgrade to 22.3 and then they're going to hold until something else comes along.
[597.68 --> 600.98]  Which, you know, it sucks because that's probably what I'm going to have to do.
[601.48 --> 607.08]  I'm grateful that I have a separate Home Assistant instance here in the studio that I'll be able to keep up to date so I can follow along on development.
[607.26 --> 615.00]  But in my RV where I consider it mission critical, I and I think a lot of people are just going to stop upgrading now.
[615.00 --> 616.76]  Yeah, I think a lot of people get burnt out.
[616.84 --> 623.66]  There was a thread on Reddit, I think it was about a week ago, complaining about the state of the Home Assistant documentation.
[624.36 --> 628.76]  The complaint itself is neither here nor there for purposes of this discussion.
[629.44 --> 641.04]  What I wanted to talk about was the general consensus in the comments of that thread that Home Assistant, despite its best efforts, for now at least, is geekware.
[641.04 --> 652.04]  You know, my dad's a smart guy, but I can't imagine giving him a vanilla Raspberry Pi with nothing except Home Assistant even flashed onto it and say, here, go automate your house.
[652.56 --> 655.08]  I can't imagine that going very well.
[655.08 --> 660.62]  And I look at things like the HomeKit integration that Apple are doing.
[660.84 --> 662.48]  I look at the Alexa stuff.
[662.72 --> 664.28]  I look at the Google Home app.
[664.94 --> 666.12]  That's what you need to do.
[666.20 --> 671.88]  That's the level of integration that you need to get to in order to make it more approachable and more accessible for people.
[672.74 --> 681.36]  Home Assistant's biggest strength is how modular it is and how customizable it is and how geeky it is.
[681.36 --> 690.52]  That's the thing I love about it the most is the fact that if I want to go and tweak a specific knob three degrees to the left, I can go and do that one specific change.
[691.40 --> 694.10]  Probably similar to the reasons why I like Linux as well, you know?
[694.44 --> 695.64]  Yeah, I do know what you mean.
[695.92 --> 703.36]  And, you know, we're trying to compare, I think, Apple's, you know, kind of, you will like this approach that they do on macOS to Linux.
[703.36 --> 719.44]  You know, I'm comparing Alexa to Home Assistant here and I don't know, like, I just think about where does the Home Assistant project go to address complaints like yours, like the ones in this Reddit thread, and complaints of my own as well.
[719.44 --> 724.68]  Where, you know, I get fatigue, and I get fatigue maintaining my own Home Assistant instance.
[725.24 --> 728.90]  Stuff just breaks for no apparent reason.
[729.18 --> 733.72]  And, you know, I stay on top of updates, and I do try and figure stuff out.
[733.96 --> 737.26]  And, I don't know, like, it's just difficult.
[737.80 --> 744.24]  I don't know that Home Assistant is quite grasping the problem that faces them quite yet.
[744.30 --> 746.70]  They're solving the technical problems really, really well.
[746.70 --> 760.32]  But, I do think, on the whole, there's still a lot of work to be done on the kind of people side of the problem that they're solving, like the education, the documentation, making things more bite-sized and more accessible to folks.
[761.02 --> 769.86]  I feel like there is a period of time where it's reasonable for Home Assistant to introduce breaking changes, to get things built right for the long term.
[770.36 --> 773.76]  And, when a project's new, you decide to do a few things, and you've got to make a few changes.
[773.76 --> 779.02]  I think, to their credit, it's not like Z-Wave.js came out yesterday, right?
[779.66 --> 781.52]  And, part of the reason is because I saw where this was going.
[781.60 --> 783.30]  There was multiple options, and I just wanted to hold off.
[783.42 --> 790.86]  But, anybody who's adopted Home Assistant in the last year just started off with Z-Wave.js, right?
[790.92 --> 792.32]  They don't have to deal with this.
[792.32 --> 805.74]  And, so, I think something we have to keep in mind is, even though you and I have been using it for a few years, I think the vast, vast, vast majority of users that Home Assistant will ever have are still yet to come, right?
[805.76 --> 807.62]  They start arriving when there's hardware devices.
[808.20 --> 813.10]  So, we're still the early adopters that are actually helping kind of bang out some of the rough edges on this thing.
[813.10 --> 820.46]  And, so, we are more likely to get exposed to those issues that cause fatigue that both you and I are feeling right now.
[821.06 --> 831.72]  But, what gives me hope is, if you zoom out a couple of years and look at the Home Assistant project's trends, the break-in changes are slowing down.
[832.10 --> 833.84]  I think you'd agree there's less.
[834.02 --> 834.98]  There absolutely are, yeah.
[834.98 --> 841.60]  Also, they're making things more and more automatic as time goes on.
[841.80 --> 855.38]  Like, when you throw Home Assistant on a network for the first time, you know, just like say you're a new user and you take a look at it, it'll often suggest four or five or six integrations automatically just by noticing what's on your network.
[855.50 --> 857.94]  They've gotten really good at like saying, hey, you got an Apple TV.
[858.08 --> 859.12]  Hey, you got an HP printer.
[859.26 --> 861.34]  You know, like, would you like to set that up?
[861.34 --> 872.50]  But the fundamental appeal that Home Assistant has that will always be a unique value proposition for at least these open source type systems is it's multi-vendor.
[872.94 --> 881.34]  It works with all the different third-party products and cloud devices that you got on a whim and two-you things that somebody bought you for Christmas.
[881.58 --> 883.20]  And it works with all of it, right?
[883.46 --> 885.60]  Whereas Apple stuff, it only works with the HomeKit stuff.
[885.60 --> 891.46]  The Echo stuff only works with the devices that, you know, work with the Echo and same with the Googs and all of that.
[891.62 --> 893.10]  It's different in that way.
[893.18 --> 896.10]  It's finally a way to just bring it all home, bring it all on the land.
[896.20 --> 903.28]  And once that starts connecting with people and there's a piece of hardware and some of these transitional things are worked out, I think it's going to be fine.
[903.36 --> 909.46]  But the reality is when you're living in the now and this stuff's still getting hashed out, it kind of sucks.
[909.74 --> 913.96]  And I'm not a big fan of doing the I'm not updating thing.
[913.96 --> 916.40]  That's sort of my last worst case scenario.
[916.74 --> 919.10]  I'm much more of a keep my systems up to date.
[919.16 --> 924.02]  Like if I'm going to run a box, when I decide to deploy something, I'm committing to keep it maintained.
[924.26 --> 925.96]  I don't just deploy something and not maintain it.
[926.02 --> 927.26]  So that bothers me a lot.
[927.86 --> 935.18]  Additionally, this is why I'm really glad I'm not running their OS because I will keep the Ubuntu base up to date, right?
[935.22 --> 941.84]  Where I don't know if that's safe when I'm running their OS, if I kept the OS upgrading all the time, but didn't upgrade Home Assistant Core.
[941.84 --> 943.50]  I don't know if something breaks.
[944.00 --> 944.36]  Possibly.
[944.58 --> 950.26]  I could see that being an issue, especially if it's like a year before any matter devices ship or maybe even longer.
[951.26 --> 957.30]  But because I've installed it myself on an Ubuntu system, I know I can keep that 2004 system up to date.
[957.66 --> 959.10]  So at least that'll be secure.
[959.74 --> 962.30]  Can you believe I got an opportunity to work the OS rant in there?
[962.42 --> 963.20]  It's been a few episodes.
[963.72 --> 966.62]  And I was almost worried that you weren't going to come up for air then.
[966.66 --> 969.00]  And then I realized you were going on an OS rant somehow.
[969.00 --> 970.14]  You managed to work that angle.
[970.48 --> 970.96]  Good job.
[971.70 --> 972.44]  It's been a while.
[974.66 --> 976.86]  Linode.com slash SSH.
[976.96 --> 980.62]  Go there to get $100 in 60-day credit on a new account.
[980.82 --> 982.12]  And you go there to support the show.
[982.30 --> 982.96]  Yeah, I mean, $100.
[983.34 --> 985.74]  You can really go kick the tires at Linode.
[985.84 --> 986.76]  It's the Geeks Cloud.
[987.30 --> 994.06]  They're not going to try to lock you into some crazy, esoteric, hyperscaler, proprietary platform where your skill set only applies to that.
[994.06 --> 997.10]  Oh, I don't like that business model at all.
[997.46 --> 998.20]  No, that's not Linode.
[998.28 --> 999.92]  They got 11 data centers worldwide.
[1000.34 --> 1004.46]  They've been working at this for 19 years to create a great experience to run applications on the cloud.
[1004.70 --> 1006.40]  You can build it from the ground up yourself.
[1006.74 --> 1008.24]  I mean, really, all the way down to the image.
[1008.64 --> 1013.94]  Or you can pick one of their ready-to-go application stacks and get it deployed in just one or two clicks.
[1014.12 --> 1016.36]  And the performance is great.
[1017.14 --> 1023.78]  Anything that faces the JB audience that we've built in the last, I don't know, two and a half years, we've built it on Linode.
[1023.78 --> 1030.16]  And I would imagine now, as being a part of Akamai, they're going to get access to Akamai's CDN.
[1030.58 --> 1035.38]  I was quite surprised when I heard the news, but I contacted a couple of our friends that we know that work there at Linode.
[1035.94 --> 1037.32]  And they seem pretty excited.
[1037.52 --> 1043.82]  In fact, they're working on a new secret product, a new Linode product offering that'll be coming out soon.
[1043.88 --> 1044.96]  That's still all in the works.
[1045.52 --> 1051.92]  And you know another thing that's really cool is the day that announcement dropped, we actually have Linode employees on the self-hosted Discord.
[1051.92 --> 1056.80]  And they were there answering our audience's questions about what does this mean for the future of the company.
[1057.28 --> 1059.84]  And I think a lot of fears were kind of put to rest that day.
[1060.20 --> 1062.54]  Yeah, they really have been part of the community for a while.
[1062.78 --> 1068.18]  I met them the same time I met you at Texas Linux Fest, you know, years ago now.
[1068.26 --> 1069.24]  It feels like 100 years ago.
[1069.74 --> 1073.76]  That was when I really realized they're actually in it because they wanted to be.
[1073.76 --> 1077.58]  Like they were passionate about being at Texas Linux Fest and made a good impression on me.
[1078.18 --> 1082.60]  So if you're ready to go spin something up, you want to go experiment or do a little R&D, go try it out on Linode.
[1083.04 --> 1085.58]  Go to linode.com slash SSH.
[1087.62 --> 1092.38]  So in the news this week, TrueNAS Scale is finally at release.
[1092.86 --> 1094.22]  Can you believe it, Alex?
[1094.68 --> 1096.66]  This was like announced in the summer of 2020.
[1096.66 --> 1102.98]  It has been a very methodical development process to get us here.
[1103.08 --> 1107.16]  And the big news with Scale is it's based on Debian 11, not FreeBSD.
[1108.08 --> 1108.44]  Right, yeah.
[1108.52 --> 1115.00]  I mean, back in the old days, TrueNAS is the product formerly known as FreeNAS, of course.
[1115.30 --> 1117.60]  In fact, there is still a variant based on FreeBSD.
[1118.34 --> 1119.54]  That's TrueNAS Core.
[1119.54 --> 1122.96]  This one, TrueNAS Scale, is based on Linux.
[1123.20 --> 1129.40]  And obviously this is made possible by some of the amazing work that's been done by the ZFS on Linux project.
[1129.92 --> 1133.02]  This TrueNAS product is still ZFS first.
[1133.32 --> 1138.02]  It's still the primary storage file system that they recommend and kind of push in the OS.
[1138.26 --> 1143.74]  And everything else around that is kind of orthogonal to that original premise of ZFS first.
[1144.18 --> 1146.62]  Yeah, ZFS with Gluster.
[1146.62 --> 1157.38]  They kind of position TrueNAS Scale as a product that works great if you want to scale out your storage across multiple systems.
[1158.04 --> 1162.90]  And they use Helm on the back end to manage all of this with like a Kubernetes system.
[1163.12 --> 1168.72]  So you could see how like when you scale that out, that back end management system scales with it.
[1168.80 --> 1175.20]  When you're deploying, say, like a Docker container on TrueNAS Scale, it's actually being orchestrated with Helm on the back end.
[1175.20 --> 1176.80]  I think that's fascinating.
[1177.00 --> 1179.32]  It must have been a ton of work to get all that working right too.
[1179.76 --> 1183.94]  They really are pitching this as a ZFS plus Gluster.
[1184.30 --> 1185.78]  And I'm curious what you think of that.
[1186.16 --> 1186.58]  Well, it's interesting.
[1186.68 --> 1190.00]  I mean, I've done a lot of work with Gluster through my OpenShift stuff at work.
[1190.00 --> 1207.86]  And all I can tell you is that with version 3 of OpenShift, we used to ship Gluster to customers, to end customers using a tool called Heceti to do a lot of the automated volume management of persistent volume claims and stuff like that on top of the underlying Gluster storage.
[1207.86 --> 1217.38]  All I'll say about it is we don't ship Gluster with version 4 of OpenShift because it wasn't very reliable.
[1218.04 --> 1218.18]  Gotcha.
[1218.56 --> 1220.52]  Based on customer feedback, you might say.
[1220.92 --> 1221.34]  Yeah.
[1221.50 --> 1229.38]  I mean, you've got to say like you look at the scale that Red Hat operates at and, you know, we battle test our stuff in development.
[1229.38 --> 1244.22]  But the real test is when you put it into production on customer sites and the reality, at least, for some of the incredible scale at which the OpenShift clusters that I work on operate at is it just wasn't up to the job.
[1244.88 --> 1248.24]  Now, for smaller deployments, sure, it's okay.
[1248.36 --> 1249.18]  I think it'll be fine.
[1249.22 --> 1251.10]  It'll get the job done for a handful of servers.
[1251.10 --> 1259.48]  I mean, the thing with Kubernetes in particular is it can spin up hundreds of pods within a space of a minute or two.
[1260.06 --> 1270.18]  And sometimes each of those pods is making a request to the API underneath to request certain things and just things, they're not really designed to handle that kind of scale.
[1270.66 --> 1275.26]  But I don't necessarily think that TrueNAS is kind of going after that particular market.
[1275.26 --> 1287.28]  I mean, we look at the marketing materials and you could be forgiven for being given a bingo card and sort of crossing things off, looking at the things they've got, you know, Docker, KVM, Kubernetes, scaling, all this kind of stuff.
[1287.38 --> 1290.22]  And I just, I look at it and wonder who it's for.
[1290.54 --> 1294.30]  It's a serious storage appliance product.
[1295.02 --> 1305.14]  But if I'm looking for a serious storage appliance product, wouldn't I go to NetApp or Dell EMC or insert other major storage vendor here?
[1305.26 --> 1308.96]  I don't know what niche is TrueNAS aimed at.
[1309.02 --> 1312.10]  Is it home users like FreeNAS started out being?
[1312.24 --> 1314.12]  Is it small, medium businesses?
[1314.86 --> 1315.62]  I'm genuinely curious.
[1315.62 --> 1321.98]  If you use TrueNAS as part of your daily workflow and you're not just a home user, let me know.
[1323.12 --> 1324.76]  Selfhosted.show slash contact.
[1325.36 --> 1333.50]  I think this is targeted at like your Linus Media Group sized companies that have a lot of storage needs.
[1333.50 --> 1338.28]  And they also want to do KVM virtualization with GPU pass-through and that kind of stuff.
[1338.52 --> 1339.16]  Or JB.
[1339.68 --> 1342.62]  You know, we have three physical x86 servers now.
[1342.98 --> 1348.98]  And you could see using this to turn all three systems into one large storage system.
[1349.20 --> 1352.48]  And take advantage of running applications across them.
[1353.14 --> 1354.90]  And VMs.
[1354.94 --> 1356.82]  I mean, I'm almost talking myself into it.
[1356.84 --> 1358.98]  Just actually, you know, saying it right now.
[1358.98 --> 1362.78]  The reality is, I think, small to medium business.
[1363.32 --> 1368.16]  I think people who were maybe buying a high-end QNAP or Synology or...
[1368.16 --> 1371.68]  What is that NAS software that Linus Media Group uses?
[1372.02 --> 1372.34]  Unraid.
[1372.68 --> 1372.90]  Unraid.
[1372.96 --> 1373.84]  We've talked about Unraid on the show.
[1374.00 --> 1377.64]  Like, they may be going after a little bit of Unraid's market as well here, I think.
[1377.92 --> 1380.22]  Yeah, Unraid was where I cut my teeth in Linux, darling.
[1380.58 --> 1380.78]  You know?
[1380.98 --> 1381.72]  Yes, I remember.
[1382.26 --> 1387.82]  In fact, I think we both, you know, we both are actually kind of fond of Unraid, even though neither one of us have used it in quite a while.
[1388.00 --> 1390.30]  But it definitely serves a market niche.
[1390.62 --> 1395.36]  And FreeNAS scale feels like it's going after that market.
[1395.56 --> 1399.10]  But they also say, we also have a way to go even bigger.
[1399.36 --> 1404.60]  And, you know, so maybe if your storage needs ever start really getting big, we've got other solutions here for you as well.
[1404.84 --> 1406.90]  It's an interesting pitch, for sure.
[1406.98 --> 1409.68]  And I'll be curious to see how it plays out over the next few years.
[1409.68 --> 1416.76]  Now, I thought I'd spin it up in the name of science slash content and see how it performs.
[1417.08 --> 1422.00]  So I built a new backup server in January, which somehow I haven't talked about on the show yet.
[1422.32 --> 1423.28]  Oh, criminal.
[1423.44 --> 1424.40]  I've kind of been meaning to.
[1424.50 --> 1426.98]  Anyway, I'll go into more detail in a future episode.
[1427.12 --> 1435.42]  But the quick pitch is it's a local box on my LAN that just duplicates the ZFS array from my basement to my attic.
[1435.42 --> 1442.28]  Right. So it's opposite ends of the house. If a pipe bursts or something happens at one end of the house, it's OK at the other.
[1442.36 --> 1446.52]  Obviously, I've got offsite backups in England for the rest of my backup methodology.
[1446.80 --> 1454.00]  But this is to save me having to mail a hard drive from England instead of uploading eight, nine, ten terabytes, whatever it is.
[1454.32 --> 1456.52]  Yeah. Pipe bursts. You don't really want to have to go through all that.
[1456.58 --> 1457.62]  And if you got the hardware, why not?
[1457.62 --> 1464.28]  Exactly. So what I thought I'd do for the purposes of this segment was install TrueNow Scale on that backup box.
[1464.48 --> 1470.06]  So I fired it up yesterday evening, installed the ISO, pretty painless.
[1470.16 --> 1473.12]  I did it through the IPMI interface of the ASRock board I'm using.
[1473.86 --> 1476.84]  Install was six minutes, something like that.
[1476.96 --> 1479.50]  Really fast, painless, ZFS en route.
[1480.36 --> 1482.88]  Great. Done. Booted. Got an IP address straight away.
[1483.02 --> 1485.20]  Everything was detected. All my drives could be seen.
[1485.20 --> 1491.10]  And first thing the operating system tells me when it boots is update available.
[1491.72 --> 1494.56]  I'm like, it was released yesterday.
[1495.04 --> 1496.68]  I just downloaded the ISO.
[1497.16 --> 1499.56]  And we're not talking small updates.
[1499.72 --> 1502.48]  We're talking, you know, the ISO is two gig or something.
[1502.72 --> 1505.48]  We're talking another 1.3 gigs worth of updates.
[1505.48 --> 1509.62]  And I'm like, couldn't you have just rolled that into the ISO that you released yesterday?
[1510.26 --> 1511.10]  That's the whole thing.
[1511.94 --> 1513.30]  Yeah. Yeah.
[1513.30 --> 1515.90]  Maybe they froze the image a little bit ago or something.
[1516.30 --> 1518.90]  Maybe. Right. I was like, fine. Screw it. Doesn't matter.
[1519.28 --> 1520.68]  I'll do the update. Press the button.
[1521.56 --> 1525.22]  Then I'm presented with an error message that says, cannot downgrade.
[1525.74 --> 1534.28]  Release 22.02.0 cannot be downgraded to release 22.0.release.
[1534.28 --> 1539.76]  And I think, man, if this is a sign of things to come, they just haven't checked the string,
[1539.84 --> 1544.52]  you know, logic that's doing the passing of the logic about which updates the newer one there.
[1544.58 --> 1549.70]  I'm thinking, okay, that's a fairly basic mistake to make, but sure.
[1549.80 --> 1550.56]  Fine. We're human.
[1550.70 --> 1551.72]  Okay, cool. No problem.
[1552.26 --> 1554.24]  I go to the storage tab next.
[1554.24 --> 1559.54]  And I think, right, I need some storage before I can actually even test out any of the features.
[1559.68 --> 1570.08]  I need a ZFS pool in which to put my KVM virtual machines and my containers that I can now run on top of TrueNAS Scale because it's a proper operating system.
[1570.62 --> 1572.66]  I'm just trying to trigger the BSD nerds there.
[1572.66 --> 1574.58]  Wait, that was a totally factual statement.
[1574.84 --> 1575.72]  What's, I understand.
[1576.22 --> 1578.84]  Fortunately, my ZFS pool showed up straight away.
[1579.36 --> 1580.78]  You know, the backups pool was there.
[1581.04 --> 1582.04]  Both drives were detected.
[1582.66 --> 1583.54]  I click import.
[1584.36 --> 1586.16]  It looks like it's doing something.
[1586.86 --> 1591.98]  And on Proxmox, this process takes 20 seconds, at most 25.
[1592.76 --> 1598.68]  That time elapses and I'm sort of, you know, watching the progress bar spin.
[1598.68 --> 1604.40]  And then another minute goes by and I'm like, okay, this is taking a bit longer than I thought.
[1604.68 --> 1607.68]  Another minute goes by and nothing's happening.
[1608.14 --> 1608.56]  Uh-oh.
[1608.98 --> 1612.40]  So then I drop to the command line, try and figure out what's going on.
[1613.04 --> 1617.98]  Do a Z pool import list and it shows me all the available pools, including my backups pool.
[1618.08 --> 1623.84]  And I'm like, okay, I'll reboot the box just in case that failed update did something silly.
[1624.24 --> 1626.70]  I didn't do the GUI this time.
[1626.70 --> 1629.96]  I just went straight to the command line, did a Z pool import backups.
[1630.40 --> 1631.56]  It imported the pool.
[1631.96 --> 1633.02]  And I'm like, okay, cool.
[1633.14 --> 1633.56]  No problem.
[1633.80 --> 1634.48]  Z pool list.
[1634.64 --> 1634.82]  Bang.
[1634.96 --> 1635.56]  Straight, straight away.
[1635.64 --> 1636.04]  There it is.
[1636.68 --> 1637.74]  Go to the UI.
[1638.58 --> 1638.94]  Nothing.
[1639.52 --> 1642.36]  So I reboot just in case there's some kind of mismatch there.
[1642.96 --> 1643.32]  Nope.
[1643.48 --> 1644.62]  We need to import the pool again.
[1644.88 --> 1645.62]  And I'm like, oh.
[1646.12 --> 1647.86]  Is it because you're doing it on the command line?
[1648.04 --> 1650.80]  Is there some GUI command to import a pool that maybe you have to use?
[1651.12 --> 1651.70]  Who knows?
[1651.86 --> 1655.56]  I mean, good luck Googling anything for this thing right now because it's so brand new.
[1655.56 --> 1662.20]  And obviously the SEO behind TrueNAS is the last five years of TrueNAS core and FreeNAS before it.
[1662.38 --> 1670.42]  And if I'm honest with you, Chris, I love the audience, but I don't love them enough to waste more than three or four hours trying to figure this thing out.
[1670.66 --> 1674.42]  And eventually after that time elapsed, I was like, screw this.
[1674.48 --> 1675.46]  I'm going back to Proxmox.
[1675.50 --> 1677.94]  I'm going to run my Ansible script and get things back up and running.
[1677.94 --> 1682.74]  So yeah, ultimately, TrueNAS scale was a massive fail for me.
[1682.96 --> 1689.08]  I have typically struggled with these types of products and I often end up just going back to basics.
[1689.66 --> 1695.90]  And I think it's kind of unfortunate because in some ways these guys can unlock stuff for me that I don't even know how to do.
[1695.90 --> 1703.28]  I also feel like there's a spectrum of user that probably prefers something like this, you know, and it works better for them as well.
[1703.34 --> 1705.56]  And I wish I could kind of get my head in that space.
[1705.88 --> 1713.60]  I was tempted for a brief moment to deploy it here at the studio and base our stuff on all that because, well, you know, we were just going to build this YOLO setup.
[1713.60 --> 1725.14]  It was like this crazy cross three system storage array and, you know, maybe even no redundancy, just tons of disks and stupid stuff like that that just has no sensible use.
[1726.16 --> 1728.48]  And then we started thinking, well, what if we wanted to do the opposite?
[1728.62 --> 1731.12]  What if we really wanted to build this thing to be reliable?
[1731.12 --> 1734.00]  We're like, you know, there's failover and all that kind of stuff.
[1734.00 --> 1737.44]  And I got to say, it's on my list of things to consider.
[1737.98 --> 1748.64]  But what my preferred route would be to just build it really simple, build it basic and probably, you know, manage it with something like Ansible.
[1749.20 --> 1752.82]  The simpler you go, the easier it is to recover from a failure too.
[1752.82 --> 1760.84]  Like in my pipe burst scenario, all I have to do is a ZFS send from one box to another and I'm back to where I was.
[1760.84 --> 1772.80]  I think it's very likely too that if you were to check back in, say, I don't know, in episode 85 and see where Chunaz scale is at, I bet you'd be in a totally different state, right?
[1773.00 --> 1777.74]  Even though they've been working on this since 2020, this is a massive reworking of the product.
[1778.10 --> 1783.36]  And it's going to be a little while before it's probably fully, fully cooked.
[1783.36 --> 1791.12]  And I think they even consider it that, like, if you look at like their presentations on this, they're kind of positioning it for more early adopters at this point.
[1791.44 --> 1795.50]  There's a difference between fully cooked and not importing the basic storage pools though.
[1797.58 --> 1800.26]  Tailscale.com slash self hosted.
[1800.50 --> 1803.08]  Go there to get a free personal account for up to 20 devices.
[1803.24 --> 1805.08]  And of course, you support the show.
[1805.24 --> 1808.38]  What I love about tailscale is that it's zero config VPN.
[1808.38 --> 1814.34]  I think it's going to blow your mind how fast you can get this thing set up and then it just runs.
[1814.58 --> 1818.54]  It connects all your devices directly using WireGuard's noise protocol.
[1818.88 --> 1823.40]  So it's as tough as WireGuard, but it's a mesh network.
[1823.62 --> 1831.82]  I was using it today to connect back to LadyJupe's to check in on the Raspberry Pi because I started getting some errors with Uptime Kuma.
[1831.82 --> 1839.66]  I was getting errors because I have Uptime Kuma running here in the studio and it connects back to LadyJupe's over tailscale and checks on stuff for me.
[1840.00 --> 1841.56]  And sure enough, yep, I was having an outage.
[1841.66 --> 1842.66]  It turned out to be Starlink though.
[1844.02 --> 1846.38]  But it was nice to know that I could go check on everything.
[1846.50 --> 1850.34]  And I've created like my own LAN that goes wherever I go.
[1850.40 --> 1853.62]  And it can connect my servers, my workstations, my mobile devices.
[1853.62 --> 1860.70]  Even when you're separated by firewalls or even double NAT, tailscale just works.
[1860.96 --> 1864.94]  I'm using it on my family's computers to help provide remote support now as well.
[1865.34 --> 1869.92]  And I just love that every device essentially gets a static IP address, at least in my world.
[1870.56 --> 1871.34]  It's pretty nice.
[1871.80 --> 1875.86]  I really like the fact that you can use different nodes as exit nodes as well.
[1875.94 --> 1882.04]  So if you want to come out in a different state or a different country for some reason, you can totally do that.
[1882.04 --> 1884.38]  So you use the advertise exit node feature.
[1884.72 --> 1888.10]  And you know, for me and my iPlayer habit, that's very handy.
[1888.62 --> 1889.88]  Yeah, that's a power move right there.
[1890.06 --> 1891.14]  That really is.
[1891.50 --> 1897.20]  And the other thing that's great is that tailscale supports your authentication system, your identity provider.
[1897.38 --> 1899.62]  So you can enforce multi-factor authentication.
[1900.02 --> 1903.00]  You could deauthorize employees or devices and stuff when people move on.
[1903.04 --> 1905.48]  Like you get access and control over all that as well.
[1905.82 --> 1912.02]  So go try it out for free for up to 20 machines and support the show by going to tailscale.com.
[1912.04 --> 1913.74]  Slash self-hosted.
[1916.04 --> 1918.82]  So David asks about keeping Nextcloud going.
[1919.02 --> 1919.76]  Hey, Chris and the Badger.
[1919.86 --> 1923.02]  I've been listening for a while now and I've just started my journey with Nextcloud.
[1923.56 --> 1925.72]  Seems to be a perfect fit for my home lab.
[1925.96 --> 1931.04]  And as I progress with my journey, I can see myself getting more into the, how do I say it?
[1931.54 --> 1933.02]  Enterprise-y way of doing things.
[1933.72 --> 1936.66]  Specifically, I'm talking around monitoring and security.
[1936.66 --> 1943.40]  So what are some of your must-haves when you're deploying things like Nextcloud for that kind of stuff like monitoring and security?
[1943.74 --> 1947.28]  I'm sure your first answer will be everything sits behind WireGuard.
[1947.64 --> 1951.22]  But outside of that, it can be a bit overwhelming to newcomers.
[1951.74 --> 1954.62]  Maybe everything sits at a side tailscale, right?
[1954.62 --> 1957.10]  You know, it's funny.
[1957.32 --> 1959.00]  I actually would go the other way.
[1959.46 --> 1961.92]  You know, I mean, so David asked, what would you install?
[1962.42 --> 1970.92]  My top Nextcloud tip is only load the apps you need and then double check if you really are using them and need them.
[1971.02 --> 1972.96]  And if you don't, unload them.
[1973.24 --> 1973.46]  All right?
[1973.50 --> 1974.52]  So that's my top tip.
[1974.52 --> 1980.42]  But as far as turning stuff on, if you're going to expose Nextcloud to the internet, turn on two-factor authentication.
[1980.96 --> 1985.88]  And it integrates with probably any two-factor authentication system that you love and know.
[1986.38 --> 1987.70]  It's really easy to do.
[1987.78 --> 1988.64]  They've made this simple.
[1988.82 --> 1990.50]  There's an app you can install as well as some settings.
[1990.60 --> 1992.70]  And I'll put a link in the show notes for how to get that going.
[1992.80 --> 2001.70]  Because I think if you just keep Nextcloud up to date, you keep it super lean, you turn on SSL, and you turn on two-factor authentication.
[2001.70 --> 2005.46]  I think that just doing those things, you'd probably be all right.
[2006.02 --> 2008.20]  What's your feeling about updates for Nextcloud?
[2008.34 --> 2012.02]  I think I'm probably five versions behind at this point.
[2012.42 --> 2014.18]  I am a version behind myself.
[2014.44 --> 2017.48]  You know, that's tricky here at JB is we run two Nextcloud instances.
[2018.10 --> 2021.14]  One that you guys interact with up on Linode.
[2021.24 --> 2023.92]  And then we run another instance here in the studio.
[2024.50 --> 2028.16]  It is kind of a pain in the butt to keep it updated, if I'm honest.
[2028.18 --> 2030.04]  Because sometimes there is some work that has to be done.
[2030.04 --> 2033.32]  So what I do is I just whine to Wes and usually get him to do it.
[2033.54 --> 2036.28]  But we do it all through Docker Compose now.
[2036.40 --> 2037.42]  And I'll do it on occasion.
[2037.82 --> 2039.98]  But I have to tell you, it slips.
[2040.68 --> 2041.94]  And I don't like that.
[2042.50 --> 2044.24]  Not everybody has a Wes at their disposal.
[2044.38 --> 2044.94]  You know that, right?
[2045.90 --> 2046.26]  Wes!
[2046.34 --> 2047.42]  You just do it like that.
[2048.00 --> 2052.66]  Thankfully, if you run it all through a container or, you know, some other system you're comfortable with.
[2052.82 --> 2054.48]  I know some of our listeners use the Snap.
[2054.48 --> 2057.92]  Some of those methodologies are actually pretty easy to keep it up to date.
[2058.26 --> 2059.10]  I'm only a version behind.
[2059.20 --> 2059.66]  I just checked.
[2059.76 --> 2060.72]  I'm on version 22.
[2061.10 --> 2062.16]  23 is the latest.
[2062.36 --> 2063.30]  Came out in December.
[2064.02 --> 2064.60]  It's not too bad.
[2064.96 --> 2065.10]  Yeah.
[2065.18 --> 2066.70]  In my head, I'm like three behind.
[2066.80 --> 2067.96]  In reality, I'm only one behind.
[2069.48 --> 2070.88]  But I feel that pressure.
[2070.88 --> 2079.44]  Another important thing, David, would be to make sure that you are really cognizant about how you actually deploy NextCloud in the first place.
[2079.92 --> 2081.62]  As Chris mentioned, some people use a Snap.
[2082.02 --> 2083.14]  Other people use a container.
[2083.42 --> 2085.76]  Other people do it by running it on the host itself.
[2086.70 --> 2095.44]  And one of the most common ways I've seen listeners lose data is by not remembering how they set something up six months, a year, two years ago.
[2095.44 --> 2098.20]  And then their server goes down for some reason.
[2098.36 --> 2107.50]  They've got a copy of the data from the sync client on their local system, but they don't have a way to reconstruct the database and the users and everything as it was.
[2107.80 --> 2109.92]  So use something like Docker Compose.
[2110.04 --> 2113.98]  It would be my recommendation for a repeatable deployment method.
[2114.56 --> 2118.94]  Whatever you do, whether it's Compose or whatever, make sure you write it down somewhere.
[2119.56 --> 2119.90]  Well said.
[2120.28 --> 2120.84]  Well said.
[2121.46 --> 2122.62]  Plus one on that.
[2122.62 --> 2125.26]  John writes in, looking for a simple way to get started.
[2126.26 --> 2127.82]  He says, I hope you guys can help me here.
[2127.88 --> 2132.18]  I'm starting to dive further into self-hosting, and I have a couple of Mac mini servers at home.
[2132.22 --> 2144.14]  And I was thinking about setting up the M1 box with either Docker, maybe with Portainer, or Unraid to start and learn about implementing containers for apps such as Plex Media Server, Home Assistant, TDAR, et cetera, et cetera.
[2144.74 --> 2150.56]  I want to have a GUI as I'm not a coder, apart from following how-to videos from YouTube and using terminal commands.
[2150.56 --> 2151.60]  What would you suggest?
[2151.84 --> 2153.36]  Cheers, John.
[2153.36 --> 2157.46]  Well, I think Unraid is a bloody brilliant place to start, to be honest with you.
[2157.64 --> 2164.02]  It's a really great mix of UI, community, and documentation.
[2164.64 --> 2168.76]  And I think those three things together make a perfect mix for newcomers.
[2168.76 --> 2179.26]  A lot of people that are running Unraid do so because they are new to serving stuff at home, you know, media servers, what have you.
[2179.26 --> 2184.42]  By this point, Unraid's been around for, I want to say, like 15 years.
[2184.42 --> 2202.76]  So not only do you have that mix of noobs, for want of a better word, but you've also got that mix of really experienced, passionate users that want other people to be as excited about their special little thing that they found 10 years ago and has been working perfectly for them ever since, you know.
[2202.76 --> 2207.42]  And there's very few products on the market that do what Unraid does.
[2207.92 --> 2214.84]  One of the things that makes it so great is the fact that you can stick any kind of hard drive in there, you know, like a JBOD style.
[2214.84 --> 2219.84]  There's no real kind of constraints around, like there is with ZFS, for example.
[2220.50 --> 2226.62]  You've got to do a matched pair for a VDEV, and if you exceed the VDEV, you lose data and yada, yada, yada.
[2227.40 --> 2228.34]  Unraid's really simple.
[2228.80 --> 2233.90]  If you have a parity disk, it has to be the biggest disk in the array or as big as.
[2234.58 --> 2238.06]  If that fails, you've lost your fault tolerance.
[2238.58 --> 2242.34]  And if any further drive fails, you lose the data on that drive.
[2242.34 --> 2247.46]  And that's really simple to understand, and I think just that simple thing hooks a lot of people into Unraid.
[2248.10 --> 2250.08]  But then you start looking at things like the community.
[2250.26 --> 2253.02]  There's lots of videos from a chap called Space Invader 1 on YouTube.
[2253.58 --> 2259.30]  He does really great, simple-to-follow tutorials where, you know, you click here, you do this, you do that, and off you go.
[2259.78 --> 2264.48]  As you grow, you might find the guardrails that Unraid has are a little bit restrictive.
[2265.16 --> 2268.14]  But as a new user, that's a good thing, in my opinion.
[2268.14 --> 2274.32]  I don't know if I've heard of anybody running Unraid on a Mac Mini, especially not an M1 Mac Mini.
[2274.92 --> 2277.98]  I also don't know if Portainer works on Mac OS.
[2278.14 --> 2281.28]  You'd probably end up using Docker Desktop on Mac OS.
[2281.82 --> 2286.16]  He talks about wanting a GUI, and Unraid's definitely an option.
[2286.52 --> 2287.86]  Maybe FreeNAS Scale's an option.
[2287.86 --> 2294.00]  If you want to manage some disks, if you're just going to have, like, one disk, and you just want to run some applications,
[2294.86 --> 2299.12]  you know, Alex, I almost wonder if it's worth considering the whole Home Assistant stack.
[2299.96 --> 2304.74]  You know, because if ultimately he wants Home Assistant anyways, when you install Managed Home Assistant,
[2305.02 --> 2308.88]  you get an app store, essentially, that lets you install things like Plex.
[2309.36 --> 2311.16]  And it just does it all through Docker containers.
[2311.16 --> 2317.30]  The only trick is you have to install it, I mean, generally, like, they release a Raspberry Pi image or something like that.
[2317.76 --> 2325.72]  But it does offer a way to run a lot of these popular, open-source, self-hostable applications with just a few clicks.
[2326.26 --> 2331.90]  Because Home Assistant itself manages, has a supervisor part that can manage all these containers.
[2331.90 --> 2336.90]  Otherwise, yeah, probably something like Unraid or FreeNAS.
[2337.20 --> 2344.84]  Or there's also just the option of doing something like CentOS or Ubuntu and using something like Cockpit on top of that.
[2345.02 --> 2349.70]  I know that's getting a little more advanced, but he did say he was comfortable using terminal commands.
[2350.12 --> 2351.24]  And so that's another choice.
[2351.64 --> 2353.82]  But let us know how the journey goes, John.
[2354.40 --> 2358.04]  I'll do a final shameless plug for perfectmediaserver.com.
[2358.04 --> 2362.40]  If you want to just do things from the command line, I think that's probably the way to go.
[2363.26 --> 2371.26]  Well, behind the scenes, we are making secret, not-so-secret plans for a JB East Coast meetup.
[2372.14 --> 2377.74]  And, of course, in the planning phase, what's come up is like, how the hell are we going to pay for this?
[2377.94 --> 2380.72]  And it got us talking, and I don't think we're going to do it for this.
[2380.84 --> 2386.80]  But down the road, there may be a project or something like a special edition of a show or maybe some special trip.
[2386.80 --> 2389.52]  But how would we, if we wanted to, do crowdfunding?
[2389.60 --> 2392.76]  And we thought, well, we'd like it to be open source and self-hostable.
[2393.30 --> 2399.82]  I went out there and did a little looking around, and it looks like a lot of those projects have died or become abandoned over the years.
[2399.96 --> 2407.56]  So if you know of a self-hosted crowdfunding application that's alive and well, maybe you're using it, let us know about it.
[2408.02 --> 2409.48]  Selfhosted.show.contact.
[2409.54 --> 2413.90]  Because if it was ever something JB did want to get into, we'd like it to kind of align with our values.
[2413.90 --> 2417.66]  I can't believe it's taken us until this point in the show to actually even mention this.
[2418.02 --> 2418.94]  But I know.
[2419.42 --> 2424.54]  April the 9th in Raleigh, we're going to have an East Coast JB meetup.
[2424.78 --> 2431.64]  And rumor has it that a certain RV dwelling podcaster might be joining us.
[2431.88 --> 2432.26]  It's true.
[2432.30 --> 2433.58]  Although I'm going to fly in.
[2433.58 --> 2445.48]  I think, I'm hoping, it'll be a life goal if it's like one part mini vacation with the fam, because it'll be my son's 13th birthday and spring break.
[2445.48 --> 2448.64]  And he is a Bitcoin nut.
[2448.90 --> 2458.48]  So we're hoping we could fly into Miami, go to the Bitcoin conference for a couple of days, and then fly up and hang out with you and the family and then go to a meetup.
[2458.58 --> 2460.18]  Like, it's all in the planning phase.
[2460.80 --> 2467.82]  But Alex, we have needed to do an East Coast JB meetup for about 15 years.
[2467.96 --> 2469.88]  I mean, it's embarrassingly bad.
[2469.88 --> 2475.92]  And, you know, you and the community just were like, screw it, we're just going to get something started.
[2476.22 --> 2483.66]  And I was talking behind the scenes thinking, you know, I'm feeling like I really need, I need to, like, take a little bit of a trip.
[2483.76 --> 2484.80]  I am really feeling burned out.
[2484.86 --> 2485.84]  Like, I need to do something.
[2486.38 --> 2490.60]  And this Bitcoin conference came up, and this meetup came up, and it's like, this is almost too perfect.
[2491.06 --> 2492.72]  So behind the scenes, we're trying to figure it out.
[2493.36 --> 2499.20]  Well, of course, normally, you're busy planning for LinuxFest Northwest, but for obvious reasons, that's still on hiatus.
[2499.38 --> 2499.78]  Right.
[2499.88 --> 2505.96]  And that was actually how the conversation started, because that's usually, like, a nice little way for us to connect with the community once a year.
[2506.26 --> 2508.52]  And we're going on two years now of not having it.
[2508.60 --> 2509.56]  It's like our big event.
[2509.96 --> 2512.32]  And you found a great spot, too.
[2512.42 --> 2517.66]  So it's like, God, it just all seems like it's coming together, like a nice spot and great weather on the East Coast.
[2518.04 --> 2521.56]  Right on Dylan's birthday spring break, I'm like, oh, let's do it.
[2521.82 --> 2522.92]  So we're figuring it out.
[2523.46 --> 2525.30]  Let me paint a picture for the audience, right?
[2525.30 --> 2532.40]  So Prime Barbecue is a Texas-style barbecue joint that's just opened just outside of Raleigh.
[2532.52 --> 2533.48]  It's a place called Nightdale.
[2533.48 --> 2536.44]  And it looks out over this big park.
[2536.52 --> 2540.48]  And on the other side of the park is a place called Oak City Brewing.
[2540.74 --> 2545.02]  So what I'm thinking is two, three o'clock in the afternoon, something like that.
[2545.08 --> 2547.84]  We'll put all the details on meetup.com closer to the time.
[2548.24 --> 2556.72]  But something like two or three o'clock in the afternoon on the Saturday, we'll meet at the barbecue place, go get some food, sit on the lawn, go and eat and mingle with people.
[2556.72 --> 2562.34]  And then as the evening progresses, we can head across the brewery and go and get some drinks.
[2562.58 --> 2568.96]  And I've been racking my brains for the last few weeks about where we could go in town that was kind of a COVID-safe location.
[2569.54 --> 2574.78]  And the beauty of this place is we can all congregate in this place together, but we're outside.
[2575.32 --> 2575.46]  Right.
[2575.52 --> 2580.98]  And the weather in Raleigh in April is going to be lovely, of course, apart from the pollen, maybe that might be a thing.
[2581.48 --> 2584.62]  But on the whole, I think it'll be a lovely day for everybody.
[2584.62 --> 2587.36]  And it's going to be right next to some great stuff.
[2588.00 --> 2588.12]  Yeah.
[2588.20 --> 2591.04]  So the thing to do would be to join our meetup.
[2591.62 --> 2600.46]  We don't have like one set for this, but you could join the group at meetup.com slash Jupyter Broadcasting or join the Discord, self-hosted.show slash Discord if you have questions.
[2600.74 --> 2607.46]  But when we get our details solidified, which we're really close to, hopefully, we'll probably make a proper meetup post about it.
[2607.46 --> 2615.26]  But the provisional plan, like I say, is Saturday, April 9th, 2 or 3 p.m. until we all get bored and want to go home.
[2615.64 --> 2616.20]  Something like that.
[2616.46 --> 2619.42]  If you're anywhere in the area, we don't make it out to the East Coast too often.
[2620.92 --> 2621.92]  So come join us.
[2621.96 --> 2622.72]  It'd be a lot of fun.
[2623.20 --> 2625.06]  And also, thank you to our members.
[2625.06 --> 2627.88]  You know, you guys really help us keep the show on the road.
[2628.08 --> 2633.28]  And you also give us the freedom to wait until a great sponsor like Tailscale comes along.
[2633.68 --> 2637.36]  You know, like you give us leverage there to make wise choices.
[2637.56 --> 2639.52]  You give us runways, they say in the business.
[2640.08 --> 2642.34]  Self-hosted.show slash SRE if you'd like to join.
[2642.76 --> 2644.32]  As a perk, you get more show.
[2644.54 --> 2645.66]  You get a post show.
[2645.90 --> 2649.18]  You can also support the entire network, just like the cost of two memberships.
[2649.18 --> 2653.80]  And you support all the shows and you get all the shows ad free, plus that post show.
[2654.26 --> 2657.20]  That network support is at jupiter.party.
[2657.72 --> 2662.72]  And as you all know by now, the place to go to get in touch with us is self-hosted.show slash contact.
[2662.92 --> 2665.66]  You can find me on the Discord at AlexKTZ.
[2665.88 --> 2667.80]  And you can find me on Matrix.
[2667.98 --> 2669.64]  Come join us in the self-hosted Matrix.
[2670.28 --> 2673.28]  Our Matrix server is colony.jupiterbroadcasting.com.
[2673.40 --> 2674.62]  And I didn't mention it in the show.
[2674.78 --> 2675.92]  And it's just a very quick addendum.
[2676.10 --> 2678.74]  Big thanks to Jake, the real orange one, the orange one,
[2678.74 --> 2683.54]  whatever his handle is this week, for running our Matrix party thing,
[2683.64 --> 2685.38]  setup party that we had a couple of weeks ago.
[2685.82 --> 2686.36]  Went really well.
[2686.42 --> 2687.82]  We had about 30 people show up.
[2688.18 --> 2689.66]  It was a fun time on a Sunday.
[2689.86 --> 2692.32]  So big thanks to Jake for setting that up.
[2692.80 --> 2694.88]  And as always, thanks for listening, everybody.
[2695.08 --> 2697.52]  That was self-hosted.show slash 65.