50： Perfect Plex Setup _transcript.txt

[1.00 --> 8.72]  You're now listening to Chris and the Badger, a presentation of the self-hosted podcast with Chris.
[9.16 --> 13.64]  A lot of options out there, but you can use this stack. I've tested this. I've refined it over the years.
[13.72 --> 14.44]  And Alex.
[14.58 --> 17.82]  I don't think there's a better solution, really, if you're willing to put the effort in.
[17.90 --> 20.16]  And featuring special guests.
[20.96 --> 22.42]  Morgan the doorbell guy.
[22.60 --> 23.98]  Wes Payne.
[24.22 --> 24.90]  An RV.
[25.50 --> 25.98]  JDM.
[26.20 --> 26.54]  What?
[27.54 --> 28.72]  Jonathan from Unraid.
[28.72 --> 30.46]  Hang on a sec. This goes on for a while.
[31.82 --> 32.26]  Geerling.
[32.68 --> 33.92]  And your hosts.
[34.38 --> 36.40]  Who are celebrating episode...
[36.40 --> 37.50]  Oh, come on.
[38.12 --> 38.64]  Hang tank.
[39.42 --> 39.74]  All right.
[40.26 --> 41.04]  And Jeff Geerling.
[41.22 --> 42.48]  Okay, now your hosts.
[42.62 --> 43.90]  Snap Raid and Merger FS.
[44.32 --> 46.10]  And I endorse this media server build here.
[46.32 --> 48.14]  Celebrating episode number 50.
[48.38 --> 50.62]  A long-term relationship with same thing.
[50.78 --> 51.88]  I think, what else could I do with it?
[51.92 --> 54.68]  And that single spark is a huge rabbit hole.
[54.68 --> 55.50]  Huge rabbit hole.
[56.08 --> 57.30]  Chris and Alex.
[58.72 --> 61.00]  Well, welcome to episode 50, everybody.
[61.24 --> 65.44]  I hope you liked our special intro to celebrate the 50th episode.
[66.02 --> 66.58]  Yeah, that's great.
[67.00 --> 68.94]  Congratulations, Alex, to episode 50.
[69.04 --> 73.08]  And thank you to, oh, yeah, in our Discord for making that awesome intro.
[73.66 --> 77.70]  Now he's got to make a special edition show themes all the time.
[77.76 --> 78.90]  That was amazing.
[79.40 --> 80.36]  And it's here, Alex.
[80.92 --> 81.74]  50 episodes.
[81.80 --> 84.32]  And it takes a while when you're doing them only twice a month.
[84.64 --> 85.56]  It's been a long haul.
[85.56 --> 87.12]  Yeah, 50, huh?
[87.46 --> 91.06]  It means, what, nearly two years of doing this with you.
[91.50 --> 96.18]  And to celebrate, we've actually got some merch available for the first time.
[97.96 --> 100.94]  This really was all really driven by Alex.
[101.00 --> 102.06]  He wanted to see this done.
[102.74 --> 103.90]  Of course, I wanted to see it too.
[104.12 --> 108.62]  But Alex really took the lead and made sure we got something special for you guys for episode 50.
[109.02 --> 111.54]  We have it up at jupitergarage.com.
[111.54 --> 118.32]  We've got a couple of special shirts, a Chris and the Badger shirt and a self-hosted logo shirt, if you'd like that.
[118.44 --> 127.42]  And we also have a couple exclusive stickers, a self-hosted square sticker, and of course, a Chris and the Badger sticker, which would look great on your machine, I got to say.
[127.82 --> 128.70]  Yeah, I think it would too.
[128.70 --> 135.88]  I mean, I think it was when Drew, who's our editor, sent me a little electronics project full of parts.
[135.88 --> 140.78]  And it said, to the Badger on the corner, I was like, we need to lean into this a bit more, don't we?
[140.82 --> 142.10]  Yeah, we are leaning into it.
[142.42 --> 144.96]  I think with episode 50, we're just like, we're doing it.
[145.36 --> 146.00]  We're doing it.
[146.00 --> 148.80]  And it's because, you know, people kind of came together and helped us make it special.
[149.54 --> 151.54]  So that's up there right now.
[151.54 --> 158.70]  And if you are a self-hosted SRE, one of our members, then check out the post show and check out your member feed.
[158.78 --> 163.60]  We will have a special promo code for you to take a little bit off the gear.
[163.76 --> 165.94]  But it's all actually at a really great price right now.
[166.00 --> 171.04]  We're basically running it pretty close to cost as it is because we just wanted to have something special out there for episode 50.
[171.40 --> 174.26]  So all of it is up at jupitergarage.com.
[174.26 --> 181.22]  And if I could just take a moment to interject and just say a huge thank you personally to all of you for listening to all these episodes.
[181.54 --> 192.50]  It's a real privilege to do this show with you, Chris, but also be able to present to the audience that we have who engage on Discord so well and on Twitter and all that kind of stuff as well.
[192.58 --> 195.90]  So it's been a huge privilege for me and a big, big thank you.
[196.42 --> 201.18]  And we want to say thank you to a cloud guru, the leader in learning for the cloud, Linux and other modern tech skills.
[201.18 --> 203.84]  They have hundreds of courses and thousands of hands-on labs.
[204.26 --> 208.66]  So go get certified, get hired and get learning at a cloudguru.com.
[209.22 --> 213.60]  Well, I'd imagine that you're still rebuilding from the great flood of a few weeks ago.
[213.70 --> 214.26]  How's that going?
[214.70 --> 217.12]  It is indeed an ongoing process, Alex.
[217.66 --> 219.10]  We'll just say that, I guess.
[219.52 --> 225.04]  I actually did pick up a couple of quick tips that I'll share in a bit in the show from this entire experience.
[225.04 --> 228.00]  And so I guess there's a bit of a silver lining there to it.
[228.32 --> 229.90]  But I haven't replaced everything.
[230.26 --> 233.28]  I have successfully saved a couple of items.
[233.44 --> 234.42]  So that's awesome.
[235.06 --> 238.84]  But for the most part, I'd say like 90% of everything was a loss.
[239.44 --> 240.12]  Oh, damn.
[240.64 --> 241.82]  I mean, I hope you had insurance.
[242.24 --> 244.10]  Well, some of it's just old gear, you know.
[244.10 --> 246.74]  Some of it's just old stuff like chargers and whatnot.
[246.88 --> 249.12]  I suppose I could probably try to do the insurance thing.
[249.86 --> 254.28]  I have a box in the attic full of old English for some reason.
[254.62 --> 255.90]  They made it across the channel.
[256.44 --> 256.84]  Channel?
[257.16 --> 257.52]  Ocean.
[258.04 --> 260.06]  I have a box full of English power adapters.
[260.34 --> 262.66]  And so they're the sort of things that just hang around forever.
[262.66 --> 267.94]  So maybe it's a good thing that you douse them all with, you know, 17 gallons worth of water.
[268.58 --> 270.96]  And I do need to kind of like change up my charging situation.
[271.08 --> 279.78]  See, what I got going in this area is a charging station, you could say, for all of the kids' iPads and switches and controllers.
[280.28 --> 290.44]  And so this whole situation has actually inspired the wife and I to cap the water pipes at that area, remove the faucet completely.
[290.44 --> 299.54]  And then after we get back on the impending Denver road trip, we're going to build a shelving system in there where the kids can slide their devices into shelves and they'll have power cords pre-run.
[299.90 --> 305.98]  So the whole incident's actually inspired us to really kind of up our game instead of just having like this loose area where we stash stuff near a sink.
[307.46 --> 310.08]  But it just took the disaster to kick our butts into gear, I guess.
[310.26 --> 317.58]  You know, one of these days I might convince you to get a 3D printer and custom print the right size inserts for the devices.
[317.58 --> 328.40]  And there's been a couple of fixes and a couple of projects for this road trip a couple of times now, because this is one of the bigger trips, because we're going to be on the road for probably about 40 days straight.
[328.58 --> 335.68]  If you think about that in terms of just wear and tear on a vehicle and the house box that is running on top of that vehicle, that's a lot.
[335.78 --> 338.36]  And so there's been a lot of things we're doing to prepare for it.
[338.36 --> 346.16]  And I've thought a couple of times, a few things I'm replacing, like trying to get a magnet on my door so that lines up with the sensor and trying to just position that magnet just right.
[346.62 --> 351.64]  If I could have built a little 3D housing for that to just position it where I needed it, it would have been job done.
[352.44 --> 353.26]  It's on my mind.
[353.64 --> 354.28]  It may happen.
[354.64 --> 356.40]  You have a few options of cheap 3D printers.
[356.64 --> 359.06]  I mean, there's a Prusa one that's the Prusa Mini.
[359.16 --> 360.82]  It's about 400 bucks delivered.
[361.82 --> 363.10]  Ender makes some.
[363.26 --> 364.42]  Creality makes some as well.
[364.42 --> 368.18]  But I had bad experiences with the Chineseian printers.
[368.86 --> 371.90]  And personally, I'm a huge fanboy of Prusa because they open source everything.
[372.30 --> 378.10]  And nine times out of ten, the print just works, which is what I'm in 3D printing for.
[378.20 --> 382.34]  I'm not really in it to tinker and 3D print new parts for my printer.
[382.44 --> 383.94]  I want to print cool stuff, you know.
[384.48 --> 388.62]  I just figured I'd wait for you to upgrade your current rig and then I'd buy this one off you used.
[389.74 --> 390.98]  That does tend to happen.
[392.00 --> 392.64]  Yeah, yeah.
[392.68 --> 393.14]  We'll see.
[393.14 --> 393.76]  We'll see.
[393.76 --> 395.78]  But we will be in Denver soon.
[395.86 --> 396.52]  We're going to have a meetup.
[396.60 --> 398.72]  Alex is going to be there running trivia night.
[399.00 --> 401.62]  So go to meetup.com slash Jupiter Broadcasting.
[401.82 --> 405.60]  I think it's August 20th, a Friday that we're going to be in Denver doing the meetup.
[405.82 --> 407.70]  There's also a meetup coming up in Salt Lake City.
[407.94 --> 408.96]  Just only I will be there.
[409.06 --> 410.36]  Alex won't be making it to that one.
[410.64 --> 413.24]  But details for that are at meetup.com slash Jupiter Broadcasting.
[413.78 --> 415.80]  It's going to be weird getting on a plane, I'll tell you that.
[416.28 --> 418.24]  How long of a flight is it to Denver for you guys?
[418.66 --> 420.60]  About three or four hours, I think.
[420.60 --> 424.88]  It really is just the perfect midpoint between you and me, isn't it?
[425.02 --> 426.66]  It's like right there smack dab in the middle.
[426.98 --> 428.80]  Yeah, it's either that or the middle of Arkansas.
[430.46 --> 436.80]  Most of the crew is flying out with the exception of myself, of course, my wife and Brent.
[437.64 --> 446.52]  Brent, you know, from Brunch with Brent is flying into Seattle and then he is going to caravan out with the family and I in Lady Joops.
[446.52 --> 448.30]  Oh, I'm so jealous.
[448.78 --> 451.70]  Brent is a precious resource that we have to share out carefully.
[451.94 --> 452.84]  We do, yeah.
[453.36 --> 455.74]  Yeah, well, he'll have his fill of us, I think, by the time.
[457.22 --> 458.20]  I mean, you know.
[458.56 --> 459.68]  It's actually going to be pretty great.
[459.76 --> 460.50]  The kids are excited.
[461.66 --> 466.72]  This is going to totally, this is going to, like, enshrine him as Uncle Brent at the end of this road trip, you know.
[466.88 --> 467.88]  So that'll be pretty great.
[468.38 --> 469.48]  And I'm really looking forward to it.
[469.68 --> 471.28]  Well, I'm extremely jealous of that.
[471.42 --> 473.96]  And I hope you have a great time on the road.
[473.96 --> 476.04]  I've always wanted to do Salt Lake City.
[476.24 --> 478.40]  I never quite made it that far north in Utah.
[478.62 --> 484.50]  We did Arches and Dead Horse State Park and that kind of stuff near Moab a couple of years ago.
[484.74 --> 485.80]  That was amazing.
[486.06 --> 488.44]  If you're ever in that area, amazing, amazing stuff.
[488.90 --> 489.70]  Absolutely love it.
[489.86 --> 490.12]  Totally.
[490.24 --> 490.84]  You're absolutely right.
[490.88 --> 491.98]  It's like another world.
[492.06 --> 494.28]  It feels like you're on a set of Star Trek when you're in Moab.
[494.48 --> 494.78]  Mars.
[494.86 --> 499.20]  You know, Salt Lake City was a promise I made to the audience because it's not, like, exactly on our way to Denver.
[499.20 --> 504.50]  But I made a promise to the audience that when we could, we'd return to Salt Lake City because we had to skip it.
[504.72 --> 505.58]  We had a whole thing planned.
[505.68 --> 506.26]  We had to skip it.
[506.30 --> 509.74]  So this is making good on a promise to the audience in Salt Lake City.
[510.34 --> 518.62]  Perhaps this is an entirely gross misrepresentation of Salt Lake City, but it's kind of colored to me by the Book of Mormon, if you've seen that.
[518.62 --> 523.70]  I mean, you know, it gets a lot.
[524.28 --> 533.38]  Actually, just sort of tangentially related to that, when we were trying to book a venue, we had to listen to a whole bunch of rules about alcohol that we have never had to sit through from any other state.
[535.08 --> 535.80]  It's a thing.
[536.04 --> 536.60]  It's a thing.
[536.60 --> 547.02]  Well, when you've had one too many beers after a meetup, the last thing you want is to be fumbling around for a phone in your pocket or trying to remember what voice command you programmed into the lady cylinder this week.
[547.10 --> 549.28]  Have you got a solution to that?
[549.64 --> 553.42]  I had a fire tablet that worked pretty well before I got water destroyed because it fell out.
[553.50 --> 554.34]  It was off the wall.
[554.46 --> 555.80]  It fell into the water bath.
[556.34 --> 562.36]  But also, you know, Brent's going to be on board and he doesn't know all those special commands and he's going to want to control things.
[562.36 --> 573.54]  So I wanted to get that tablet on the wall replaced, which runs my home assistant dashboard 24-7 because it makes it easier for the family and it makes it easier for guests.
[574.08 --> 578.04]  And, yeah, it makes it easier when you just can't remember what, you know, what did I call that group of lights again?
[578.10 --> 578.72]  I can't remember.
[579.72 --> 588.28]  So at a bit of, I'd say, maybe laziness and at a bit of budget concerns, I've been picking up the Amazon Fire tablets.
[588.28 --> 594.54]  And I don't really want to invest in a system where I need to reflash these things.
[594.70 --> 595.78]  It's not that I'm against it.
[595.80 --> 597.08]  I used to love doing that.
[597.50 --> 602.26]  It's just kind of, it crosses an effort line for me that I'm willing to put into this kind of device.
[602.78 --> 604.96]  Beyond that, I'd rather just get like a used iPad.
[605.52 --> 610.06]  Well, we talked a little bit about flashing lineage on my old Kindle Fire a little while ago.
[610.38 --> 610.66]  Right.
[610.74 --> 613.96]  And for me, it's just, it's just not quite worth the effort.
[614.50 --> 615.98]  The tablets kind of suck already.
[615.98 --> 621.84]  And so if I have to do all this extra work, it just, it kind of like loses the value for me a little bit.
[622.04 --> 627.44]  I wanted to see if I could find a nice sweet spot where I could still pick up a Fire tablet for a great price off of Amazon.
[628.24 --> 635.50]  And then just easily and quickly modify it for my needs, which is mount it to a wall and run Home Assistant dashboard all day.
[636.00 --> 641.38]  And so a couple of projects that I found made it exactly what I was shooting for that kind of like that sweet spot in the middle.
[641.78 --> 644.14]  And I picked up a 10 inch Amazon Fire tablet.
[644.14 --> 648.24]  I opted to go for the ad free one because again, I'm not going to reflash this thing.
[648.56 --> 657.84]  But if you were going to reflash the thing, you could, you could save a few bucks and you could get the version that comes with ads on the lock screen, which is so obnoxious.
[658.18 --> 663.12]  In fact, I've bought the no ads version in the past and still received the version that comes with the ad.
[663.12 --> 666.14]  So I could totally understand if you wanted to reflash it.
[666.20 --> 667.78]  But I, that wasn't what I wanted to do.
[668.10 --> 670.66]  I wanted to use this app that I found called Wall Panel.
[670.90 --> 674.82]  It's an Android application for web-based dashboards like Home Assistant.
[674.98 --> 676.24]  Like that's what's in a lot of their screenshots.
[676.98 --> 678.64]  And you could sideload it if you want.
[678.64 --> 687.58]  But they've also submitted Wall Panel to the Google Play Store and to the Amazon App Store, which means it makes it stupid easy to get it up and going on a Fire tablet.
[687.86 --> 690.94]  It has really great fast camera motion detection too.
[691.08 --> 693.82]  So now what I can do is sleep my screen.
[694.24 --> 698.34]  And then when the front facing camera detects motion, it wakes the screen up.
[698.46 --> 701.10]  And that's actually surprisingly handy.
[701.38 --> 704.82]  You approach the tablet and as you're approaching it, the screen just becomes available.
[705.08 --> 707.18]  And then I have it set to like a three minute sleep window.
[707.18 --> 713.22]  You can have a pin code option in there to kind of lock the screen out if you don't want to just give anyone access to your dashboard.
[713.94 --> 727.44]  And with the ease of access and installing this thing and the power options for keeping the screen awake and all that kind of stuff, it gets me 90% of the way there with a stock Amazon Fire tablet.
[727.76 --> 728.58]  So it's Wall Panel.
[728.72 --> 730.14]  I'll have a link in the show notes for that.
[730.84 --> 733.18]  So what if I did want to reflash it or tinker with it?
[733.38 --> 734.18]  What can I do there?
[734.62 --> 735.94]  There are a couple of options there.
[735.94 --> 739.82]  The one that I think I'd recommend like the next step up from Wall Panel.
[740.38 --> 742.26]  You may have seen this over at the XDA forums.
[742.36 --> 744.06]  It's called the Amazon Fire Toolbox.
[744.54 --> 762.08]  And this uses the Android debug bridge to apply tweaks to the Fire tablet from completely reflashing them to just doing things like maybe installing Google Play or removing some of Amazon's annoying software that's on there to just completely replacing the version of Android.
[762.08 --> 766.52]  If you like the downside is you got to use Windows.
[766.52 --> 769.42]  And I just don't really have access to a Windows machine.
[769.50 --> 770.66]  It's a Visual Basic app.
[771.06 --> 772.84]  They say they're going to work on Linux support.
[772.84 --> 777.64]  But Datastream33 who kind of hangs out over the XDA forums.
[777.72 --> 778.98]  He's a senior member over there.
[779.38 --> 781.12]  It's his project or their project.
[781.54 --> 783.18]  And they're a Windows user right now.
[783.24 --> 784.14]  So they're making it for Windows.
[784.14 --> 788.00]  So it's not really something that I have quick access to.
[788.12 --> 792.42]  But the idea is you plug your Fire tablet into your Windows box.
[792.50 --> 793.72]  You load this toolbox up.
[793.72 --> 806.08]  And then that gives you a GUI with a bunch of options in there that just kind of can go in there and lobotomize the Amazon stuff out of the tablet if you want and give it actual genuine Google Play Store APIs.
[806.88 --> 808.84]  Who doesn't want to lobotomize a tablet, huh?
[809.34 --> 812.92]  Well, I mean, have you seen the nag where they put on these things?
[812.92 --> 826.60]  They want you to buy everything that Amazon makes and they want to turn it into an Alexa and they also want you to turn it into an Audible station and they also want you to turn it into a Prime streaming machine and they put all this stuff all over it.
[826.68 --> 828.40]  And I just wanted to run one single app.
[828.88 --> 836.86]  You know, I was worried about this kind of thing because in days past you had to route things and reflash bootloaders and that kind of stuff.
[836.86 --> 845.54]  And I read a long time ago that warranty claims were refused if people had done modifications like this to these ad-supported devices.
[845.72 --> 847.36]  Is that still the case now?
[848.04 --> 857.36]  So the nice thing about the toolbox that we were just talking about from XDA, that's not messing with like the system restore partition on your Fire tablet.
[857.54 --> 861.26]  So you could go in there and like lobotomize the Amazon stuff out of the image.
[861.66 --> 866.50]  And then if you needed to, reset it to factory defaults and it just restores it to a stock Fire tablet.
[866.50 --> 869.74]  So your warranty is good if you just did that before you sent it in.
[870.10 --> 870.62]  Yeah, that makes sense.
[870.72 --> 871.96]  I mean, it's just software, isn't it?
[872.08 --> 878.38]  I mean, unless there's like an intrusion detection in the firmware, I don't see how they'd ever know.
[878.68 --> 880.08]  Well, yeah, they could do that, I suppose.
[880.16 --> 881.10]  But thankfully they're not.
[881.56 --> 885.60]  But that's where wall panel is kind of this nice starting point.
[885.80 --> 888.98]  And you could just start with that for these on-wall dashboard.
[889.30 --> 895.64]  This is, I think, such a great way to make home automation more accessible to your family is a visual way for them to control things.
[895.64 --> 899.96]  And with the Home Assistant dashboard setup, you could make something really appealing to people.
[900.08 --> 902.22]  And it renders really great on a 10-inch tablet.
[903.18 --> 907.72]  And wall panel has an option to turn on by default when the tablet boot.
[907.80 --> 913.78]  So it kind of just launches immediately and kind of papers over all that Amazon stuff.
[914.02 --> 918.00]  And it really gets you like 90% of the way there super quick.
[918.60 --> 919.50]  What's the last 10%?
[919.98 --> 922.26]  I think the last 10% would be replacing the OS.
[922.26 --> 925.02]  You know, because then you could put something a little more modern on there.
[925.48 --> 930.74]  Because Amazon's Fire Android OS space is often behind mainline Android.
[931.24 --> 931.38]  Well, yeah.
[931.44 --> 941.26]  I mean, I saw today just in the JB Telegram chat that people were talking about the, I think it's like a 12-year-old Kindle is getting internet access revoked or something by Amazon.
[942.22 --> 943.76]  Turning it into e-waste, essentially.
[944.34 --> 945.44]  You know, that's a tricky one.
[945.68 --> 947.48]  The cellular networks eventually get shut down.
[947.58 --> 950.04]  I think that's things like on the 3G network or something, right?
[950.04 --> 951.94]  Because it's pretty old, I mean.
[952.38 --> 953.92]  Yeah, eventually they got to shut down the network.
[953.92 --> 963.52]  But it really kind of does make you think, like, if you want something to last a really, really long time, you've got to look at ways of self-hosting it.
[964.16 --> 967.76]  And maybe some devices just aren't the right fit.
[967.88 --> 972.52]  Although you could argue 12 years is a pretty good value proposition when you consider new Kindles are like $100.
[972.84 --> 974.60]  Like, back then those Kindles were not that cheap.
[974.86 --> 976.14]  But new Kindles are a lot cheaper.
[976.94 --> 977.48]  Well, very good.
[977.48 --> 986.40]  I think next time there's a Black Friday sale or some kind of Amazon invented Prime Day thing, I might pick up a Fire tablet and just give that a go.
[986.92 --> 991.80]  The one that I flashed with Lineage a little while ago has been doing perfect duty, actually,
[991.90 --> 1002.14]  as we've been using one of the Wyze Cam V3s with that Lineage OS 7-inch Fire tablet from half a decade plus ago as our baby monitor.
[1002.14 --> 1003.90]  And it's been working brilliantly well.
[1004.20 --> 1009.10]  So you can breathe new life into old dogs with this stuff.
[1009.76 --> 1019.20]  As part of the episode 50 festivities, I wanted to complete a project that I've been kind of working on in the evenings, off and on over the last six months or so,
[1019.26 --> 1022.74]  which was a searchable archive of our show notes.
[1022.74 --> 1048.54]  And huge thanks goes out to the orange one from Discord, who rewrote, I think, something like all but three lines of my code to scrape the fireside website and ingest the HTML and the XML feeds and spit out what eventually turns out to be an MKDocs-based searchable archive of the entire Jupyter broadcasting suite of shows.
[1048.54 --> 1053.48]  That's so great. And, you know, I feel like he kept those three lines of code in there just to be nice to you.
[1053.68 --> 1061.60]  But it's so quick and snappy, and it makes it really quick to find stuff that eventually this is going to get integrated into the site itself.
[1061.74 --> 1068.02]  But for right now, it's just a great way to, like, I know we talked about something. When did we talk about it? Like, it's good for that kind of stuff.
[1068.02 --> 1072.26]  I can't tell you how many times a week I get pinged with, when did you talk about X?
[1072.26 --> 1079.04]  Or when did you, you know, great example is the lineage flashing of the seven-inch fire tablet.
[1079.32 --> 1086.86]  As we were talking just then, I just typed into the search bar, lineage OS, and boom, up came episode 44 of Self Hosted.
[1087.76 --> 1090.20]  There we go. Job done. So it's already working for me.
[1090.20 --> 1094.62]  Now, you can find this thing at notes.jupiterbroadcasting.com.
[1094.90 --> 1103.70]  We've got Coda Radio, Jupyter Extras, Linux Action News, Linux Unplugged, and, of course, this here self-hosted podcast.
[1104.48 --> 1108.58]  All right. Well, this is the self-hosted show, so you've got to tell us a little bit about how you set it up and what's running.
[1109.06 --> 1113.96]  Well, one of the coolest things that Orange managed to do was dynamic theming between a different show.
[1114.06 --> 1118.24]  So I don't know if you're on the site right now, but if you click between the different shows,
[1118.24 --> 1122.66]  you'll notice the top header changes, so self-hosted is Orange, Coda Radio.
[1123.16 --> 1125.16]  I do like that. Yeah, that's so cool.
[1125.42 --> 1126.72]  Linux Action News is Red.
[1128.52 --> 1134.34]  It's all backed by MKDocs, and he's done a bit of dynamic CSS switching between the different tabs, which is pretty cool.
[1134.98 --> 1140.34]  But what we're doing is we scrape all of the show information that's on Fireside,
[1140.40 --> 1146.16]  and we use Fireside as our podcasting publishing platform, and we use that as a source of truth.
[1146.16 --> 1156.58]  And this Python script then takes that scraped data, uses what's called a Ginger2 template to substitute things like the tags in there,
[1156.66 --> 1163.92]  the hosts, any of the links that we put in the episodes, that kind of thing, and it spits out a plain markdown file.
[1164.98 --> 1171.20]  MKDocs then ingests that plain markdown file, and bada-bing, bada-boom, we have an MKDocs site.
[1171.44 --> 1172.08]  Very nice.
[1172.08 --> 1177.54]  But we are relying on a small element of non-self-hosted software.
[1177.70 --> 1183.52]  We're using GitHub Actions, and we're running it through a con job, so at 5 or 6 a.m. every day,
[1183.64 --> 1185.56]  it just goes and scrapes the JB site.
[1185.74 --> 1189.38]  So you'll see that these show notes are getting automatically updated.
[1189.58 --> 1194.06]  This website gets automatically updated every day, so it's never out of date.
[1194.06 --> 1198.16]  Linode.com slash SSH.
[1198.24 --> 1202.42]  Go there to get $100 in 60-day credit towards a new account, and you go there to support the show.
[1202.50 --> 1205.46]  So that's Linode.com slash SSH.
[1205.82 --> 1209.92]  And yeah, of course, notes.jupiterbroadcasting.com is running on Linode.
[1210.04 --> 1214.30]  Everything we build that we want the audience to be able to use, we host that on Linode,
[1214.38 --> 1216.42]  because their infrastructure is killer.
[1216.96 --> 1218.42]  And the price is great, too.
[1218.42 --> 1227.20]  In fact, Linode is 30% to 50% less than the other big hyperscalers out there, and they've been around since 2003 doing this.
[1227.32 --> 1236.34]  So for 18 years, they have remained focused on building out the greatest cloud that you could possibly ever want as a Linux geek.
[1236.42 --> 1238.00]  I mean, it's like a playground.
[1238.42 --> 1242.88]  I go up there, and sometimes when I just want to try out a couple of different projects for talking about on the show,
[1242.98 --> 1246.70]  like, how do you know if something is worth proceeding with?
[1246.70 --> 1249.54]  Like, this is true for you when you're building out something like you have a project.
[1249.62 --> 1251.72]  Like, how do you know if this is the stack you want to use?
[1252.92 --> 1257.70]  Well, I deploy it on Linode, often with some of their one-click deployments, and I'll test it out,
[1257.82 --> 1260.44]  and I'll run it for a couple of days and see how it works.
[1260.68 --> 1266.30]  And often, I keep one out of two or three things, and that eventually turns into a show.
[1266.38 --> 1268.78]  And then we create a project around it, and we end up putting it in production.
[1269.04 --> 1272.22]  And the entire time, from beginning to end, we're doing it all with Linode,
[1272.22 --> 1277.40]  because they just make it simple, it's affordable, and it's easy to work with the team, too.
[1277.60 --> 1282.84]  And then on top of that, they have a really handy API that you can either use directly yourself,
[1282.92 --> 1288.20]  chromatically, or do like I do and just kind of take the lazy route and use their command line client.
[1288.80 --> 1293.06]  So I'll do this to, like, pop a file up on their S3-compatible object storage,
[1293.36 --> 1297.40]  and I can mark it public and generate the URL in, like, three or four seconds.
[1297.40 --> 1300.64]  And this is awesome when we're trying to get clips ready for a show or something like that,
[1300.68 --> 1305.82]  or we're collaborating on a project, or recently I sent a big batch of files to somebody,
[1305.86 --> 1309.00]  and we were going back and forth, like, how are we going to even share this file?
[1309.42 --> 1312.02]  I'm like, oh, hold on a second here, I'll get you a little zip file with a URL.
[1312.36 --> 1316.32]  I did that with a video of my daughter the other day that was, like, 170 meg to a parent,
[1316.48 --> 1317.90]  and Telegram was like, nope.
[1318.54 --> 1320.74]  So I just used the object storage, and it worked great.
[1321.24 --> 1325.06]  Yeah, and the command line client is, like, the pro way to get things up there,
[1325.06 --> 1330.12]  because what I do, because I'm such a nerd, is I have a Uake dropdown terminal
[1330.12 --> 1335.24]  where it's always, like, in one of the tabs, so it's, like, up, up, change a couple of things, hit enter.
[1335.60 --> 1336.48]  It's great.
[1336.86 --> 1340.76]  But on top of that, they've got cloud firewalls, they've got VLAN support,
[1340.82 --> 1345.24]  they have a really powerful DNS manager, they're beginning to roll out bare metal servers,
[1345.50 --> 1347.52]  and they also work with infrastructure management.
[1347.68 --> 1349.78]  So if you want to plug in with Kubernetes and Terraform,
[1349.88 --> 1353.48]  maybe you want to even just use Linode as part of a multi-cloud strategy.
[1353.48 --> 1354.78]  They're great for that, too.
[1354.84 --> 1360.12]  In fact, 66% of companies will save money working with a mix of alternative cloud providers
[1360.12 --> 1362.78]  instead of just relying on, like, one big hyperscaler.
[1362.86 --> 1364.58]  So it's worth just looking into that.
[1365.08 --> 1366.96]  Linode could be part of your multi-cloud strategy.
[1367.30 --> 1370.02]  And if you ever run into any trouble, you ever need any help,
[1370.08 --> 1372.44]  they've got the best customer service in the business.
[1373.14 --> 1376.72]  And when your business is running on Linode, it's nice to know that's available.
[1377.22 --> 1379.16]  And their support for the community runs deep.
[1379.28 --> 1382.56]  They're making it possible for our team to get together in Denver.
[1382.56 --> 1384.48]  They're making the whole road trip possible.
[1385.28 --> 1385.98]  And that's pretty awesome.
[1386.06 --> 1389.66]  And not only that, but they're going to be bringing swag and giveaways like raspberry pies
[1389.66 --> 1392.88]  and all kinds of awesome shirts they've made just for the trip.
[1393.00 --> 1396.20]  And it's just going to be a whole party made possible by Linode.
[1396.26 --> 1399.12]  And they're doing that just to have a chance to connect because, like us,
[1399.50 --> 1400.44]  they miss seeing people.
[1400.58 --> 1401.26]  It's been a while.
[1401.68 --> 1404.68]  And Linode has been so enthusiastic about supporting our reunion.
[1405.78 --> 1407.30]  But there's so many things I could go on about.
[1407.34 --> 1408.84]  You just got to go check it out for yourself.
[1408.96 --> 1411.00]  You got to get your hands on it and see it.
[1411.00 --> 1412.38]  So go use that $100.
[1413.30 --> 1414.40]  Maybe learn something.
[1415.62 --> 1416.70]  And support the show.
[1417.50 --> 1419.70]  Linode.com slash SSH.
[1419.70 --> 1428.50]  Now, I came across a thread on Reddit a couple of weeks ago that Shaw, who's an ISP in Canada,
[1428.76 --> 1435.12]  was blocking Plex because it thought it was suspicious, which tingled my spidey sense a little bit.
[1435.62 --> 1440.04]  Because I often tell people that I share my Plex server with that the ISPs don't care.
[1440.16 --> 1442.02]  It's all just encrypted traffic.
[1442.18 --> 1444.46]  They have no idea what is going on, right?
[1444.46 --> 1446.42]  And so I dug into it a little bit.
[1446.48 --> 1451.30]  And one of the comments has some really interesting information about how the Plex web app works,
[1451.36 --> 1453.68]  which I thought might be interesting to share with you all.
[1454.62 --> 1461.36]  Now, Shaw Protected Browsing uses a service called Zvelo, which happens to flag app.plex.tv.
[1461.36 --> 1469.06]  And the way that the Plex app works in your web browser is it downloads the code to the browser and then runs it locally.
[1469.36 --> 1477.40]  So if you can't access or the web URL is blocked by an ad blocker or some kind of safe browsing plugin,
[1478.48 --> 1481.18]  it just can't download the code and you can't run it.
[1482.04 --> 1489.80]  And because of this, you know, it could affect things running, you know, a web app on a TV, for example, might suffer the same fate.
[1489.80 --> 1495.38]  And I just thought it was really interesting that these apps aren't local.
[1495.66 --> 1501.44]  They're not locally rendered, which is why when Plex update their UI, you don't have to download anything.
[1501.68 --> 1503.46]  It just automatically happens.
[1504.90 --> 1509.22]  Plex clients for Android, Android TV, iOS, tvOS, etc.
[1510.12 --> 1512.84]  aren't affected because they are full versions of the app.
[1512.84 --> 1524.06]  So if you have a smart TV or a hosted Plex web app.plex.tv, you're probably going to want to find a way to route it around something like Zvelo,
[1524.18 --> 1527.52]  which is what Shaw uses to avoid this issue.
[1528.24 --> 1530.20]  It's hard to not be skeptical.
[1530.64 --> 1531.60]  Safe browsing.
[1531.78 --> 1535.00]  This just sounds like they're trying to reduce load on their network, doesn't it?
[1535.02 --> 1538.10]  Or perhaps encourage people to sign up for streaming packages.
[1538.10 --> 1551.38]  I absolutely find it abhorrent that Verizon or AT&T, they all do it here, have different quality profiles of Netflix videos or YouTube videos.
[1551.52 --> 1557.26]  And they lock you into certain quality profiles unless you pay them more money.
[1557.26 --> 1563.52]  This is one of the reasons I decided to set up my PepWave with their Fusion Hub VPN solution,
[1563.72 --> 1570.82]  because it routes my traffic through a VPN and they can't tell what it is, and so they don't re-encode the video for me.
[1571.28 --> 1575.46]  Actually, what AT&T does, each provider does a little bit differently.
[1576.10 --> 1580.04]  And AT&T is particularly frustrating because they just sort of brute force it.
[1580.04 --> 1586.98]  So that way, the YouTube client and the Netflix client, they just sit there and bang their head against the video streaming service,
[1587.06 --> 1590.24]  asking for the best quality, and it keeps failing and failing and failing.
[1590.56 --> 1596.78]  And then when the client finally says, okay, fine, I'll go down to the next lower quality, it tries that, that fails.
[1596.86 --> 1599.84]  And then when it finally goes down to 480p, then it plays.
[1599.94 --> 1604.74]  So you just sit there waiting while your carrier is blocking these connections.
[1604.74 --> 1607.96]  You wait with your little spinner on the screen.
[1608.14 --> 1609.10]  It's so frustrating.
[1609.34 --> 1613.88]  And to see Shaw do this for Plex, it really, it stinks.
[1614.24 --> 1614.98]  It stinks.
[1615.10 --> 1618.96]  Because the reality is they know what's going on over that Plex port.
[1619.06 --> 1622.70]  They know it's not some sort of attack or some sort of weird malware.
[1622.90 --> 1624.26]  They know it's video streaming.
[1625.10 --> 1629.82]  And my reading of the law is the copyright violation really happens when you download the file.
[1629.82 --> 1636.32]  I think, I don't know, I could be wrong if anybody wants to let me know in a clear, explain it to me like I'm a five-year-old way,
[1636.64 --> 1637.92]  cell phone.show slash contact.
[1638.04 --> 1641.40]  But my understanding is you're not actually violating copyright if you stream it.
[1642.10 --> 1643.10]  That can't be right.
[1643.44 --> 1647.50]  But either way, I don't know how Plex scoots around that particular issue.
[1647.90 --> 1652.20]  But regardless, it's not Shaw's place to enforce copyright law.
[1652.36 --> 1654.44]  It's just not, or IP law.
[1654.54 --> 1656.72]  It's just, they should just be passing the bits.
[1656.72 --> 1661.38]  Yeah, I don't expect my water company to choose which bits of water I get.
[1663.00 --> 1665.56]  Yeah, although you do want them to keep the bad stuff out of the water.
[1665.74 --> 1667.34]  So that might be a bad analogy.
[1668.74 --> 1673.48]  I know, Alex, you are, you are very organized compared to me in your Plex collection.
[1673.48 --> 1675.98]  Like you have collections for everything.
[1675.98 --> 1678.42]  You've got nice, consistent album art.
[1678.58 --> 1684.42]  Like at some point in time, you must have just sat back, had a drink and spent like hours organizing all of your metadata.
[1684.76 --> 1685.70]  Well, I am now.
[1685.70 --> 1689.90]  This week I've found possibly my new favorite Plex pick of the year.
[1690.50 --> 1691.82]  Plex Meta Manager.
[1692.18 --> 1695.26]  This is a Python script and it is awesome.
[1695.80 --> 1700.86]  So this thing will go through using the Plex API of your local Plex server.
[1700.86 --> 1707.98]  It uses the token that you can generate by going to Vue XML and get the little token from up the address bar.
[1707.98 --> 1718.52]  And what it will do is it will basically match the TMDB ID of the movie against a list of different collections.
[1718.52 --> 1725.52]  So it's built me in my Plex library, for example, a bunch of different collections based on genres.
[1725.52 --> 1729.86]  Okay, yes, I already had genre filtering, but this is using Plex's smart search.
[1730.30 --> 1731.30]  It's just really cool.
[1731.34 --> 1732.20]  You've got to go check it out.
[1732.20 --> 1739.60]  I've got now a 90s, a noughties, a tensies, a twenties collection in my Plex library as well.
[1740.36 --> 1742.62]  It's just really, really cool.
[1742.62 --> 1746.96]  But what got me looking at this in the first place was my wife and I were browsing through.
[1747.04 --> 1751.30]  I've got a thousand movies or so on my server and we were just browsing through the other night saying,
[1751.40 --> 1752.04]  what should we watch?
[1752.12 --> 1758.16]  And neither of us could come to any kind of agreement about what we should watch.
[1758.54 --> 1759.62]  I know, it's so true.
[1759.86 --> 1764.88]  Well, first of all, why don't I have a bunch of collections of stuff that's, you know, recently added?
[1764.88 --> 1775.10]  And it's one thing that Plex does out the box, but there's no real kind of, you know, trending kind of collection like there is through the Plex Meta Manager,
[1775.82 --> 1778.00]  like a Netflix or Amazon Prime would give me.
[1778.20 --> 1783.16]  And with this, I'm able to sort of say, oh, hey, yeah, that new Wonder Woman movie.
[1783.32 --> 1783.88]  Okay, cool.
[1783.94 --> 1785.14]  I could go and watch that tonight.
[1785.88 --> 1787.84]  So that was really the motivation behind it.
[1787.88 --> 1790.76]  But this script takes a little bit of elbow grease to get set up.
[1790.76 --> 1794.78]  The documentation is very good, but it's also very verbose.
[1795.16 --> 1798.16]  So it almost put me off, but I'm very glad it didn't.
[1798.74 --> 1805.82]  You need to configure a couple of YAML files and then they actually provide a Docker container that you can run the Python script out of,
[1806.00 --> 1808.04]  which just floats my boat.
[1808.66 --> 1811.56]  I have it set to run every day through a systemd timer.
[1812.38 --> 1820.18]  And the main reason that actually we wanted to go into refreshing all the metadata every day was because of the critic ratings that Plex has.
[1820.18 --> 1833.90]  I noticed that several of the movies that I had, the critics rating and the Ross and Tomatoes rating didn't really seem to line up with what I thought the movie was, like not even a little bit.
[1833.96 --> 1838.38]  And it turns out that it was just a few thousand votes on those really early scores.
[1838.38 --> 1843.42]  And so the Plex Meta Manager goes through every day and refreshes things like critic ratings.
[1843.64 --> 1845.36]  It has a cache, which you can configure.
[1845.52 --> 1847.22]  And I think I've got mine set to 30 days.
[1847.56 --> 1851.76]  So it's not going to go and scrape every movie every day.
[1852.06 --> 1855.90]  But, you know, once a month, I think updating my critic ratings is probably worthwhile.
[1855.90 --> 1866.06]  So this Python script, you set it up to run through systemd every night, and then it goes out and gets all the updated information, and then it writes it to the Plex database directly?
[1866.66 --> 1866.92]  Yeah.
[1867.08 --> 1870.68]  So if you're running Plex in a container, are you running this script in that container?
[1870.82 --> 1871.82]  How's that working?
[1872.20 --> 1873.94]  You supply the Plex server URL.
[1874.22 --> 1879.30]  So in my case, it was just 192.168.port32400.
[1879.44 --> 1880.56]  So it's talking Plex.
[1880.64 --> 1882.12]  It's not like crawling the file system.
[1882.42 --> 1882.64]  No.
[1883.02 --> 1883.34]  Gotcha.
[1883.52 --> 1885.46]  And then how does it get access to the database, though?
[1885.46 --> 1886.24]  Through a token.
[1886.54 --> 1890.68]  So when you go into your media library, there is a Plex token that you can get.
[1890.78 --> 1894.20]  You can click on, I think it's Get Info, and then View Raw XML.
[1895.02 --> 1901.50]  And as part of that XML payload, up in the address bar, there is a 20-character long token.
[1902.06 --> 1907.68]  You give this script that token, and then it authenticates against the Plex API, and off it goes.
[1908.20 --> 1910.52]  That is so cool, Alex.
[1910.52 --> 1915.42]  Man, I love the idea of going out and getting the updated ratings, because I have observed that same exact.
[1915.46 --> 1920.66]  And I'm really glad you dug into it, because I had wondered, how exactly does that work?
[1921.14 --> 1924.36]  That is so cool that it goes out there and gets the trending stuff, too.
[1924.70 --> 1929.66]  I noticed, too, that you came across Movie Match, which is what I actually thought was going to do some of this.
[1930.12 --> 1932.02]  Yeah, it's like Tinder, this thing.
[1932.14 --> 1934.68]  Not that I've ever used Tinder, because I've been married for 10 years.
[1934.92 --> 1936.12]  Now you're more of a grinder guy.
[1940.36 --> 1941.12]  Oh, man.
[1942.42 --> 1942.78]  No.
[1944.26 --> 1944.90]  I'm not.
[1945.48 --> 1945.92]  Oh, okay.
[1945.92 --> 1946.00]  Yeah.
[1946.36 --> 1952.14]  But it is like, it's actually more of like, it's more of matching taste up with a group, right?
[1952.18 --> 1954.62]  It's more about like, hey, what do we all want to watch together?
[1955.28 --> 1960.82]  And when, again, going back to that problem, when you've got like a thousand movies in your library, it's harder.
[1960.82 --> 1973.98]  If a group of us were here in the studio, legitimately, if we were all just hanging out, you, me, and everybody were hanging out on the couch, and we were just flipping through live TV, and like Star Wars was like on one of the cable channels, we would just watch it.
[1974.34 --> 1975.68]  There wouldn't even really be a debate.
[1975.80 --> 1976.76]  That's what we would put on.
[1977.26 --> 1983.96]  But when you actually have to choose, and you want a group of people to decide, it's a real first world problem.
[1984.36 --> 1985.48]  Mesa likes Star Wars.
[1985.68 --> 1986.54]  Oh, no.
[1986.78 --> 1987.58]  Those ones even?
[1987.58 --> 1990.18]  Yeah, I was a kid when that came out.
[1990.28 --> 1995.42]  Episode one, I was like nine or ten when that came out.
[1995.86 --> 2002.76]  And I remember we were on, this is one for the British audience, we were on a Norfolk Broads holiday, and we were in Lowest Off that night.
[2002.92 --> 2009.18]  And I remember walking down the road with my dad to go to the cinema from the boat to go and watch episode one.
[2009.44 --> 2011.22]  And it's just one of those things that stuck in my memory.
[2011.42 --> 2012.08]  Ah, that's great.
[2012.28 --> 2013.60]  How can you not love pod racing?
[2013.70 --> 2014.84]  It's just the coolest thing ever.
[2015.12 --> 2015.86]  Yeah, that's true.
[2015.86 --> 2017.66]  The pod racing was super awesome.
[2018.20 --> 2020.10]  Yeah, I mean, I enjoy the Star Wars movies.
[2020.24 --> 2021.86]  The prequels, not as much.
[2022.02 --> 2023.20]  I think the writing's horrible.
[2023.56 --> 2024.92]  But I'm more of a Star Trek guy.
[2025.20 --> 2028.18]  I've kind of lost track of what's going on these days.
[2028.78 --> 2037.80]  So speaking of this movie match thing, essentially what you do is you and your partner or your group of friends set up this app to talk to your Plex library.
[2037.80 --> 2043.66]  And it presents you with a random bunch of movies that you swipe right, swipe left if you like it or don't like it.
[2043.66 --> 2049.08]  And if you and your group end up with a common set of movies, it will show you at the bottom.
[2049.18 --> 2052.96]  Here are the three movies that you all thought were worth watching.
[2053.34 --> 2055.64]  So it just narrows things down for you.
[2055.98 --> 2058.90]  You could set up like a group chat, like movie night group chat.
[2058.90 --> 2065.46]  And you drop that link in there a couple of nights before and have everybody go through and swipe right and left.
[2065.78 --> 2069.70]  And then when it comes time, use the new Plex watch feature and just watch it all together.
[2070.12 --> 2071.28]  Socially distanced movie night.
[2071.52 --> 2072.70]  Hey, it could be a thing again.
[2072.70 --> 2075.66]  And now we have the tools we need.
[2076.08 --> 2076.92]  This is really cool.
[2077.04 --> 2080.50]  So we'll have a link in the show notes or you could just Google search for movie match.
[2080.54 --> 2084.06]  It's just one word, but links will be at self-hosted.show slash 50.
[2084.74 --> 2088.70]  Now, my final Plex pick for this week is a no spoilers script.
[2088.70 --> 2094.72]  Have you ever been watching a TV show and seen an episode, three or four episodes ahead in Plex,
[2094.94 --> 2101.72]  and you see a character whose current storyline doesn't fit with that thumbnail?
[2102.18 --> 2102.46]  Yes.
[2102.70 --> 2106.58]  Well, this script will blur out the future episodes you haven't yet watched.
[2106.98 --> 2107.56]  That's great.
[2107.78 --> 2112.14]  So it must be going through finding that JPEG and actually like applying a blur to it.
[2112.76 --> 2113.58]  That's funny.
[2113.92 --> 2114.88]  That's really funny.
[2115.26 --> 2118.84]  It will blur out the episodes based on the user who sets it up.
[2119.02 --> 2123.22]  So, for example, my server, let's say Catherine had her own account, my wife.
[2123.68 --> 2127.58]  All the episodes I hadn't watched would be blurred even if she'd watched them.
[2127.80 --> 2130.16]  So it's not perfect, but it's better than nothing.
[2130.60 --> 2132.42]  Mark my words, Plex will...
[2132.70 --> 2134.38]  Introduce this feature to the Plex client.
[2135.06 --> 2137.02]  My prediction right here on self-hosted 50.
[2137.02 --> 2143.56]  Because Infuse, what I've been raving about recently, which is also a Plex compatible client, does this.
[2143.60 --> 2144.66]  It's an option in the settings.
[2145.30 --> 2146.44]  And it's a game changer.
[2146.50 --> 2148.54]  It's what actually switched it over using Infuse.
[2148.60 --> 2150.44]  And now I've just stuck for all of the other reasons.
[2150.44 --> 2154.04]  But it pre-blurs the image and the description.
[2154.80 --> 2157.20]  Once you've watched it, it unblurs all that stuff.
[2157.90 --> 2160.14]  And it just goes based on the watch status.
[2160.14 --> 2161.76]  And there's just one user with Infuse.
[2162.12 --> 2169.02]  But if you are on an Apple TV platform and you want to use Infuse to watch Plex and would like to do that, it's just in the settings.
[2169.24 --> 2171.16]  And we love this feature.
[2171.16 --> 2175.84]  So I've got to imagine this is something Plex is going to implement, too, just because it's so freaking handy.
[2176.40 --> 2179.12]  Yeah, I'm still butthurt about this NVIDIA Shield update.
[2179.68 --> 2181.10]  I thought I'd get used to it.
[2181.14 --> 2182.72]  And I thought I wouldn't care too much.
[2182.80 --> 2186.64]  But I tell you what, my Shield downstairs doesn't have the update.
[2186.72 --> 2187.86]  But the one upstairs does.
[2188.20 --> 2190.74]  And the one upstairs is really beginning to grate on me.
[2190.84 --> 2193.56]  So I might have to get an Apple TV soon.
[2193.56 --> 2198.76]  I want to take a moment and thank our friends over to Cloud Guru for their support.
[2198.96 --> 2201.74]  And I want to mention to you they have a Linux file sharing course.
[2201.90 --> 2204.20]  It's a deep dive on Linux file sharing.
[2204.54 --> 2212.08]  It's a standalone course, but it's also part of a learning path intended to prepare you for the LPIC 2 Engineer 202 and 450 exam.
[2212.56 --> 2216.78]  In this course, they're going to cover the basics and advanced configurations for Samba and NFS,
[2217.24 --> 2223.40]  including configuring file servers, exporting file shares, user authentication, client configuration, and mount options.
[2223.80 --> 2225.52]  We'll have a link for that in the show notes.
[2225.84 --> 2227.36]  Or you can go to cloudguru.com.
[2228.06 --> 2231.06]  And also, we have cloudfree.shop sponsoring this week's episode.
[2231.56 --> 2235.08]  You can go to cloudfree.shop to get a pre-flashed TASMOTOR smart plug.
[2235.46 --> 2238.76]  Use the coupon code self-hosted to get a dollar off per smart plug.
[2239.26 --> 2242.70]  And of note, the new version 2 smart plug has been released recently.
[2243.44 --> 2245.82]  And this one's really cool because it features energy monitoring.
[2245.82 --> 2250.22]  So not only do you have a free and open source firmware on this thing from the factory,
[2250.22 --> 2257.12]  but I can now also monitor how much power my server is using without needing to tie up my kilowatt, for example.
[2257.64 --> 2258.10]  Super cool.
[2258.48 --> 2261.74]  So go to cloudfree.shop and use the coupon code self-hosted.
[2261.74 --> 2264.84]  Greg writes into the show,
[2264.92 --> 2266.62]  Chris and the Badger, love the show.
[2266.68 --> 2271.62]  It inspired me to learn Docker this past April and convert all of my self-hosted services to Docker.
[2271.62 --> 2275.90]  I built one big Docker Compose that provides the MariahDB for various components,
[2276.06 --> 2280.36]  plus the Swag and SSL for all my external services.
[2280.80 --> 2286.04]  And I've moved over to AirSonic Advanced and BookSonic and Ghost as well.
[2286.04 --> 2287.66]  All tips from the show.
[2287.74 --> 2288.98]  But here's my question.
[2290.10 --> 2292.90]  How do I manage updates for the various service images?
[2293.52 --> 2296.54]  Most of the Compose entries are built with the latest tag.
[2297.06 --> 2301.94]  Should I move to a specific version and definition and then rebuild it on a regular basis?
[2303.06 --> 2305.28]  And for in-container security updates,
[2305.68 --> 2308.58]  how often should I repull the images to keep them up to date?
[2309.14 --> 2311.88]  Perhaps there is a guide or a white paper on different approaches.
[2312.60 --> 2314.22]  I think Greg just needs some help, Alex.
[2314.22 --> 2318.42]  Well, my advice would be straight off the bat,
[2319.34 --> 2323.34]  don't run latest because it's just a disaster waiting to happen.
[2323.48 --> 2327.98]  As I found out with my next cloud this week, which broke again.
[2328.18 --> 2329.14]  No, no, no way.
[2329.26 --> 2331.66]  Even though I talk about it in the last episode,
[2331.76 --> 2335.18]  and I've pinned it to a specific version, you know, a major version.
[2335.36 --> 2338.86]  So 19, 20, 21, something like that.
[2338.98 --> 2340.80]  But within those certain tags,
[2340.88 --> 2343.10]  sometimes you've got to watch the developers as well even.
[2343.10 --> 2346.94]  Because they all just released all the security patches and all the updates
[2346.94 --> 2350.06]  for the entire lifecycle of that major version.
[2350.96 --> 2354.72]  So you will get a lot of updates even sometimes when you pin specific versions.
[2354.96 --> 2359.96]  So the only way to be sure is to go to the Docker Hub page for a specific image
[2359.96 --> 2362.20]  and look at the list of tags that are available.
[2362.20 --> 2369.26]  And some providers, some developers offer specific tags to the exact specific version,
[2369.40 --> 2371.06]  which ties to a specific commit.
[2371.66 --> 2376.16]  Others, like Nextcloud, offer a stable version of a major version.
[2376.84 --> 2379.32]  Lots of different ways to do this particular thing.
[2379.62 --> 2384.52]  But for apps that don't matter, maybe you'll get away with latest.
[2384.76 --> 2387.20]  You know, things like traffic, for example, is probably a good idea
[2387.20 --> 2390.40]  to run that on latest because that's public facing.
[2390.80 --> 2394.38]  So you want the latest, you know, CVEs and things patched in that one.
[2395.26 --> 2398.58]  But for the rest of them, I would probably steer away from latest
[2398.58 --> 2402.10]  just because at some point or other, it will bite you.
[2402.66 --> 2407.66]  Bevan writes in, and he is looking for a security camera system for a vacation house.
[2407.72 --> 2410.28]  So I think one that he probably isn't intending to be at very often.
[2410.28 --> 2416.14]  He writes, most of the options seem to need a cloud component in order to operate,
[2416.68 --> 2420.00]  which is a bit concerning since the systems are not cheap to install.
[2420.42 --> 2425.24]  I'd be interested to know what you guys use and maybe what other listeners might have installed.
[2425.48 --> 2425.72]  Cheers.
[2425.98 --> 2426.58]  Love the show.
[2427.00 --> 2430.16]  Well, let me just fire up notes.jupiterbroadcasting.com
[2430.16 --> 2434.64]  and type in blue iris because that's going to be my recommendation.
[2434.92 --> 2437.34]  We've got a couple of episodes where we've talked about it in the past.
[2437.34 --> 2441.46]  Episode 43, episode 28, 36.
[2442.42 --> 2443.94]  Now, we've talked about it quite a few times.
[2444.64 --> 2449.64]  The too long didn't listen, though, is Blue Iris is a Windows app.
[2449.82 --> 2454.46]  So you're going to want to have some kind of a system that has a quick sync enabled CPU.
[2455.12 --> 2460.74]  So something like the HP 290 Slim box, which you can pick up off eBay for about $130
[2460.74 --> 2462.84]  at the time of recording.
[2463.20 --> 2467.04]  That has an 8th gen Intel CPU in it, which has quick sync.
[2467.34 --> 2468.98]  You install Windows on there.
[2469.30 --> 2469.94]  Yes, I know.
[2470.06 --> 2470.68]  Sorry, Windows.
[2471.32 --> 2473.24]  And then Blue Iris on top of that.
[2473.82 --> 2480.30]  And then what you will need to power the hardware is a PoE switch connected to PoE cameras.
[2480.64 --> 2485.96]  And you can usually get those for anywhere from $10 or $20 from Alibaba
[2485.96 --> 2491.02]  all the way up to $300, $400 each if you want to buy a Unify gear.
[2491.02 --> 2496.22]  What I tend to stick with is the price point of around $50 a camera unless I absolutely
[2496.22 --> 2497.22]  need 4K.
[2497.80 --> 2499.62]  And then it's about $100 a camera.
[2500.30 --> 2502.14]  But it's not terribly expected.
[2502.22 --> 2503.90]  The cameras are the cheap part, essentially.
[2504.54 --> 2509.28]  Running Ethernet is going to be something of a consideration because that's how the cameras
[2509.28 --> 2510.00]  get their power.
[2510.86 --> 2515.76]  And then also you might want to upgrade a couple of things in the HP box I recommended.
[2515.76 --> 2520.06]  It comes, I think, the one on eBay with a 500 gig spinning drive, for example.
[2520.56 --> 2522.22]  So you might want an SSD for that as well.
[2522.98 --> 2524.62]  But that's a pretty solid setup.
[2524.72 --> 2527.20]  And there are lots of guides on YouTube on how to set up Blue Iris.
[2528.00 --> 2532.88]  And recently, they've got some really cool features in there with deep stack to do object
[2532.88 --> 2534.36]  detection and that kind of stuff.
[2534.52 --> 2536.42]  So Blue Iris gets my vote.
[2536.96 --> 2537.02]  Right.
[2537.08 --> 2540.78]  And those cameras going over Ethernet are going to be a rock solid setup.
[2540.78 --> 2548.02]  And I think that's really key is a lot of the cloud solutions are all Wi-Fi cameras.
[2548.26 --> 2550.64]  And Wi-Fi cameras are going to work 90% of the time.
[2551.48 --> 2554.98]  But wired cameras are going to work 100% until there's like a hardware failure.
[2555.24 --> 2559.78]  Now with Blue Iris, Alex, because I'm unfamiliar with it, is there a remote viewing component so
[2559.78 --> 2561.30]  we could pull it up on a mobile device?
[2561.80 --> 2562.50]  It's so cool.
[2562.98 --> 2569.98]  There's an app for all the major mobile platforms as well as a web browser, like a web interface.
[2569.98 --> 2575.92]  So I can just type the URL of my server, which happens to go through my traffic reverse
[2575.92 --> 2576.28]  proxy.
[2577.18 --> 2580.98]  And straight away, I'm thrown into a web interface that is HTML5.
[2581.34 --> 2584.24]  And I can see all six of my cameras, boom, right there.
[2584.34 --> 2591.58]  So if I hear a noise or the doorbell goes or something like that, I just type in bi.mydomain.com
[2591.58 --> 2593.90]  and boom, straight in a browser.
[2594.12 --> 2594.70]  I'm good to go.
[2595.12 --> 2598.78]  And that's another thing about the local wired systems is those camera feeds are going to
[2598.78 --> 2599.58]  come up a lot quicker.
[2599.58 --> 2602.58]  The cloud-based systems are going to have to connect to the service first.
[2602.88 --> 2606.62]  There's usually somewhere like on a good day, a three-second delay.
[2606.74 --> 2608.22]  Sometimes it can be a 30-second delay.
[2608.68 --> 2609.60]  I don't like it.
[2609.94 --> 2613.60]  Now, I normally would sit here and I'd tell you about my Wyze system.
[2613.92 --> 2617.88]  I have the WYZE cams that are going into a Shinobi box.
[2617.88 --> 2623.30]  But I don't love the solution because the cameras are not super reliable.
[2623.30 --> 2627.84]  And so I would not recommend them for a security system like what you have here.
[2627.98 --> 2632.90]  I have it for we're off grid somewhere and we come back and somebody's broken into our
[2632.90 --> 2633.20]  rig.
[2633.20 --> 2635.58]  I want to have a good shot that I've caught something on camera.
[2635.70 --> 2637.30]  That's really what I have my system for.
[2637.62 --> 2642.02]  But I don't know if I would trust it to run 24-7 because they're Wi-Fi cameras.
[2642.32 --> 2645.08]  They're doing it over RTMP or RTSP.
[2645.26 --> 2646.88]  It's just not super reliable.
[2647.50 --> 2650.94]  Now, I've never used the next system I'm about to talk about.
[2650.98 --> 2652.70]  So I would not normally recommend it.
[2652.70 --> 2658.18]  However, I have gotten a couple of emails in people have said that if you want a system
[2658.18 --> 2663.72]  that's kind of like a Midway system, I have heard that the Arlo camera system is good for
[2663.72 --> 2664.50]  that kind of thing.
[2664.72 --> 2668.00]  You can get it like on Amazon and like a three to six camera kit.
[2668.36 --> 2672.24]  And what's kind of different about this is it has a base station unit that the cameras
[2672.24 --> 2674.06]  connect back to locally on your LAN.
[2674.28 --> 2675.84]  And that's where the video is stored.
[2676.50 --> 2679.18]  And so that does seem compelling to me.
[2679.50 --> 2682.14]  And I guess it has a pretty flexible setup system.
[2682.14 --> 2688.34]  And you can get a three camera kit for 385 bucks off of Amazon when it's not on sale.
[2688.96 --> 2693.22]  And I don't know how great it is, but the people who've written into the show seem to
[2693.22 --> 2693.66]  really like it.
[2693.70 --> 2695.64]  The cameras seem to work indoors and outdoors.
[2695.84 --> 2696.66]  Never tested it myself.
[2696.80 --> 2702.68]  But if I had 385 bucks to burn, I may give this a go one day because I do like the idea
[2702.68 --> 2704.74]  of making this as much of an appliance as I can.
[2704.78 --> 2709.04]  And I am not really in a situation to run Ethernet and do PoE.
[2709.04 --> 2712.82]  Now, I do have a couple of those Wyze cameras plugged into Blue Iris as well.
[2713.38 --> 2719.30]  One thing of note, though, is that the new V3 cameras don't support the RTSP firmware yet.
[2719.50 --> 2728.18]  So if you're thinking about getting those cheap $20, $25 Wyze Cam V2 cameras, just be aware
[2728.18 --> 2729.76]  you'll need to put a custom firmware on there.
[2729.98 --> 2730.12]  Yeah.
[2730.12 --> 2731.78]  My advice would be don't do Wyze right now.
[2732.18 --> 2737.10]  The Wyze 2 is just not fast enough to do the feed reliably.
[2737.80 --> 2742.34]  And the V3, while it has a faster processor and better optics, doesn't have the firmware
[2742.34 --> 2743.16]  yet, like you were saying.
[2743.62 --> 2747.82]  And I would hold off on purchasing a Wyze camera system until then, because what I like
[2747.82 --> 2750.82]  to do is bring all those feeds back into Shinobi running on my Raspberry Pi.
[2750.82 --> 2755.34]  But with the V2 Wises, they drop off several times an hour right now.
[2755.56 --> 2756.70]  It's no good.
[2756.94 --> 2757.58]  There's gaps.
[2758.00 --> 2761.60]  And I think the V3s would be a lot better, but you have to wait.
[2761.80 --> 2762.74]  So I'd say, hold up.
[2762.78 --> 2765.04]  When we come back on the show and say we've tested it, go for it.
[2765.04 --> 2768.06]  But in the meantime, if you can, Wired is the way to go.
[2768.50 --> 2771.90]  And don't forget, as we talked about at the top of the show, we have a big Jupiter
[2771.90 --> 2776.66]  broadcasting meetup coming up very, very soon, both Salt Lake City and Denver.
[2776.66 --> 2781.58]  And don't forget to go to jupitergarage.com and grab some self-hosted 50 merch.
[2782.14 --> 2787.50]  For the next couple of weeks, we're running member pricing on the store to celebrate episode
[2787.50 --> 2787.96]  50.
[2788.46 --> 2791.98]  So you got a limited amount of time to get over to jupitergarage.com and pick yourself
[2791.98 --> 2794.46]  up some stickers or shirts or I don't know.
[2794.64 --> 2795.76]  There's all kinds of stuff over there.
[2795.86 --> 2796.36]  I'm not you.
[2796.78 --> 2797.46]  I don't know what you do.
[2798.18 --> 2801.34]  And if you want to support the show, you can get a self-hosted.show slash SRE.
[2801.78 --> 2806.26]  I got a memo the other day that we might be doing a special discount for all original
[2806.26 --> 2806.80]  merch.
[2807.12 --> 2807.64]  That's right.
[2807.74 --> 2809.92]  Crazy self-hosted is giving away prices.
[2810.14 --> 2811.04]  We're dropping prices.
[2811.16 --> 2813.24]  We're slashing prices for members only.
[2813.64 --> 2819.24]  We'll have a discount code that will take a little bit off any original merchandise items.
[2819.30 --> 2822.96]  And when you go to jupitergarage.com, there's a products drop down menu.
[2822.98 --> 2827.10]  And if you choose original merch, members are going to get a percentage off all that.
[2827.18 --> 2829.40]  We'll have details in the members only post show coming up.
[2830.04 --> 2830.40]  Absolutely.
[2830.72 --> 2833.88]  Now, for all the ways to go and get in touch with us, you can go to self-hosted.show
[2833.88 --> 2834.78]  slash contact.
[2835.14 --> 2837.50]  And you can find me on Twitter at Ironic Badger.
[2837.92 --> 2839.24]  I'm there too at Chris LAS.
[2839.50 --> 2843.60]  And this here show for news announcements and whatnots at self-hosted show.
[2843.88 --> 2844.76]  Thanks for listening, everybody.
[2845.02 --> 2846.88]  That was a special episode 50.
[2846.88 --> 2851.18]  You're welcome.
[2851.22 --> 2855.44]  Bye.
[2855.50 --> 2856.66]  Bye.
[2857.74 --> 2858.62]  Bye.
[2863.94 --> 2864.40]  Bye.
[2865.04 --> 2865.48]  Bye.
[2866.28 --> 2866.50]  Bye.
[2866.86 --> 2866.94]  Bye.
[2867.20 --> 2868.04]  Bye.
[2868.04 --> 2868.18]  Bye.
[2868.24 --> 2868.54]  Bye.
[2868.56 --> 2868.78]  Bye.
[2868.88 --> 2868.98]  Bye.
[2869.34 --> 2869.60]  Bye.
[2869.60 --> 2870.50]  Bye.
[2870.66 --> 2871.28]  Bye.
[2871.28 --> 2871.34]  Bye.
[2871.34 --> 2871.58]  Bye.
[2871.60 --> 2871.80]  Bye.
[2871.86 --> 2872.72]  Bye.
[2872.96 --> 2873.14]  Bye.
[2873.14 --> 2873.82]  Bye.
[2874.02 --> 2874.68]  Bye.
[2874.68 --> 2875.06]  Bye.
[2875.14 --> 2876.12]  Bye.
[2876.12 --> 2876.60]  Bye.