[0.00 --> 6.50]  Coming up on the show, we react to Home Assistant password shaming both of us and then attempt to solve an age-old cloud problem.
[7.28 --> 8.50]  Backups. I'm Chris.
[8.94 --> 10.50]  And I'm Alex, and this is Self-Hosted.
[11.72 --> 14.16]  The podcast is a middle-aged man now. We're 40.
[15.08 --> 21.22]  Yeah, the podcast is feeling like he's still got some pet left in him, but also has a few miles on him. Or her.
[21.46 --> 22.74]  Midlife crisis coming up.
[23.26 --> 27.36]  Is the podcast, does it have a gender? It's a thing, right?
[27.36 --> 29.46]  The podcast prefers to be referred to as they.
[30.00 --> 35.02]  Podcast pronouns.
[35.88 --> 37.52]  There's a title right there, I'll tell you what.
[38.08 --> 41.72]  Anyway, you were going to tell me about your off-grid solar stuff. We've not heard about that for a while.
[42.26 --> 47.88]  We were chatting about this just before we hit record because I'm off-grid and podcasting on solar right now.
[48.22 --> 50.64]  I was just talking to you, actually, because you're thinking about getting solar.
[50.64 --> 56.22]  And I think the thing that people have to wrap their head around is, what are you planning for?
[56.28 --> 58.68]  Are you planning for a grid blackout or brownout?
[58.68 --> 61.24]  Are you planning for going out into the woods?
[61.70 --> 62.94]  What's your scenario?
[62.94 --> 68.26]  And then how much battery do you really need versus could you supplement with a generator?
[68.26 --> 77.40]  Like, for me right now, I think I've hit a sweet spot of enough battery capacity that I can run on it for a day or so.
[77.54 --> 82.10]  And if it's a sunny day out, I can get a 30%, 40% charge right now in the winter.
[82.46 --> 85.34]  But I can't get 100% charge off of solar right now.
[85.34 --> 91.44]  And so I need to run the generator for about an hour once a day right now when I'm off-grid.
[92.34 --> 93.48]  And that's fine.
[93.58 --> 98.22]  I feel like that's actually a really good spot because the more battery you have, the more generator or solar you're going to need.
[99.02 --> 100.90]  You can't, you know, you can't charge all.
[100.96 --> 102.94]  You have to have the ability to charge all that stuff up.
[103.08 --> 107.72]  So I feel like I've kind of hit the sweet spot that because it's winter, you know, we're not getting prime sunshine.
[107.72 --> 110.56]  And I'm only running the generator about once a day.
[110.78 --> 112.76]  And otherwise, we're getting along.
[112.90 --> 114.42]  I think I'm kind of in that sweet spot.
[114.50 --> 120.16]  And I think that's something you should think about when you're specking out your solar system for your house is what are you covering for?
[120.24 --> 122.30]  Are you covering for a couple of days of no power?
[122.46 --> 124.64]  Or do you really just need to cover for a couple of hours?
[125.18 --> 128.02]  And if it goes longer, maybe you could run a generator for an hour or two.
[128.48 --> 133.50]  I think I want to cover just the average daily low-level load of the house.
[133.50 --> 134.94]  I want to make the house more sustainable.
[134.94 --> 141.08]  So, you know, like just all the lighting, all the computers that are on in here, whatever that works out to be.
[141.76 --> 146.28]  My electric bill is normally in a sort of $100 to $120-ish range.
[146.36 --> 147.32]  So it's not too crazy.
[148.36 --> 150.78]  And for me, it's about sustainability.
[151.16 --> 155.46]  And I was watching a David Attenborough program, Our Perfect Planet, the other night.
[155.80 --> 158.90]  Beautiful 4K HDR on the LG OLED.
[159.28 --> 161.52]  Oh, it was magical to watch that thing.
[161.82 --> 162.90]  Streaming from the Plex server.
[163.28 --> 163.60]  Correct.
[163.60 --> 165.30]  Yeah, through the Nvidia shield.
[166.06 --> 176.44]  You can't help but watch these perfect planet things and be left with a sense of guilt about what humanity is doing to the planet and how we're consuming too many resources and stuff like that.
[176.58 --> 189.10]  So, you know, I think about how I might be in a position to do something about that as just an individual when in reality we need to, as a species, collectively actually affect change.
[189.10 --> 191.66]  But as an individual, there isn't much I can do.
[191.66 --> 197.14]  But reducing my use of fossil fuels, even by a little bit, feels like a good place to start.
[197.40 --> 202.64]  Yeah, I love the idea of even just offsetting the computers that run all the time.
[202.64 --> 206.26]  So, during the day, I've reached the point where all day long I'm running off the solar power.
[206.38 --> 215.74]  I'm bringing in more solar power than I am using, which is a great spot to be because that means my home server, all my stuff is being sustained by the sun.
[215.74 --> 220.92]  And I'd love to do a similar setup at the studio, a couple of panels on the roof.
[220.98 --> 227.82]  If I could just bring in, you know, 400 watts or so, I could probably cover most of my computer gear that's running 24-7.
[227.82 --> 236.70]  And, you know, I think about long-term, Alex, say even just 10 years, 15 years down the road, maybe the majority of cars or all cars sold will be electric.
[237.28 --> 244.88]  How does the grid in the United States, at least, handle that if we don't have some people offsetting their load with solar?
[245.02 --> 252.94]  It seems like long-term, the direction things are going between crypto mining and electric cars, there's going to be more demand on the grid than ever.
[252.94 --> 260.12]  So, being able to supplement a little bit might not only just be a nice thing to do for the environment, but also ensure that you have enough power to go around.
[260.78 --> 261.50]  Free Bitcoin, baby.
[262.06 --> 262.24]  Yep.
[262.34 --> 263.36]  Get that crypto going.
[263.94 --> 266.10]  And maybe, maybe spend your time learning.
[266.22 --> 268.52]  This episode is brought to you by the all-new A Cloud Guru.
[268.72 --> 272.96]  They are the leader in learning for the cloud, Linux, and other modern tech skills.
[273.14 --> 273.62]  Go check them out.
[273.66 --> 276.24]  They have hundreds of courses and thousands of hands-on labs.
[276.34 --> 276.70]  Get certified.
[276.86 --> 277.26]  Get hired.
[277.68 --> 280.28]  Get learning at acloudguru.com.
[280.28 --> 287.24]  You could spend that time mining crypto, or you could spend that time learning job skills and getting hired.
[287.62 --> 297.32]  But, you know, I think maybe you and I are thinking about off-grid and backup power today because a lot of our listener services are down and offline as we record this right now.
[297.74 --> 298.08]  That's right.
[298.18 --> 298.30]  Yeah.
[298.46 --> 304.60]  OVH, one of the largest VPS providers in Europe, have suffered a major fire this week.
[304.60 --> 316.64]  And it's taken, literally taken out one of their data centers and had dramatic effects on some of their other regions, data centers, whatever they called for OVH as well.
[317.36 --> 319.42]  It's just got me thinking, great.
[319.62 --> 322.16]  There's another disaster that I hadn't really thought about.
[322.24 --> 325.50]  What if AWS or DigitalOcean or Linode, what if they catch fire?
[325.50 --> 327.68]  Oh, that's another one to plan for.
[329.12 --> 335.40]  Yeah, the thing that's tricky about OVH is data centers one through four were all kind of like in the same area.
[335.84 --> 341.86]  So after midnight on the Wednesday of the week we're recording this, OVH cloud had an alarm go off.
[342.24 --> 344.82]  The cause as of this recording right now is still unknown.
[344.82 --> 350.16]  However, the founder and CEO speculated it may have been a UPS fire.
[350.34 --> 358.90]  And he noted in a video update that he released a couple of days ago that UPS number seven had been serviced earlier that day.
[358.98 --> 361.70]  But obviously more investigation is required.
[362.02 --> 366.38]  In total, OVH had four data centers in this area and one data center.
[366.78 --> 370.76]  SBG two was just totally destroyed by fire.
[370.76 --> 375.40]  And then part of SBG one was also damaged.
[375.54 --> 378.22]  And then SBG three and four, they're fine.
[378.40 --> 383.44]  But as we record, there's still some outages because there's some areas the staff can't get to.
[383.52 --> 384.68]  There's network issue.
[384.94 --> 386.64]  There's still some power issues.
[386.64 --> 392.56]  And there's even the fact that they still have to validate that the cooling system is still fully functional.
[392.90 --> 394.56]  It's like bad, Alex.
[394.56 --> 406.88]  This is a weird one to me because every data center that I've worked near or in in some occasions, they've all had argon fire suppressant systems.
[406.88 --> 414.92]  And just fire was something that you kind of assumed would never get out of control in a data center because it's a controlled environment.
[415.42 --> 419.56]  There isn't a huge amount of flammable stuff like on a data center floor.
[419.86 --> 423.44]  It's just metal boxes with some cables and stuff like that, essentially.
[423.44 --> 424.04]  Yeah.
[424.28 --> 426.98]  So it's kind of surprising to me that it was able to get to this level.
[427.10 --> 432.44]  I mean, if you look at some of the pictures and we've got a Reuters article linked in the show notes, that building was toast.
[433.20 --> 433.54]  Yeah.
[433.58 --> 442.84]  The CEO says something about it using older style construction techniques and that the newer buildings that weren't damaged were using the newer style.
[443.04 --> 447.78]  I wonder if that style is fire suppression, you know.
[447.96 --> 448.60]  Yeah, maybe.
[448.92 --> 450.30]  Or materials or something.
[450.30 --> 454.94]  But it kind of got us thinking like, you know, we got kind of a sad note in from listener.
[455.04 --> 458.62]  Kerry said, my server was in data center one and I have lost it.
[458.68 --> 467.80]  I'm afraid I didn't have any complete backups because I didn't really have anywhere to back up to that server already blew my personal self-hosting budget.
[468.46 --> 470.88]  I feel like I've lost a loved one.
[471.52 --> 474.44]  I guess I'll get a box at home and I'll have to back up to that from now on.
[474.44 --> 476.64]  But that's going to get very expensive.
[477.42 --> 478.12]  That is tricky.
[478.12 --> 479.08]  Well, it is.
[479.40 --> 480.82]  It is going to get expensive.
[481.40 --> 486.62]  But I would argue that the emotions you're feeling right now are also expensive.
[487.18 --> 491.48]  Just in a, you know, not dollars and cents necessarily, but they're expensive in a different way emotionally.
[492.50 --> 496.44]  And only you can quantify how much your data is worth.
[496.44 --> 504.78]  I mean, I don't know what was on this particular server for you, Kerry, but I certainly know in the past when I've lost data, it hurts.
[505.20 --> 516.68]  Genuinely, you spend the next few weeks, months, sometimes longer wishing you'd done things differently, thinking, oh, if only I'd spent a couple of hundred on a Pi and an external hard drive.
[516.68 --> 519.30]  And I wouldn't even be in this situation.
[520.56 --> 530.24]  I mean, if you think about what most typical VPSs are, they are probably less than a hundred gig disk, probably only a few gigabytes of RAM or something like that.
[530.32 --> 533.84]  So we aren't talking about a huge amount of data to back up here.
[534.32 --> 541.80]  And what I would say is if you've got no backup, I mean, literally zero, don't try and aim for perfect.
[541.80 --> 553.66]  Just get a 128 gig USB stick off Amazon and then just get in the habit of downloading your data once a month, once a year even.
[553.94 --> 559.84]  Because I'm sure right now you wish you'd had something, even if it was 11 months old, you'd have something.
[559.84 --> 571.82]  Something I've seen really common is a lot of people these days, when they have cheap cloud hosting, they're going for like a NUC with a disk hanging off it or something that they're syncing to locally.
[572.04 --> 576.72]  And getting that peace of mind by having the data on their local network.
[576.72 --> 583.72]  And I got to admit, it's kind of what I did for the Jupyter Broadcasting stuff is we have NextCloud up at Linode.
[583.88 --> 589.82]  And then we have NextCloud installed on the server at the Jupyter Broadcasting Studio on the LAN.
[590.22 --> 593.48]  And we sync the stuff that I really care about.
[593.58 --> 596.02]  We don't sync everything because it's hundreds of gigs.
[596.32 --> 600.42]  But locally, we actually will also archive.
[600.62 --> 603.88]  So I should probably back up the studio server now that I think about it.
[603.88 --> 609.10]  But we back up the cloud locally to anything that's not ephemeral.
[609.36 --> 611.22]  And anything that's not ephemeral, we try to keep locally.
[611.46 --> 615.14]  And then my intention is to back that server up somewhere.
[616.00 --> 618.70]  Alex's house, Backblaze, I don't know what.
[618.88 --> 620.86]  But I've got the cloud part covered.
[621.16 --> 623.98]  I just don't necessarily have the local part fully covered right now.
[624.18 --> 629.94]  Because I ended up, and this is sort of where I connected with what Carrie was saying, is I just ended up with terabytes of data.
[630.60 --> 630.92]  Terabytes.
[630.92 --> 634.66]  And I don't know, I don't really know how to even get that offsite over the wire.
[634.76 --> 635.32]  It's so much data.
[636.14 --> 644.08]  Never underestimate, I think the saying goes, the bandwidth of a truck driving down a highway full of hard drives.
[644.74 --> 646.72]  Get it on a hard drive and mail it to me.
[646.82 --> 647.72]  That's the best way.
[647.94 --> 652.04]  What you're saying is I should pack up the RV and drive a hard drive down to your place.
[652.62 --> 653.90]  That makes the most sense, right?
[653.94 --> 654.76]  You can if you want.
[654.92 --> 656.50]  $3,000 backup trip.
[656.50 --> 660.78]  But, you know, so that's something we all struggle with.
[660.78 --> 670.00]  But you remember when we went and saw Wendell, how he was implementing at his data center on his LAN, he was backing up his place was nuts.
[670.12 --> 670.24]  Yeah.
[670.30 --> 675.38]  And he was backing up his client's cloud data for them to his servers, just in case their cloud providers had issues.
[676.10 --> 681.28]  It's something you do kind of have to think about is when I'm building something, what is the risk to losing this?
[681.28 --> 688.70]  Like there's some things I have on the cloud that if they were lost, it'd be inconvenient, but we could regenerate from source material.
[689.68 --> 690.50]  Not everything.
[690.92 --> 691.00]  Yeah.
[691.16 --> 698.28]  It is about evaluating the, I don't want to say like opportunity cost or whatever, but everything has a cost.
[698.82 --> 702.76]  And, you know, photos, for example, are irreplaceable.
[702.98 --> 705.28]  You can't recreate those moments, videos, whatever.
[705.28 --> 717.66]  But, you know, a PDF with an invoice of some work you did 10 years ago, maybe that, okay, it might be nice to have it, but that's all just nice.
[717.66 --> 738.84]  But, you know, the cost of a one-time backup offsite to a pen drive or something like that is so small compared to the amount, just the amount of time you're going to spend noodling after you've lost some data whilst you reconstruct what was actually on that file system and remember, oh yeah, that was on that box as well.
[738.90 --> 739.82]  I lost that too.
[740.06 --> 743.40]  And some of that stuff won't occur to you until years later.
[743.82 --> 744.40]  That's very true.
[744.40 --> 749.28]  And it feels so, you just feel like you've, like somebody's cut a hole out of you sometimes.
[749.64 --> 759.40]  And I think that, especially when it comes to the pictures, I have opted to leave on for the iPhone members of my family our iCloud photo backup for everybody.
[759.88 --> 762.70]  I even ended up paying for like some sort of family storage plan.
[762.84 --> 772.32]  So that way I knew, because my mom's on there and, you know, my wife, and I just wanted to know that everybody's photos were backed up, even though I also back them up.
[772.32 --> 782.32]  My phone, every picture I take goes off to Nextcloud in 100% quality, but Google Photos also duplicates everything.
[782.68 --> 789.78]  I'm off the Google Photos sauce because I'm using the iCloud photo, but it's like, you know, trading one service for the other.
[789.78 --> 798.10]  I mean, there are arguments to be made for Google's privacy policies versus Apple's, but I'm not sure I fully trust either, to be honest with you.
[798.42 --> 799.12]  Yeah, yeah.
[799.22 --> 803.36]  I mean, I'm kind of gambling that Apple's are a little better and that they're not mining it for data, but...
[803.36 --> 804.42]  No, make no mistake, bro.
[804.54 --> 806.18]  Apple are mining you for your cash.
[806.44 --> 806.80]  Right.
[807.00 --> 807.44]  No kidding.
[807.66 --> 808.10]  No kidding.
[808.10 --> 814.30]  And we have talked about Google Photos alternatives, and it's not that I'm not going to implement one of those.
[814.34 --> 815.36]  That's actually been my intention.
[815.90 --> 821.36]  But I still feel like I get some value out of just paying Apple to back that thing up because they are so valuable.
[821.98 --> 823.52]  And that's really, photos are it.
[823.72 --> 827.08]  Like, pretty much everything else, I'm comfortable how I back it up.
[827.82 --> 830.44]  Although I know there's a couple of areas that I could probably do better.
[830.64 --> 835.66]  I mean, do you feel like there's an area where if you were to audit your backups right now, you'd look at it and go, oh, no, Alex, you got to fix it.
[835.66 --> 836.60]  Yeah, I do.
[837.20 --> 840.32]  So the last couple of months have been a bit crazy for me.
[840.38 --> 847.46]  My wife and I had our first daughter, and she came a little bit early, and she spent a couple of months in the hospital.
[848.20 --> 851.56]  So things have kind of been decaying whilst I've been there.
[852.06 --> 854.34]  Congratulations, an official on-show congratulations.
[854.66 --> 854.86]  Yay.
[855.92 --> 856.28]  Yay.
[857.00 --> 859.98]  I've known, but this is the first time you've said anything on the show, so it's exciting.
[859.98 --> 863.88]  Yeah, I didn't want to go public until she was home, just in case, because, anyway.
[864.66 --> 868.64]  She's home, she's healthy, everything's good with the world.
[869.02 --> 875.80]  So, yeah, I purchased the Helios as to be my on-site replication backup device.
[875.96 --> 876.10]  Right.
[876.10 --> 888.52]  And then when everything went down in January, and Ella was born, I was in the middle of rebuilding my server at that point, because that's when the whole GVTG thing started playing up and not working quite as I'd hoped.
[888.68 --> 895.66]  So, you know, I was at the hospital most of the day, but I'd come back here for two or three hours just to unwind and just mess around with hardware and stuff.
[895.66 --> 899.06]  And I never quite got to putting my backups back in place.
[899.16 --> 902.24]  And it's one of those things you think, oh, I'll get to it, I'll get to it.
[902.26 --> 906.00]  And then before you know it, a year later, you have a problem, you think, crap.
[906.44 --> 907.20]  I never got to it.
[908.56 --> 908.90]  Yeah.
[908.90 --> 914.94]  I do have plans, which we'll share with you soon, as to what's going to replace the Helios in that situation.
[915.20 --> 923.68]  But I'm tight-lipped for now, but we do have an upcoming segment on backups that will hopefully give you some ideas and inspiration.
[923.68 --> 927.64]  Linode.com slash SSH.
[927.72 --> 930.26]  Go there to get $100 in Linode credit.
[930.36 --> 933.72]  This could be the opportunity to try out Linode.
[933.82 --> 935.42]  Linode.com slash SSH.
[935.56 --> 937.12]  You also support the show.
[937.64 --> 939.48]  Linode is how we host in the cloud.
[939.70 --> 944.78]  We've built all kinds of backend services for the show and for Jupyter Broadcasting on Linode.
[944.78 --> 948.42]  And I have a peace of mind knowing that Linode has great support.
[948.52 --> 952.46]  So if I ever get stuck, well, I know they're going to take care of me.
[952.46 --> 961.78]  In fact, they just received, Linode just received the People's Choice Stevie Award for Favorite Customer Service in the Computer Services category.
[962.24 --> 963.72]  That's huge, you guys.
[963.96 --> 969.22]  Having great support has been one of the key things that people write into our show when they switch and tell us about Linode.
[969.48 --> 971.36]  They have 11 data centers worldwide.
[971.36 --> 980.54]  In 2016, they became their own ISP and have full control over their own network and have built out super fast connections to their worldwide data centers.
[980.54 --> 986.90]  They have a brilliant cloud manager that makes it simple to use Linode if you're a brand new user or if you're a pro.
[987.06 --> 988.30]  You're going to love what they have.
[988.48 --> 989.40]  Then there's the pricing.
[990.42 --> 992.66]  Linode has dialed this in.
[992.80 --> 994.22]  The value is nuts.
[994.58 --> 996.92]  They have systems, of course, are like $5 a month, right?
[996.96 --> 999.80]  But you can do different combinations depending on what you need.
[999.88 --> 1001.68]  Maybe you need a lot of memory or a lot of CPU.
[1002.10 --> 1003.16]  Maybe you need GPU.
[1003.28 --> 1004.56]  Maybe you need several GPUs.
[1004.66 --> 1005.74]  Maybe you need it all.
[1005.74 --> 1011.56]  I got to be honest, we recently just decided to go all in on our matrix server because it's getting busier and busier.
[1012.12 --> 1013.82]  And it's awesome what Linode lets you do.
[1013.92 --> 1020.16]  And even when you need to upgrade an existing machine or clone a machine or snapshot, it's all just brilliant in their cloud manager.
[1020.28 --> 1025.16]  I'm really impressed with the complexity that they can make seem so simple.
[1025.26 --> 1030.52]  You know, like I'm managing servers in data centers around the world and they just make it all seem so intuitive.
[1030.52 --> 1031.68]  So I like that.
[1031.74 --> 1034.90]  And you can really get a sense of that when you try out our $100 credit.
[1035.00 --> 1039.38]  $100 when you go to linode.com slash SSH.
[1039.54 --> 1040.82]  See what I've been talking about.
[1040.96 --> 1042.80]  And, of course, you support the show.
[1042.94 --> 1050.32]  When you go there and you visit that URL and you use that and you sign up, it tells Linode that our audience is supporting the show and that Linode should keep supporting us.
[1050.38 --> 1052.02]  It helps us put these shows out for free.
[1052.18 --> 1054.42]  It makes content like this possible.
[1055.00 --> 1056.68]  It's the circle of podcasting.
[1056.88 --> 1059.18]  Go to linode.com slash SSH.
[1059.18 --> 1062.40]  Don't be using that stinking Linux unplugged Linode code.
[1062.50 --> 1064.30]  You've got to be using that self-hosted Linode code.
[1064.38 --> 1064.74]  That's right.
[1065.00 --> 1065.46]  Live long.
[1065.70 --> 1067.40]  So hashtag SSH.
[1067.52 --> 1071.08]  Live long and go to linode.com slash SSH.
[1073.00 --> 1076.64]  My home assistant box password shamed me this week.
[1076.74 --> 1077.44]  Did you get this?
[1077.68 --> 1078.10]  Yes.
[1078.50 --> 1080.14]  Did you get it for the SSH add-in?
[1080.38 --> 1081.44]  That's what I think I got it for.
[1082.10 --> 1084.02]  Mine was node red, I think.
[1084.68 --> 1085.96]  Oh, node red.
[1086.10 --> 1089.16]  Alex, you're using a bad password with node red?
[1089.84 --> 1090.16]  Oh my goodness.
[1090.16 --> 1091.92]  Or maybe even home assistant itself?
[1092.18 --> 1092.36]  Yeah.
[1092.44 --> 1092.72]  I don't know.
[1092.74 --> 1093.30]  I've been a bit busy.
[1093.38 --> 1094.24]  I didn't actually read it.
[1094.76 --> 1097.22]  I just saw the notification and dismissed it.
[1097.26 --> 1097.96]  I was like, oh, whatever.
[1098.04 --> 1098.72]  I'll get to you later.
[1098.86 --> 1100.38]  I dismissed it and then mine came back.
[1100.50 --> 1106.74]  Mine is for the add-on core underscore SSH, which uses secrets, which have been detected as not secure.
[1107.40 --> 1110.02]  Probably a lot of people in the audience are getting this if they run home assistant.
[1110.02 --> 1113.02]  It's a new feature, quote unquote, that has been integrated.
[1113.78 --> 1116.00]  And frankly, probably a good one.
[1116.00 --> 1119.26]  Yeah, but the internet being the internet, people are pissed.
[1119.78 --> 1122.12]  I don't really get this.
[1122.36 --> 1126.38]  Maybe I'm just becoming a grumpy old man now I'm a dad.
[1127.08 --> 1131.38]  And outrage culture is just, I don't know, I'm just tired of it.
[1131.38 --> 1138.70]  So there's a link in the show notes to a post by Troy Hunt, who is an incredibly well-respected security researcher.
[1139.18 --> 1142.68]  And he's the guy that is behind the website, Have I Been Pwned?
[1142.68 --> 1145.28]  And this website is incredible.
[1145.40 --> 1153.04]  You can tap in any password into their database and it'll tell you that, yes, this password is out in the wild.
[1153.36 --> 1161.96]  And as Troy puts it, if your password is in this list, I've seen it clear text, which means that the bad guys have seen it clear text.
[1161.96 --> 1162.44]  Right.
[1162.70 --> 1171.72]  So no matter your opinion on how secure you think it is, I guarantee it's out there in the wild somewhere and somebody knows what it is.
[1171.76 --> 1173.40]  So don't use that password.
[1173.62 --> 1176.72]  It's actually pretty clever for the home assistant developers to build this in.
[1176.76 --> 1179.90]  So the way it works is your passwords are hashed.
[1180.30 --> 1188.60]  The first five characters of that hash, so just the first five characters of a hash of your password, are then used to query the Have I Been Pwned website.
[1188.60 --> 1192.70]  It then returns a result of possible password hashes that match.
[1193.26 --> 1197.88]  And then home assistant checks that list against your hash locally.
[1198.10 --> 1201.34]  All of that validation is happening on your box.
[1201.88 --> 1214.84]  And what I found really interesting, and Troy goes into full details in the article, he basically goes through the home assistant forums thread where people are bitching and moaning and whining about this feature being turned on without their permission.
[1214.84 --> 1224.66]  To give you an idea of how, I don't want to say stupid, but honestly, when I was reading this Troy Hunt article, I was like, yeah, this thread is stupid.
[1225.48 --> 1229.14]  Someone was complaining it was sending out data over their metered connection.
[1229.40 --> 1229.50]  Right.
[1229.60 --> 1232.96]  He then proceeded to say it's a few bytes.
[1233.32 --> 1234.72]  Like 36 kilobytes, you know?
[1235.00 --> 1235.28]  Yeah.
[1235.48 --> 1239.24]  We're talking five times smaller than the average web page load.
[1239.42 --> 1242.12]  If you notice that on a metered connection, then you've got problems.
[1242.54 --> 1242.74]  Right.
[1242.74 --> 1244.60]  We're not really talking very much data.
[1244.80 --> 1250.86]  And it's probably, although we don't know for sure, only happening when you start up home assistant or reload the config.
[1251.54 --> 1254.34]  How do you feel about doing this on your local LAN?
[1254.42 --> 1257.94]  I mean, I'm definitely guilty of reusing passwords on the internet.
[1258.58 --> 1260.90]  I'm certainly guilty of doing it on my LAN.
[1261.28 --> 1265.60]  That seems to be the crux of everyone's argument is my LAN, my rules.
[1265.60 --> 1272.10]  I have a safe, trusted environment, and I don't want to have to use good password hygiene.
[1272.30 --> 1274.54]  I don't want long passwords that are unique.
[1274.54 --> 1277.70]  And I can definitely relate.
[1278.40 --> 1284.52]  There's sort of, when you do this for a living, every now and then it's nice to be a little lazy.
[1285.04 --> 1289.90]  Like, you know, what's the saying about the guy who makes shoes, his kids always have the worst shoes?
[1290.54 --> 1291.30]  You know?
[1291.66 --> 1294.80]  Like, because you just get home, it's the last thing you want to do, right?
[1294.84 --> 1295.84]  It's just the last thing.
[1296.08 --> 1296.28]  Yeah.
[1296.28 --> 1298.08]  So I do understand that.
[1298.26 --> 1301.20]  However, this is where I fall down on it.
[1301.70 --> 1311.16]  The home assistant community is kind of a special case because they're playing around with IoT smart devices that are network connected.
[1312.20 --> 1319.08]  There's a higher threat level, a broader threat attack surface, if you will.
[1319.14 --> 1325.28]  And so I feel like you have to be a little more secure when you are willing to ride the IoT train, you know?
[1325.28 --> 1330.26]  Because the problem is any one of those individual devices one day could become compromised.
[1330.54 --> 1333.98]  And then that becomes a launching off point where they can go after other devices on your LAN.
[1334.04 --> 1335.34]  And we see it happen.
[1335.84 --> 1342.18]  And to that point, Troy actually makes this point in his article that LinkedIn, I mean, we're talking a proper website here,
[1343.06 --> 1348.64]  had a data breach because one of their developers' home networks had a weak SSH password,
[1348.64 --> 1356.04]  which allowed people to pivot through that developer's home network into LinkedIn servers and compromise LinkedIn that way.
[1356.48 --> 1357.82]  Yeah, they brute forced his iMac.
[1357.96 --> 1363.58]  And so, you know, I put myself in that developer's shoes and I think, well, holy crap, someone could pivot into Red Hat from here.
[1363.62 --> 1364.94]  And I wouldn't want that.
[1365.12 --> 1368.96]  So I think to myself, OK, actually, Troy, you've probably got a point here.
[1369.00 --> 1370.74]  I do need to step up my game.
[1370.74 --> 1372.72]  And he uses 1Password.
[1372.82 --> 1374.80]  I think he's on the advisory board for 1Password.
[1375.02 --> 1377.66]  But we talked last episode about Bitwarden.
[1378.20 --> 1385.34]  And I really cannot emphasize enough, you know, there are command line clients and stuff like that that you can use.
[1385.38 --> 1388.98]  So you can put it in scripts and do all sorts of fun stuff if you want to.
[1389.10 --> 1399.78]  And I think that's going to have to become a 2021 rather late New Year's resolution for me is to try and use that CLI stuff more on my LAN at least.
[1399.78 --> 1404.22]  Yeah, good passwords, I think, matter when we're kind of riding the cutting edge of technology.
[1404.22 --> 1411.94]  Even if you're not intentionally exposing your LAN to the Internet, you never know when some crazy thing could happen.
[1412.30 --> 1413.78]  It's unlikely, but it could happen.
[1413.98 --> 1424.82]  But really, you also never know if one day somebody's going to be able to rock up onto your Wi-Fi or something or somebody joins your LAN that you put on intentionally, but they have some misconfiguration or infection.
[1424.82 --> 1430.32]  So it's kind of like multiple layers of protecting yourself is the best kind of protection.
[1430.58 --> 1438.78]  And I think when you look at logins, you could look at maybe not only unique passwords, but when possible, also using keys to do SSH sign-ins.
[1438.98 --> 1440.80]  So that way you have to have maybe a key and a password.
[1441.18 --> 1442.98]  And that just takes it a little bit step further.
[1442.98 --> 1451.64]  Like that LinkedIn developer, if he had had a decent password or password and a key, then the attackers would have never gotten onto his iMac and then never gotten into LinkedIn.
[1452.12 --> 1465.80]  And when the whole COVID lockdown thing started and we had a lot more people all of a sudden working from home, that was one of my first concerns is, well, now all of these corporations are as insecure as people's home networks are.
[1465.80 --> 1468.46]  And you never know when that could be an issue as well.
[1468.60 --> 1475.92]  I just think as much of a pain in the arse as it is, there's enough tools and we know enough information now that it's worth doing.
[1476.22 --> 1483.10]  The only thing I would have changed with how Home Assistant has implemented this is give me an option to turn it off for a bit.
[1483.82 --> 1486.16]  You know, I'm not fixing it while I'm out here in the woods.
[1486.94 --> 1490.32]  Silence that checkbox for seven days or something, you know.
[1490.56 --> 1493.38]  Or until next update even, you know, that could work too.
[1493.38 --> 1497.86]  I do believe they're actually working on making it opt-in or opt-out now.
[1498.38 --> 1503.54]  So for what it's worth, the outrage has had some effect on the feature.
[1504.24 --> 1505.44]  But I mean, I think it's great.
[1505.56 --> 1510.76]  I think anything that we can do, and here's another point about the Home Assistant community being a special case as well,
[1511.48 --> 1517.98]  is a lot of people are coming to servers for the first time because of Home Assistant.
[1517.98 --> 1522.78]  They're running a box in their house for the first time that's got SSH listening on something.
[1523.38 --> 1524.90]  Maybe for the first time ever.
[1525.84 --> 1533.60]  And anything that Home Assistant can do for those kind of newer users that aren't, you know,
[1534.00 --> 1541.10]  enterprise-grade buffoons like me that just reminds them that, hold on, you know,
[1541.14 --> 1546.02]  if you're exposing your house to the internet through Nebukassar, through WireGuard,
[1546.16 --> 1548.86]  through whatever it might be, there is some risk.
[1548.86 --> 1555.28]  And then when you couple that up with some leaky washing machine that's running an old firmware from eight years ago,
[1556.14 --> 1557.62]  there are risks to these things.
[1557.68 --> 1562.00]  And I, for one, applaud the Home Assistant project for having the stones to put this in.
[1562.00 --> 1562.36]  Yeah.
[1562.66 --> 1568.00]  And it definitely, I think, will improve the community security overall, which is a good thing for them.
[1568.56 --> 1572.96]  And as they make this a commercial product one day, because you know this has got to be the direction this thing's going,
[1573.04 --> 1579.54]  when they try to make it a consumer product and not just a, you know, a more advanced prosumer or enthusiast product.
[1579.84 --> 1580.52]  Nerd product.
[1580.84 --> 1581.54]  Go on, you should say it.
[1581.66 --> 1582.20]  Nerd product.
[1582.48 --> 1583.58]  It's a nerd product right now.
[1583.58 --> 1589.24]  But one day, maybe one day they're going to try to sell it to average Joes who have bought all these smart devices.
[1589.24 --> 1591.26]  And now they just need something to make it all work together.
[1591.72 --> 1594.30]  And, you know, buy the $100 Home Assistant appliance.
[1594.60 --> 1596.22]  And you need these kind of things built in.
[1596.70 --> 1600.76]  And they just recently had a run-in with add-ons that were leaking information.
[1600.76 --> 1603.04]  So I could see why this is an area they're investing into.
[1603.50 --> 1604.52]  And I say good on them.
[1604.68 --> 1606.42]  And I think it'll be a smooth transition.
[1606.42 --> 1614.08]  There is also something worth looking into is they're working with K-Anonemy, which is a Cloudflare-hosted service.
[1614.30 --> 1617.62]  So Cloudflare is kind of proxying some of these requests to anonymize them.
[1617.92 --> 1620.74]  That's also made some people uncomfortable in all of this.
[1621.18 --> 1622.54]  But I did a read-through of the setup.
[1622.66 --> 1626.08]  And it actually, it seems like they've done a really, really solid job here.
[1626.20 --> 1632.08]  So we'll have a link in the show notes at selfhosted.show.40 for the Cloudflare information on that.
[1632.08 --> 1637.48]  And if that has also perhaps gotten the hairs on the back of your neck up a little bit, it's worth reading about.
[1637.56 --> 1638.26]  We'll have information.
[1638.80 --> 1643.48]  I'm super curious to hear what you all do for your local LAN password situations.
[1643.64 --> 1644.80]  Do you use a password manager?
[1645.38 --> 1648.78]  Are you like me and reuse the same password on every box?
[1649.66 --> 1650.16]  Let us know.
[1650.38 --> 1651.82]  Selfhosted.show slash contact.
[1653.68 --> 1656.34]  Datadog.com slash selfhosted.
[1656.44 --> 1656.80]  One word.
[1656.94 --> 1659.08]  Datadog.com slash selfhosted.
[1659.20 --> 1659.92]  Go there.
[1660.16 --> 1660.68]  Try it out.
[1660.86 --> 1661.90]  And get a free T-shirt.
[1662.52 --> 1665.36]  Datadog is going to solve problems and help you communicate them.
[1665.56 --> 1668.56]  Analyze code level performance across your entire environment.
[1668.96 --> 1672.22]  And troubleshoot issues faster with Datadog.
[1672.56 --> 1678.44]  You see, Datadog's continuous profiler automatically collects information from your production servers all the time.
[1678.44 --> 1683.84]  So then, when you're ready, when you need to, you can quickly look and analyze all of the data with minimal overhead.
[1684.24 --> 1689.58]  And get, finally, a unified picture of your entire environment.
[1689.58 --> 1697.00]  Correlate code performance with server metrics and other monitoring data in real-time, beautiful dashboards.
[1697.42 --> 1699.24]  Datadog.com slash selfhosted.
[1699.24 --> 1701.08]  Just to look at these dashboards.
[1701.08 --> 1712.04]  And then they have a lot of tightly integrated additions, add-ons, tracing, log management, and that continuous profiler that brings it all into one platform.
[1712.04 --> 1713.04]  That's Datadog.
[1713.38 --> 1718.74]  And imagine getting yourself a visual dashboard that you can use to communicate issues with your team.
[1719.12 --> 1720.36]  Developers to sysadmins.
[1720.60 --> 1722.18]  Sysadmins to executives.
[1722.66 --> 1723.54]  Make plans.
[1723.86 --> 1725.20]  Predict future performance.
[1725.82 --> 1726.62]  Try it all out.
[1726.62 --> 1729.30]  And take advantage of their machine learning alerting.
[1729.86 --> 1733.96]  Datadog enables you to pinpoint the root cause of an issue faster than ever.
[1733.96 --> 1740.56]  So try their products out for free for 14 days by visiting datadog.com slash selfhosted.
[1740.66 --> 1745.56]  For a limited time, if you start a trial and create one dashboard, you'll get some free swag.
[1745.68 --> 1746.56]  A Datadog t-shirt.
[1747.06 --> 1748.40]  And I miss swag.
[1748.68 --> 1750.06]  I miss event swag.
[1750.42 --> 1751.26]  I miss t-shirts.
[1751.78 --> 1752.44]  So go get one.
[1752.52 --> 1754.16]  Datadog.com slash selfhosted.
[1754.20 --> 1754.62]  Great account.
[1754.62 --> 1755.90]  Get that trial going.
[1755.98 --> 1756.54]  Get a t-shirt.
[1757.12 --> 1760.70]  And then begin visualizing your entire infrastructure.
[1761.04 --> 1763.14]  Datadog.com slash selfhosted.
[1765.10 --> 1766.52]  Listener Chris writes in,
[1766.64 --> 1770.14]  I run a number of services from my home server that are internet facing.
[1770.50 --> 1774.66]  I understand that the smart best practice is to minimize that as much as possible.
[1774.66 --> 1777.66]  But some of these things I want to access whilst I'm away from the house.
[1778.16 --> 1780.24]  Some of them are also used by family members.
[1780.32 --> 1782.68]  And so it's unavoidable on some levels.
[1782.94 --> 1784.08]  My question is this.
[1784.08 --> 1789.82]  How do I know if a service is hardened enough to raw dog it out on the open internet?
[1790.28 --> 1790.60]  Wow.
[1791.80 --> 1793.96]  We're just going to let's let that sit for a second.
[1795.16 --> 1795.96]  How do you know?
[1796.10 --> 1797.44]  How do you know if you can raw dog it?
[1798.06 --> 1798.40]  Yeah.
[1798.50 --> 1802.14]  I mean, I feel this one, you know, Plex is one, you know, Plex you kind of feel safe about.
[1802.22 --> 1806.04]  But how do you know about some of the lesser used ones like subsonic or something?
[1806.12 --> 1806.32]  Right.
[1806.32 --> 1810.20]  I think it's safe to assume that everything is porous.
[1811.20 --> 1811.56]  Everything.
[1812.06 --> 1812.34]  Yeah.
[1812.34 --> 1815.30]  I hate, though, that the answer always is put it behind a VPN.
[1815.76 --> 1815.98]  Why?
[1816.16 --> 1820.22]  I mean, with WireGuard these days, it's really the barrier to entry.
[1820.34 --> 1822.32]  As long as you don't screw up your subnets like I did.
[1823.22 --> 1824.62]  The barrier is pretty low.
[1824.78 --> 1828.92]  But you have friends and family that are using your Plex server without connecting to WireGuard.
[1829.26 --> 1830.72]  You know, like Plex is such a great example.
[1830.72 --> 1834.36]  Or Jellyfin because you do often want to share with others.
[1834.62 --> 1834.98]  That's true.
[1835.18 --> 1838.50]  And I could see that being true with others as well.
[1838.90 --> 1840.48]  Nextcloud he mentions in here.
[1840.66 --> 1843.66]  But BabyBuddy, I'm not so sure about that.
[1843.78 --> 1845.44]  You know, that starts to get a little more niche.
[1846.36 --> 1850.20]  And I hate to be the guy that just says, well, if it's big, you can use it publicly.
[1850.30 --> 1851.76]  And if it's small, you should hide it.
[1851.84 --> 1855.28]  But that's kind of a general rule of thumb that I follow.
[1855.88 --> 1857.62]  You know, you try to figure how many eyes have been on it.
[1857.62 --> 1861.02]  You know, another angle to consider is security by obscurity.
[1861.72 --> 1867.38]  Now, if you think that, you know, you just have a random URL that you're using to access this service.
[1867.58 --> 1869.14]  And you've put it behind a reverse proxy.
[1869.58 --> 1873.60]  And probably these days you're using Let's Encrypt to generate a certificate for it.
[1873.64 --> 1875.30]  So that you know that things are secure.
[1876.12 --> 1877.48]  Well, I've got bad news for you, I'm afraid.
[1877.54 --> 1881.96]  If you go to crt.sh and type in your domain name.
[1881.96 --> 1889.48]  You'll see every single certificate that's ever been issued by Let's Encrypt for your domain name.
[1890.10 --> 1899.26]  And so you think to yourself, okay, well now my super secret string that I came up with to hide this service is now out in the public domain.
[1899.38 --> 1901.82]  So really, it's not secret at all.
[1901.82 --> 1906.14]  One thing you could do to kind of work around that is use a wildcard certificate.
[1907.02 --> 1908.98]  That would kind of sort of help.
[1909.52 --> 1912.48]  Because it wouldn't, you know, publish the actual string.
[1913.40 --> 1919.92]  But it just goes to show to me that, you know, security through obscurity is really not, it's an illusion.
[1919.92 --> 1929.96]  Yeah, and I was going to suggest throwing it out on like a VPS like Linode and run your software there for a bit on the public internet and monitor the logs.
[1930.10 --> 1933.20]  But you could run something for six months and nobody nibbles at it.
[1933.28 --> 1938.14]  And then on, you know, day one of seven months, somebody nibbles on it.
[1938.56 --> 1939.78]  It's tricky that way.
[1939.78 --> 1949.38]  And so it really, the only way to have full peace of mind, and that's what I've opted to do here in Lady Joops, is just to have absolutely zero outside inbound.
[1949.92 --> 1954.02]  It's the only way I've found to be completely comfortable with it.
[1954.12 --> 1963.50]  I don't necessarily always follow that rule myself because some services like mail servers, web servers, media streaming servers, they have to be public by their very nature.
[1963.78 --> 1969.42]  So you have to hope that those just have more eyes and that they get a little more attention and that they've been a little more audited.
[1969.76 --> 1972.18]  But remember, logging is your friend.
[1972.40 --> 1975.94]  So if you ever suspect something weird is happening, go check your logs.
[1976.00 --> 1977.12]  See if you have weird logins.
[1977.12 --> 1979.30]  See if you have somebody hitting your website all the time.
[1979.30 --> 1980.36]  Use Datadog.
[1980.68 --> 1980.94]  Yeah.
[1981.26 --> 1981.58]  Yeah.
[1981.62 --> 1983.60]  Use something that will go through there and alert you.
[1983.72 --> 1985.22]  That absolutely could be a good way to go.
[1985.72 --> 1989.78]  It's a good question, though, listener Chris, because I'm sure it's one that people struggle with.
[1989.82 --> 1991.48]  So let us know what you out there would do.
[1991.96 --> 1993.68]  Self-hosted.show slash contact.
[1993.68 --> 1996.36]  Now, we have Joseph who writes in.
[1996.42 --> 2001.28]  He says, I have a bunch of those Tekken smart switches flashed with Tasmoto and they work great.
[2001.66 --> 2005.04]  I have a need for smart switches to replace my wall switches, though.
[2005.40 --> 2010.22]  You know, for example, like my kids' closet lights, which are always left on.
[2010.22 --> 2021.38]  I would also love to replace the controllers on our ceiling fans with smart devices, something that would toggle the light on and off and also set the fan to high, medium or low or even off completely.
[2021.60 --> 2026.76]  My preference would be for something I can self-host, non-cloud connected, open source software.
[2026.76 --> 2032.02]  Are there any devices which would actually fill this need or similar to the way the Tekken smart plugs do?
[2032.32 --> 2032.88]  What are your thoughts?
[2033.36 --> 2034.46]  Well, this is an easy question.
[2035.00 --> 2038.62]  The Shelly devices are exactly what you're looking for.
[2038.70 --> 2040.50]  And I think we've talked about them on a previous episode.
[2040.76 --> 2047.32]  But just to recap, they're about the size of an Oreo cookie and they go inside the light box behind the switch.
[2047.46 --> 2049.06]  So you don't change the switch itself.
[2049.52 --> 2054.42]  But this little cookie size box has a relay inside it.
[2054.84 --> 2056.30]  You need to do a little bit of wiring.
[2056.30 --> 2057.76]  So, you know, mains voltage.
[2058.16 --> 2060.88]  Be careful or get an electrician if you're not comfortable.
[2061.62 --> 2062.64]  They make a few products.
[2062.74 --> 2067.62]  So they make a 2.5, which will let you do up to two switches in the same box.
[2068.16 --> 2070.32]  They make a single unit as well.
[2070.46 --> 2074.98]  And they make a bunch of other stuff that does like rolling shutters for garage doors and all sorts of stuff.
[2075.50 --> 2078.54]  So go to Shelly.cloud and check out their stuff if you're interested.
[2078.74 --> 2080.44]  But it's exactly what you're looking for.
[2080.70 --> 2082.72]  And you can put TAS motor on them.
[2083.34 --> 2085.06]  So Mahendra writes in.
[2085.06 --> 2088.98]  In the latest episode, you suggest file run for a simple file browser.
[2089.40 --> 2093.00]  I wanted to suggest another minimalist alternative.
[2093.40 --> 2100.36]  It's very light with no database required at github.com slash file browser slash file browser.
[2100.60 --> 2101.86]  God, that rolls off the tongue, doesn't it?
[2102.28 --> 2102.96]  It's very simple.
[2103.06 --> 2103.58]  Easy to remember.
[2104.08 --> 2104.30]  Yeah.
[2104.36 --> 2108.76]  It is just a web-based file browser that sits on top of a directory.
[2108.92 --> 2110.30]  Each user gets their own directory.
[2110.30 --> 2112.42]  And it's just a standalone app.
[2113.08 --> 2113.84]  Pretty simple.
[2114.36 --> 2114.96]  I like it.
[2115.22 --> 2117.16]  Even easier than the one we had talked about before.
[2117.46 --> 2119.16]  So I'm going to think I'm going to grab this and try it out.
[2119.64 --> 2120.16]  It is nice.
[2120.34 --> 2121.58]  Yeah, I tried it out before the show.
[2121.84 --> 2125.24]  And I kind of wish I hadn't bothered with file run now.
[2125.40 --> 2132.46]  This is, I think, my new standard kind of throw it up and forget about it remote access software.
[2132.46 --> 2133.72]  So, yeah, great job.
[2133.78 --> 2134.66]  Thanks for writing in, Mahendra.
[2135.50 --> 2139.54]  Now, I've mentioned Chowdown a couple of times on the show before as a self-hosted recipe app.
[2139.78 --> 2140.50]  I still use it.
[2140.56 --> 2141.26]  I still love it.
[2141.34 --> 2145.52]  It stores all of my recipes in clear text files on disk.
[2145.72 --> 2146.96]  But there are some alternatives.
[2147.48 --> 2149.72]  And we've had a couple of listeners write in.
[2150.08 --> 2152.22]  And one of them is called Tandoor Recipes.
[2152.28 --> 2153.14]  What do you think of this one, Chris?
[2153.36 --> 2154.66]  It looks really good.
[2154.66 --> 2164.50]  And this, if anything, would probably get me to start doing something like this because it has a planning aspect, which is useful for a guy like me.
[2164.56 --> 2168.40]  I can do a little meal planning, but also has a sharing feature.
[2168.64 --> 2174.46]  And it's all on a progressive web app, which means my wife and I could share it like on our phones, which I think would be really nice.
[2174.46 --> 2179.50]  And then the other thing I would need is, and it does support importing from Chowdown, is import.
[2179.60 --> 2187.56]  And it has Chowdown import as well as Nextcloud cookbook import, Mealy, paprika, saffron, and a couple of others it can import from.
[2188.22 --> 2190.46]  I think it's easy to try out.
[2190.96 --> 2197.60]  Now, we have mentioned this one previously because it goes by the name vabeen1111 slash recipes on GitHub.
[2197.84 --> 2199.12]  That's the repo it's in.
[2199.76 --> 2201.88]  I think the Tandoor name must be new.
[2201.88 --> 2204.30]  I don't know how old exactly it is.
[2204.46 --> 2206.64]  Yeah, it is a new release too.
[2206.80 --> 2208.32]  So that might be maybe they did a name change.
[2208.62 --> 2210.66]  But they are using mkdocs for their documentation.
[2211.18 --> 2212.74]  So I've got to give them a plus point for that.
[2213.18 --> 2219.46]  Yeah, it says here that they're happy to announce they've released a new version, which gives the application its well-deserved name and logo, Tandoor recipes.
[2219.62 --> 2220.18]  So there you go.
[2220.60 --> 2222.62]  It runs out of a Docker container.
[2222.90 --> 2225.38]  It will also run on Unraid, Synology, Kubernetes.
[2225.74 --> 2227.74]  You can do it manually as well if you want to.
[2228.40 --> 2232.36]  There's a bunch of interesting stuff about syncing and storage in their documentation.
[2232.36 --> 2237.88]  So it's going to take a lot for me to throw away Chowdown because I do genuinely really like it.
[2237.96 --> 2241.68]  And I've modified the CSS so I've got some fuzzy search.
[2241.74 --> 2243.10]  You know how I love my fuzzy search.
[2243.24 --> 2244.00]  Oh, that's cool.
[2244.28 --> 2246.08]  You know, I've customized Chowdown for my own needs.
[2246.54 --> 2248.92]  But then maybe the grass is greener.
[2248.94 --> 2250.04]  Maybe I should try this one out.
[2250.46 --> 2252.24]  I mean, it does have the import functionality.
[2252.24 --> 2254.94]  Downside, though, is it needs a Postgres database.
[2255.42 --> 2260.88]  And I've already got, like, it feels like a dozen different database containers running.
[2260.96 --> 2262.14]  Do I need another one?
[2262.62 --> 2265.44]  That is a constant internal battle.
[2265.62 --> 2267.70]  And sometimes I'm just down to, ah, who cares?
[2267.80 --> 2268.64]  Just run a whole bunch.
[2268.72 --> 2269.56]  You've got the resources.
[2269.70 --> 2273.60]  And other times, like the sysadmin in me is just not having it.
[2274.12 --> 2277.18]  It's just you can't run three copies of Postgres.
[2277.30 --> 2278.20]  That doesn't make any sense.
[2278.28 --> 2279.00]  They're different versions.
[2279.08 --> 2281.44]  They have different security issues, different features.
[2281.44 --> 2282.22]  What are you doing?
[2282.82 --> 2284.44]  And it's a recipes app at the end of the day.
[2284.76 --> 2285.90]  Like, you know what I mean?
[2286.08 --> 2291.90]  Just having the files in clear text on disk feels more future-proof to me.
[2292.04 --> 2297.54]  So if this person loses interest in maintaining this particular app for whatever reason,
[2297.78 --> 2300.64]  I'm not up the creek without a paddle, so to speak.
[2300.64 --> 2302.22]  That, I think, is a great feature of Chowdown.
[2302.66 --> 2306.14]  That kind of clear text back end gives me peace of mind.
[2306.34 --> 2307.10]  That's just it.
[2307.22 --> 2308.50]  Peace of mind for that kind of stuff.
[2308.86 --> 2311.04]  And if Chowdown stops working for some reason,
[2311.04 --> 2314.10]  I can just pull it up in any text editor and it's still readable.
[2314.52 --> 2317.24]  Yeah, it's almost as good as writing them down on an index card.
[2318.52 --> 2320.08]  You know, you laugh at that.
[2320.18 --> 2324.56]  But I'm pretty sure if I asked my mom to go and find me a recipe for something,
[2325.36 --> 2328.12]  she would find it in less time than it takes me to fix.
[2328.58 --> 2329.90]  Oh, Chowdown's not working?
[2330.06 --> 2334.20]  Okay, well, let me just SSH in and do this, do that, do the other.
[2334.70 --> 2336.04]  And before you know it, 10 minutes later,
[2336.04 --> 2338.10]  you've forgotten that you're actually looking for a recipe,
[2338.10 --> 2340.12]  and then you go and order pizza instead, so.
[2341.42 --> 2344.08]  Yeah, and meanwhile, she's got the index card ready to go.
[2344.18 --> 2344.84]  It's very true.
[2345.04 --> 2345.96]  There's something to that.
[2346.64 --> 2350.08]  A reminder, you can find our sponsor, our Cloud Guru, on social media.
[2350.22 --> 2351.66]  They're just slash a Cloud Guru.
[2351.82 --> 2353.68]  It's really easy, like on Twitter, Facebook, YouTube,
[2353.98 --> 2355.50]  pretty much all the social media platforms.
[2355.80 --> 2357.16]  Just slash a Cloud Guru.
[2357.66 --> 2358.62]  Also, our members.
[2358.86 --> 2361.64]  Thank you to our members, selfhosted.show slash SRE.
[2361.78 --> 2362.64]  You support the show.
[2363.20 --> 2365.00]  You become our site reliability engineers.
[2365.00 --> 2367.76]  You get a limited ad feed and extra content.
[2368.20 --> 2369.34]  The post show.
[2369.92 --> 2371.52]  Selfhosted.show slash SRE.
[2371.72 --> 2373.64]  If you'd like to support the show and become a member.
[2374.16 --> 2375.64]  My Wisecam 3 came in this week,
[2375.70 --> 2377.26]  so we're going to have a little chat about that today.
[2377.36 --> 2378.64]  Yes, that's going to be the post show.
[2378.68 --> 2380.46]  I ordered a few of them, so I got thoughts.
[2380.60 --> 2381.14]  Of course you did.
[2383.06 --> 2385.32]  So you can go to selfhosted.show slash contact,
[2385.60 --> 2387.28]  and that's the place to go to get in touch with us.
[2387.52 --> 2390.56]  You can find me on Twitter at Ironic Badger.
[2390.56 --> 2393.26]  Oh, I'm there as well, at Chris Elias,
[2393.38 --> 2395.68]  and the show is at selfhosted.show.
[2395.98 --> 2398.20]  On Discord, I'm at AlexKTZ.
[2398.62 --> 2400.00]  So thanks very much for listening, everybody.
[2400.26 --> 2402.68]  That was selfhosted.show slash 40.