2021-SelfHosted-Transcripts / 48: A Solution Looking for a Problem _transcript.txt
willtheorangeguy's picture
add all 2021 transcripts
c844cb3 verified
[0.00 --> 6.40] This episode is brought to you by the all-new A Cloud Guru, the leader in learning for cloud, Linux and other modern tech skills.
[6.78 --> 13.12] Hundreds of courses, thousands of hands-on labs. Get certified, get hired, get learning at acloudguru.com.
[14.62 --> 22.78] This is a bit of an awkward one. Chris just messaged me and said that he's poured 15 gallons of water all over his MacBook Pro for some reason.
[23.00 --> 24.86] I don't know why he'd go ahead and do that.
[25.12 --> 29.86] So we have a backup post today. We have Morgan joining us from Florida. Hello, Morgan. How are you?
[30.24 --> 33.84] You know, a little hot, a little sweaty, but it's what I'm used to.
[34.16 --> 36.54] Nothing compared to the Pacific Northwest this week.
[37.08 --> 39.06] Yeah, I can't complain about that. At least I have AC.
[39.62 --> 42.96] Yeah, yeah. Down in Florida, I mean, you kind of have to have it, right?
[43.12 --> 47.80] So, Morgan, you last joined us on episode 18 to talk about doorbells.
[47.80 --> 50.10] So does that make you our resident doorbell correspondent?
[50.34 --> 56.56] Well, seeing how the doorbell died on me, and I think it was actually the heat that killed it, maybe.
[56.56 --> 60.06] All right. Well, let's talk about doorbells, shall we?
[60.10 --> 66.00] Last time you were on, you were testing one of the cloud-free doorbells for us.
[66.26 --> 67.60] And how's that been going?
[67.60 --> 77.66] So a couple months ago, I would say back in April, I went to check to see if a package was left at my door, and I noticed I couldn't connect to the doorbell.
[77.66 --> 85.54] So I fired up the, you know, Unify app, and I noticed it disconnected at about seven-something in the morning the day before.
[86.18 --> 88.50] You check the actual doorbell itself.
[88.68 --> 89.68] It still has power.
[89.80 --> 90.38] It works.
[91.06 --> 92.54] But the camera doesn't work.
[92.66 --> 94.76] So, you know, I go on the website.
[95.34 --> 96.24] No real help.
[96.36 --> 100.56] There's a forum, because as you guys know, this is a generic relabeled camera.
[100.56 --> 109.42] So I go on the website, the EasyViz website, and I start taking a look, and there's like 10 or 12 different ways to save it, to bring it back.
[110.08 --> 110.44] Nothing.
[110.76 --> 112.26] You know, I couldn't get it to come back.
[112.70 --> 118.04] You know, we were super concerned about heat, and it just died on me.
[118.18 --> 123.56] You know, I pulled out the SD card, and I threw it in there, and, you know, I had it set to just record nonstop.
[123.56 --> 127.24] And sure enough, like right at 7 a.m. in the morning, it just died on me.
[127.86 --> 130.64] You know, the SD card's fine, but it just died.
[131.50 --> 134.82] To check that it wasn't the transformer, I replaced the transformer.
[135.48 --> 137.66] I replaced the electronic doorbell itself.
[138.26 --> 139.84] Everything was fine, just the camera.
[140.04 --> 144.62] So I don't know if, you know, I just got unlucky.
[145.16 --> 147.26] You know, the model I had had an issue with it.
[147.26 --> 153.52] And I've seen other people talk about how they have them in Arizona, and they reach, you know, temperatures a lot higher than what I have.
[153.64 --> 155.86] But unfortunately for me, it died.
[156.66 --> 157.66] Is yours in direct sunlight?
[158.20 --> 161.94] It is in direct sunlight for the last hour or two of the day.
[162.66 --> 167.62] Luckily, my front door faces west, and, you know, the houses are two stories.
[167.62 --> 171.22] So with the trees, usually the last two hours of the day.
[171.54 --> 174.32] And it doesn't get enough direct sunlight to get too hot.
[174.32 --> 178.52] But again, as we mentioned on the original show, it's hot to the touch, you know.
[178.60 --> 179.78] So that was a concern.
[180.26 --> 182.78] And maybe that's the reason why it bit the bullet.
[183.16 --> 190.58] Well, I mean, on the flip side, I've been using the EasyVis branded version of this doorbell for the last year or so at my house.
[191.04 --> 197.46] And as you say, it runs a bit warm, but I've not had any issues with it dropping out or stopping working or anything like that.
[197.46 --> 201.36] I guess it's just based on your field research.
[201.52 --> 202.62] It's just a matter of time, hey?
[202.62 --> 208.38] The downside is there's not a lot of options out there other than these EasyVis clones.
[209.36 --> 214.78] RCA makes an EasyVis clone, and a lot of people are saying that the firmware is actually a little bit better.
[215.70 --> 218.08] You know, Wyze just came out with a camera.
[218.42 --> 221.70] And unfortunately, you know, Wyze did a little bit of trickery.
[222.02 --> 226.90] You know, there's a USB port that they cover with a sticker that they don't tell you that's there.
[226.90 --> 230.20] You know, there's a YouTube video that shows you how to access that.
[230.54 --> 233.74] And it's actually really great for, you know, places like an RV.
[233.74 --> 236.38] But it's cloud storage only.
[237.10 --> 241.12] You know, there's no SD card port.
[241.12 --> 245.70] So you're in a situation where you're really being forced into the cloud.
[246.28 --> 250.80] And the only viable option that I can find is back to the EasyVis clone.
[251.26 --> 259.72] And to be honest with you, I've run without a doorbell camera for a while because I don't want to buy something that I know is not going to be good.
[259.72 --> 266.60] So I may find myself again in the next few days with yet another EasyVis clone.
[267.10 --> 269.08] Or I may go with the RCA.
[269.30 --> 272.74] The RCA one, it seems to be the one that everybody recommends.
[273.42 --> 273.96] Yeah, it's interesting.
[274.08 --> 278.38] Looking at the Wyze website, they've started making pretty much everything.
[279.00 --> 284.84] I've seen a smartwatch from them recently and doorbell on top of the cameras and all that kind of stuff.
[284.94 --> 289.18] So they're really expanding their business pretty aggressively at the moment.
[289.18 --> 292.00] And I'm not sure how to feel about it.
[292.26 --> 301.10] Like, they obviously made their name with these really cheap, affordable $20 little cameras that most people use.
[301.14 --> 304.50] And I've still got a couple in this house that have got the RTSP firmware on them.
[305.06 --> 305.68] They work great.
[306.10 --> 313.68] But the version 3s, the company says the RTSP firmware is, air quotes, coming soon.
[314.18 --> 315.94] And that was six months ago.
[316.18 --> 318.48] And yeah, it hasn't come soon yet.
[318.48 --> 319.96] So I don't know.
[320.04 --> 321.46] Why is it kind of on thin ice with me?
[321.56 --> 326.36] So I'd be wary of going down that route just for that reason alone.
[326.94 --> 335.68] There's definitely a market right now for somebody to come in and make a doorbell that is just bare bones.
[336.00 --> 336.98] It does what you need.
[337.24 --> 341.70] SD slot powered either by batteries or powered by a transformer.
[341.70 --> 345.88] And has the ability to be connected to, you know, to stream.
[346.68 --> 349.00] The future is getting you into that monthly payment.
[349.50 --> 354.78] And the more features they strip out, the better chance that you're going to make that monthly payment.
[355.18 --> 356.60] And it's really unfortunate.
[356.60 --> 360.08] And it makes home labs and self-hosting even harder.
[360.08 --> 364.22] I don't know what's going to happen if EasyViz stops selling the clones.
[364.50 --> 366.98] I mean, that model is, I think, a little over two years now.
[367.04 --> 369.62] It doesn't look like they're looking to come out with a new one.
[370.24 --> 372.02] Planned obsolescence is a real problem.
[372.02 --> 386.26] And I think one of the things we can do to kind of help the environment in that respect from, you know, pointless e-waste is, I suppose, on the one hand is consume less, right?
[386.38 --> 387.76] Buy less stuff that we don't need.
[387.84 --> 395.18] I mean, our doorbells have functioned fine for 30 years as just a little switch with a wire going to a little bell in the hallway.
[395.18 --> 404.92] Anyway, the fact that we're sat here talking about them having a camera in them and all sorts of circuitry and stuff when there's a global chip crisis is very much a first world problem.
[405.60 --> 414.12] But on the other hand, I think these companies can do a lot more to help us, help them, really, in having open devices and open firmwares.
[414.12 --> 420.94] And I saw some news today come out of the UK about this right to repair bill that they've passed.
[420.94 --> 433.88] And how it's unbelievable, the right to repair bill they've passed doesn't include laptops and phones, which are two of the most important devices that people upgrade regularly.
[434.06 --> 446.32] I mean, fridges and washing machines and all that kind of stuff are important, of course, because they're very bulky and, you know, refrigerant and all that kind of stuff is, it's not endless to manufacture this stuff.
[446.32 --> 457.26] But yeah, I think there's some kind of ethical responsibility that these manufacturers have to start playing, you know, playing the game.
[457.64 --> 460.38] But it's all about where's the incentive?
[460.58 --> 466.36] Like if, let's take Samsung, for example, if they make a smartphone and it lasts three years,
[466.36 --> 474.38] they foot exactly 0% of the bill to recycle, to, you know, dispose of that item.
[475.00 --> 478.60] They sell me the phone, I use it for a little bit and I throw it in the bin.
[479.50 --> 483.50] The transaction so far as Samsung is concerned is I've bought the phone.
[483.80 --> 490.70] There's no consequence for them if I throw it in the bin after a day or after three years.
[490.70 --> 502.74] And I think until we have a way of getting companies attached to their environmental footprint, if that's even the right word,
[502.88 --> 508.88] that, you know, the waste that their products generate by failing prematurely, this cycle is just going to perpetuate.
[509.42 --> 509.84] That's a good point.
[509.84 --> 520.72] The other thing you're taking consideration is you have CEOs of major car manufacturers who are guilt tripping cryptocurrency miners for wasting electricity
[520.72 --> 527.66] without taking into consideration of how does the electricity get produced that then powers the very car he sells.
[528.34 --> 530.32] I wonder who you could be talking about there.
[530.40 --> 532.92] I think his name begins with E and ends with Lon, right?
[533.42 --> 534.02] Possibly.
[534.18 --> 535.90] But that's another topic for another day.
[536.24 --> 539.68] And I don't want to get attacked on a Twitter account I don't have.
[539.84 --> 547.68] Well, speaking of Twitter, Home Assistant announced this week that they're going to be working on an official two-year integration.
[548.18 --> 548.90] This is pretty cool.
[549.00 --> 556.02] So two-year, the manufacturer, are going to be actually writing software that is compatible out of the box with Home Assistant.
[556.60 --> 559.04] I've struggled to deploy Home Assistant.
[559.60 --> 561.30] And it's not because I don't want to use it.
[561.78 --> 566.32] It's because I just can't make up my mind what product to go with.
[566.32 --> 575.00] And I think the biggest issue that I'm having is I want to host my own solutions, but I don't want to get vendor lock-in.
[575.48 --> 580.40] I don't want to go with something that requires me to do a hack install.
[580.40 --> 583.00] I want something that's just going to be easy.
[583.16 --> 584.30] I can take it out of the box.
[584.46 --> 585.86] I can connect it to my Wi-Fi.
[586.20 --> 587.98] I can wire it into my device.
[588.20 --> 589.68] And then I can go into Home Assistant.
[589.92 --> 591.18] I click a wizard and it's done.
[591.84 --> 595.02] And I've talked to a lot of other people who are in the same situation.
[595.38 --> 599.92] We have a lot of really intelligent people who are out there that are very tech savvy,
[599.92 --> 608.12] but they don't want the hassle of having to configure XML files or JSON or installing firmware, etc., etc.
[608.38 --> 609.48] It is a pain.
[609.72 --> 616.12] And it's the biggest roadblock that I see to get people to adapt.
[616.46 --> 621.34] So to hear that somebody is going to come out and design something that is going to work directly with Home Assistant
[621.34 --> 625.04] and is integrated into their firmware is phenomenal.
[625.04 --> 632.96] What's really exciting about this piece of news is that they say that they're going to do the cloud API first with a local API to follow.
[633.40 --> 638.84] Now, I love me a good local API because I don't see why, if I have a light bulb next to me on my desk,
[639.16 --> 645.38] why does it need to go all the way to a data center in outer Mongolia and then come back to my desk again?
[645.54 --> 647.74] I mean, it's got to travel six feet.
[647.92 --> 649.96] So why don't we just do that?
[650.28 --> 651.54] Why do we need to go out and in again?
[652.10 --> 653.82] So that's very exciting to me, too.
[653.82 --> 655.12] Yeah, I totally agree.
[655.38 --> 657.52] And it's interesting what you're saying about a local API.
[658.18 --> 664.22] When you got me hooked on Shelleys and I wired a couple of Shelleys in to control some lights around the house,
[664.68 --> 667.04] the first thing I did is I timed it.
[667.36 --> 674.68] How long does it take to tell Alexa to turn off the light compared to how long does it take to open the app?
[674.74 --> 677.82] And I click the lights off and they turn off.
[678.42 --> 681.72] And these are seconds that we're talking about.
[681.72 --> 685.92] But just the idea that it's instantaneous, right?
[685.96 --> 687.88] We're not having to transverse the internet.
[688.22 --> 694.32] I have no idea who's looking at my packets, what Amazon is trying to do with what I just said.
[694.78 --> 698.48] But the idea that it's local, it's in your house.
[698.72 --> 702.68] If you lose internet, you can still control your lights.
[702.94 --> 704.50] Can't do that when you're cloud connected.
[704.50 --> 708.28] We've probably got some people listening that are going, yeah, what was wrong with a light switch?
[708.36 --> 710.90] I mean, you could control your lights without the internet with a light switch.
[711.52 --> 714.88] But, you know, you can't automate a light switch particularly well.
[715.06 --> 717.76] I suppose you could have a child and get them to walk over and flick the switch.
[717.88 --> 720.38] But that's quite an expensive solution, really, isn't it?
[720.38 --> 726.80] Yeah, and I have six lights that are embedded in the ceiling where I watch our movies.
[727.26 --> 731.24] And sometimes I want four of them on or I want the two behind me on.
[731.58 --> 734.62] And previously, they were all wired to an on and off switch.
[734.94 --> 740.26] And I really don't want to be in a situation where I need to run six, eight switches to get what I want.
[740.72 --> 744.08] But I spent a day, ran some wires, installed some Shelleys.
[744.08 --> 749.86] When I say turn off one, two, three, and four, they turn off.
[750.32 --> 751.16] Bada bing, bada boom.
[751.84 --> 759.40] A couple months ago, I finally decided that I was going to pull out the wallet and make some purchases and build a home server.
[759.82 --> 763.74] Now, I had a home lab that I previously talked about before, but it was just that.
[763.82 --> 764.42] It was a lab.
[764.64 --> 766.80] I tore it up, broke it a lot.
[767.10 --> 768.06] It broke a lot.
[768.06 --> 777.54] So it wasn't something that I could reliably count on to host services that my kids need every day.
[777.88 --> 783.36] To watch movies, TV, to listen to music, all that good stuff.
[783.64 --> 785.02] Really important stuff, right?
[785.46 --> 787.90] The things that keep them from driving me insane.
[788.92 --> 794.88] So, Alex, you had a UNAZ that you had bought and you didn't need it anymore.
[794.88 --> 798.86] So I graciously, for a decent price, took that off your hands.
[799.76 --> 807.14] And, you know, I set it up, got it all built, slapped in a bunch of spinning disks, set up MergerFS.
[807.68 --> 812.62] Well, I didn't go to perfectmediaserver.com and I didn't read the directions.
[813.02 --> 815.46] So I totally didn't set up MergerFS properly.
[815.72 --> 822.54] And I found out that we really couldn't stream two or three movies at a time because they just weren't handling the bandwidth.
[822.70 --> 824.02] And I was like, what did I do wrong?
[824.02 --> 826.74] And then I realized, ah, genius.
[827.48 --> 828.76] Everything's going to one disk.
[828.90 --> 831.40] You're trying to stream a bunch of movies at one time.
[831.58 --> 833.12] People are trying to listen to music.
[833.24 --> 834.14] It's just not going to work.
[834.44 --> 839.46] So I had to find something that would let me properly rebalance, right?
[839.78 --> 841.44] And off to Google I went.
[841.68 --> 843.98] And so I fell upon MergerFS-tools.
[844.68 --> 846.56] You know, it's over on GitHub.
[847.26 --> 847.70] Fantastic.
[848.04 --> 848.88] Easy to set up.
[849.72 --> 850.58] Clone the repository.
[850.58 --> 855.12] Within seconds, everything's being rebalanced across my drives.
[855.12 --> 857.14] Yeah, these tools are really great, actually.
[857.38 --> 858.36] And there's a few of them.
[858.58 --> 862.40] It's mergerfs.ctl.fsoc.dupe.
[862.40 --> 865.78] And the first one is mergerfs.ctl.
[866.08 --> 869.70] This is a wrapper around the MergerFS-x-atra interface.
[870.54 --> 876.02] Essentially what this lets you do is add and remove drives as well as get info about the array that's in there.
[876.70 --> 880.14] And, you know, print things like your version and your mount point and stuff like that.
[880.52 --> 881.72] Pretty useful if you need it.
[882.08 --> 885.22] Probably most people won't need that one, but it's there if you do.
[885.22 --> 889.52] The next one is mergerfs.fsoc.
[890.04 --> 892.22] So mergerfs.fsoc.
[893.50 --> 897.80] Audit's permissions, ownerships of files and directories in a mergerfs.mount.
[898.08 --> 902.72] And then one of the great tools that I really like is mergerfs.dupe.
[902.88 --> 903.38] No, no, no.
[903.42 --> 903.68] Hold on.
[903.90 --> 906.90] Before we sweep this under the carpet, we've got to clear this up.
[907.40 --> 908.78] Fsoc or fs.check.
[909.04 --> 913.98] If you have an opinion on this, let us know at self-hosted show on Twitter, please.
[913.98 --> 914.58] I don't know.
[914.70 --> 916.58] I think fsoc sounds a little dirty.
[917.44 --> 917.84] fs.ck.
[919.50 --> 921.24] All right, mergerfs.dupe.
[921.26 --> 925.46] This one duplicates files and directories across different branches in a pool.
[926.22 --> 930.00] The selected file can be duplicated using the dupe option.
[930.32 --> 936.74] So this could be useful if you're not using something like SnapRaid for kind of parity type redundancy.
[937.00 --> 942.58] This one would literally physically duplicate a file across X number of disks.
[942.58 --> 946.12] And then, of course, you have the follow-up to that, which is mergerfs.dupe.
[946.62 --> 948.10] Ddupe does as it says.
[948.18 --> 950.26] It finds removed duplicate files across pools.
[950.92 --> 955.88] You know, you can set up ignore, ddupe, and strict options to target specific use cases.
[955.88 --> 964.28] I can tell you, this one I used right away because as I was copying pictures over, you know, I copied them from my Mac.
[964.38 --> 965.94] I copied them from my Fedora box.
[966.16 --> 970.28] And I knew that I had them in multiple places because, as they say, if you don't have three copies...
[970.28 --> 971.34] It may as well not exist.
[971.58 --> 971.72] Yeah.
[971.72 --> 977.30] The first thing I did is I ran the ddupe, you know, because this became my fourth copy.
[977.54 --> 980.60] And there was no point in having multiple of the same files everywhere.
[980.86 --> 982.12] And it was really quick.
[982.20 --> 983.10] I was really surprised.
[983.68 --> 989.12] One of the things I like about the ddupe tool is, by default, it doesn't actually delete anything.
[989.32 --> 997.42] You have to explicitly set execute mode, which, you know, for fat-fingered people who don't read the docs like me on occasion, that's a good thing.
[997.42 --> 1004.60] And then again, as I originally mentioned, there's the MergerFS balance, you know, probably the best feature you're going to run into.
[1004.80 --> 1008.48] It's going to make sure that your data is balanced equally across the pool.
[1008.90 --> 1010.92] You know, you can set a defined range.
[1011.02 --> 1012.62] I think the default is like 2%.
[1012.62 --> 1016.16] So the last one is MergerFS.consolidate.
[1016.24 --> 1018.86] And this does the complete opposite of balance, really.
[1018.94 --> 1023.94] It takes things from multiple places and puts them and co-locates them all onto one single drive.
[1024.90 --> 1026.60] That one requires rsync.
[1026.60 --> 1028.86] I think there's a couple of others that require rsync as well.
[1029.32 --> 1033.06] But obviously under the hood, it's just doing some rsync magic to copy that stuff around.
[1033.80 --> 1034.30] It's definitely great.
[1034.36 --> 1038.50] Like I said, if you're running MergerFS in your home lab, definitely check it out.
[1038.96 --> 1042.10] You know, I'm sure there's going to be at least one tool in there that's going to help you out.
[1043.98 --> 1045.84] Linode.com slash SSH.
[1045.98 --> 1049.34] Go there to get a $100 60-day credit on your new Linode account.
[1049.86 --> 1052.20] Linode is the largest independent cloud provider.
[1052.60 --> 1056.06] Now, no matter what skill level you're at, what technology stack you use,
[1056.06 --> 1058.58] Linode can help your ideas come to life on the web.
[1058.78 --> 1060.74] If you run into any trouble getting set up,
[1060.90 --> 1064.80] Linode comes with amazing 24-7 customer support by phone or ticket,
[1065.30 --> 1068.22] along with hundreds of guides and tutorials to help you get started.
[1069.10 --> 1071.68] Linode has an easy-to-use and powerful cloud dashboard,
[1072.24 --> 1073.82] S3-compatible object storage,
[1074.02 --> 1075.04] cloud firewalls,
[1075.20 --> 1077.50] simple one-click application deployments,
[1078.00 --> 1078.92] super-fast networking,
[1079.14 --> 1080.20] and so much more.
[1081.06 --> 1084.42] Linode started in 2003 as one of the first companies in cloud computing,
[1084.42 --> 1087.38] three years before AWS and other enterprise providers.
[1087.88 --> 1090.70] They're independently owned and founded on a love for Linux.
[1091.06 --> 1092.02] And I tell you,
[1092.10 --> 1095.50] when you use Linode and you dig into some of their more advanced stuff,
[1096.34 --> 1096.92] by the way,
[1096.96 --> 1099.42] did you know they will let you boot your own ISOs?
[1099.56 --> 1100.12] Oh, yes.
[1100.36 --> 1104.02] If you want to run some esoteric thing from 20 years ago,
[1104.20 --> 1105.98] you can try and do that on Linode.
[1105.98 --> 1111.76] So go to linode.com slash SSH and get a $100 60-day credit on your new Linode account.
[1112.00 --> 1114.50] That's linode.com slash SSH.
[1116.80 --> 1123.24] One of the downsides of having a home lab and then a media server is I needed permission to buy it
[1123.24 --> 1125.46] and I needed permission to where to put it.
[1125.76 --> 1129.26] So the downside is it's next to my desk and it's in a small little hole.
[1129.26 --> 1135.16] And I have my three monitors and my MacBook and then I have my desktop for work.
[1136.04 --> 1138.40] And I have so many cables, you know,
[1138.44 --> 1142.44] and I'm constantly in a situation where when I need to hook up to the UNAZ,
[1142.56 --> 1144.14] I'm unplugging a cable.
[1144.46 --> 1146.18] Same thing with the ESXi box.
[1146.68 --> 1147.82] And I need a solution.
[1148.70 --> 1151.46] But I need a solution that really works.
[1151.58 --> 1156.22] I don't want the old style KVM where you're running all these cables and you're pushing a button.
[1156.22 --> 1161.52] You know, I want something that works with a modern monitor, HDMI, you know,
[1161.84 --> 1163.86] and something that just works.
[1164.48 --> 1168.68] Well, I was actually talking with Wendell about this the other night because he did a video on Pi KVM
[1168.68 --> 1170.44] and I sort of messaged him afterwards and said,
[1170.52 --> 1178.58] you know what would be really great is if I could take that single Pi 4 that I've got acting as a KVM unit
[1178.58 --> 1182.58] and control three or four systems with it.
[1182.58 --> 1186.62] I'm like, well, surely this should be possible with an HDMI switcher.
[1187.04 --> 1190.82] But I tried a couple in the past and they need you to actually be physically present
[1190.82 --> 1195.18] to push the button on the front of the damn thing to change the input from system one,
[1195.34 --> 1197.12] system two, three, four, whatever.
[1198.00 --> 1201.24] But the really nice thing about the unit that I've put in the show notes,
[1201.50 --> 1205.10] it's a four port HDMI switch.
[1205.24 --> 1206.00] It was about $60.
[1206.00 --> 1211.28] And this thing lets you use a keyboard shortcut to change inputs.
[1211.40 --> 1214.42] So I just press control, control, one, control, control, two,
[1214.74 --> 1218.12] and that changes the input on the KVM switch.
[1218.42 --> 1222.44] So how I've got it wired up is the HDMI goes from the server
[1222.44 --> 1228.28] out into the input of input one on the switch.
[1228.28 --> 1236.96] And then it comes from the switch output port into the capture port on the Raspberry Pi 4 through the CSI bridge.
[1237.34 --> 1239.74] Now, I've written a blog post about this, of course,
[1239.88 --> 1242.74] because that's what I seem to spend my spare time doing.
[1243.16 --> 1245.50] And I put a link to it in the show notes with a little diagram
[1245.50 --> 1249.46] in case that is a little confusing to follow by my talking.
[1249.64 --> 1252.90] But it takes about five minutes to wire up and put together.
[1253.96 --> 1255.82] And yeah, it just works, Morgan.
[1255.82 --> 1257.04] That's the really cool thing.
[1257.14 --> 1263.14] I can now switch between my server and my other server and my Raspberry Pi 3 that's doing DNS.
[1263.62 --> 1266.30] And they all just appear in the browser.
[1266.54 --> 1267.56] It's like magic.
[1268.10 --> 1269.26] Does it have the ability to record?
[1269.66 --> 1270.62] Can you record the output?
[1271.00 --> 1272.08] I don't think it does.
[1272.20 --> 1273.56] You can record macros.
[1273.62 --> 1277.44] So you can record different keyboard sequences and mouse sequences and that kind of thing.
[1277.66 --> 1280.16] But I don't think it will let you record the actual stream.
[1280.86 --> 1283.60] Although it's a WebRTC based system.
[1283.60 --> 1289.58] So I would wonder if there's some kind of a stream that we could hook into with VLC or something and maybe do it like that.
[1289.90 --> 1294.14] If you know the answer to that, again, write in and let us know at selfhosted.show slash contact.
[1295.26 --> 1299.18] Now, you're much more of a sysadmin than I am, I would say.
[1299.24 --> 1304.82] You've got a bit of a background working in all sorts of different places, cruise ships and hospitals and all sorts of places, right?
[1304.82 --> 1311.24] So you've probably run into email gateway issues when servers are trying to notify you that they've failed.
[1311.82 --> 1314.68] That's always been one of the fun parts about working in a data center.
[1315.22 --> 1318.10] Most of my employment has been with Exchange.
[1318.26 --> 1321.24] And you always run into these systems that just need an open relay.
[1322.06 --> 1325.12] As anybody knows, open relays are a little bit dangerous in the world.
[1325.12 --> 1332.90] So you're always looking for a good solution for, you know, an SMTP gateway that isn't expensive.
[1333.30 --> 1338.30] Or you can do what most people do and just copy their Gmail password around onto various boxes and have it connect that way.
[1338.38 --> 1340.26] I mean, what's the worst that can happen?
[1340.58 --> 1342.06] Yeah, when you're working from your home.
[1342.18 --> 1344.62] But, you know, what happens when you're working in a data center?
[1345.12 --> 1346.64] You're probably going to get that blocked.
[1346.92 --> 1347.74] Probably, yeah.
[1347.74 --> 1350.76] So I have an app pick for you that might tickle your fancy.
[1350.90 --> 1352.10] This one's called MailRise.
[1352.28 --> 1355.44] And this is an SMTP gateway for notifications.
[1355.80 --> 1359.40] Essentially, it plugs into an app we've mentioned before called AppRise.
[1359.86 --> 1367.70] So this MailRise application kind of sits in the middle, listening for emails, you know, syslog emails, whatever it might be.
[1367.78 --> 1370.40] Failures coming in from various different system services.
[1370.92 --> 1376.22] And when it receives the email, it reacts to that and then connects to AppRise.
[1376.22 --> 1382.06] So you can talk to any of the 60 plus notification services that AppRise supports.
[1382.30 --> 1385.68] So, you know, Telegram, Slack, Discord, you name it.
[1386.44 --> 1397.36] For those of you who are new to the show or possibly missed that episode, AppRise is a great tool that allows you to send notifications to almost all the most popular notification services today.
[1397.86 --> 1403.06] Think Telegram, Discord, Slack, you know, Reddit for those people who are really cool.
[1403.18 --> 1405.68] You know, it's a one notification library to rule them all.
[1406.22 --> 1413.46] And what's great is, is the tool MailRise, as Alex said, sits in front of that and is an SMTP gateway.
[1413.88 --> 1419.80] So there's a lot of applications that really don't have the ability to have that newer feature.
[1420.52 --> 1425.68] And MailRise gives you that by allowing you to send emails to the SMTP gateway and then you can send it off.
[1425.68 --> 1434.86] So when your laundry is done, you can send an email and post it on Reddit to let everybody know I now have clean clothes.
[1435.64 --> 1436.60] Hooray for that.
[1436.92 --> 1438.40] And that, you know, we live in the future.
[1438.76 --> 1442.90] We can monitor Morgan's laundry schedule via Reddit.
[1442.90 --> 1451.04] And speaking of the cloud, CloudFree.shop has some exciting news this week.
[1451.26 --> 1454.58] They have released their version 2 smart plugs.
[1454.70 --> 1455.46] So these are really cool.
[1455.56 --> 1457.56] They've got energy monitoring built right in.
[1458.16 --> 1461.10] And of course, they run TASMOTOR out of the box.
[1461.10 --> 1467.36] And, you know, the best thing about the company, it's a small family owned business run by one of our very own listeners.
[1467.60 --> 1472.26] Now you can go to CloudFree.shop and use the coupon code self-hosted so that they know that we sent you.
[1472.82 --> 1475.72] And you also get a dollar off per plug as well.
[1476.08 --> 1479.16] So that's CloudFree.shop with the coupon code self-hosted.
[1479.16 --> 1481.98] Mike writes to us,
[1481.98 --> 1483.72] Hey guys, love the show.
[1484.12 --> 1485.82] I'm a longtime Linux user and administrator.
[1486.26 --> 1489.46] But I have to admit, I've fallen a little behind on the whole container craze.
[1489.86 --> 1490.86] That's understandable, Mike.
[1491.36 --> 1492.96] I'm very comfortable with VMs.
[1493.22 --> 1494.84] They always made logical sense to me.
[1495.30 --> 1501.40] You have a virtual disk image, probably something with some metadata in it, and you get to run as a full-fledged system.
[1501.96 --> 1507.98] Something about the whole Docker runs X and it just magically happens without specifying any parameters
[1507.98 --> 1509.46] just struck me as creepy.
[1510.44 --> 1513.82] Regardless, I've used them a little bit inside of Firewall for LAN services,
[1514.16 --> 1517.08] but I'm wondering if there are best practices that either of you use.
[1517.44 --> 1522.42] For instance, when you're running multiple containers with persistence, where would you put the compose file?
[1522.84 --> 1525.96] Do you have any tips for organizing container volumes on CFS?
[1526.56 --> 1528.72] I've looked around and I haven't found any good articles.
[1528.72 --> 1534.54] Just lots of run Docker compose up and magic happens, which is disconcerting in a production environment to me.
[1534.54 --> 1538.24] That's the beautiful thing of Docker is it is just magic.
[1538.76 --> 1541.44] And for some people, that's exactly what they need.
[1541.80 --> 1550.72] You know, for your average person running an Unraid box or a small Raspberry Pi who's not working in this stuff day-to-day,
[1550.72 --> 1556.82] being able to do Docker run Plex or whatever it is without having to juggle half a dozen Bash scripts
[1556.82 --> 1560.12] and eight different versions of Java and all this kind of crap.
[1561.10 --> 1563.62] That's exactly where Docker is going to win.
[1564.28 --> 1571.80] Also, developers, if they're trying to do multiple different versions of an application development lifecycle all at once.
[1571.80 --> 1578.70] You know, I've got three different builds and I'm trying to figure out which one is causing my production systems to go down.
[1579.36 --> 1584.18] It's very easy to isolate and roll back a container that way because it's a declarative build.
[1585.84 --> 1595.12] But I understand there are some more old school people around that don't like that approach because it is a little more opaque than you've been used to.
[1595.12 --> 1605.86] However, I would say the reason it appears opaque is because perhaps you haven't quite taken the amount of time you need to to look into where that container originated from.
[1607.52 --> 1614.74] And sometimes you can go and look at the Docker file in the open source community and see basically a Docker file is like a recipe.
[1615.08 --> 1617.88] It's a glorified Bash script, essentially.
[1618.74 --> 1624.06] And say apt install this package, create this user, install this particular library.
[1624.06 --> 1628.66] And on the whole, those containers work pretty well.
[1629.30 --> 1636.32] And this is a problem that used to exist that I haven't seen really be a problem for quite some time now.
[1636.86 --> 1641.34] Is a lot of containers used to get uploaded to Docker Hub without a Docker file.
[1641.52 --> 1645.62] So you had to just trust that they weren't going to run a crypto miner on you or something like that.
[1645.70 --> 1648.00] And that problem largely seems to have gone away.
[1649.00 --> 1651.20] There are lots of different places you can go.
[1651.32 --> 1652.84] Linux server.io is one of them.
[1652.84 --> 1657.34] You can go to obviously Docker's website as well for some documentation there.
[1657.90 --> 1660.66] I'm going to say something that's probably not going to be popular.
[1661.14 --> 1664.12] But I don't think containers are solution for everything.
[1665.60 --> 1669.64] And it's Alex and I know containers are what puts roof over our heads.
[1670.00 --> 1674.28] And I will honestly tell you again, I don't think containers are the solution for everything.
[1674.28 --> 1681.26] You don't always need to build a server and install Docker or Podman and run a container on it.
[1681.60 --> 1687.80] Sometimes you can just install the Debian, the dev files or the RPM files and configure it yourself.
[1687.80 --> 1694.76] However, what containers do is it makes it easier to install services that work together.
[1695.30 --> 1703.60] You know, if you have a service that goes out and queries, it does a search for a file, injects that download file into the download service.
[1703.86 --> 1705.80] The download service then downloads the file.
[1705.80 --> 1710.18] Another service grabs the file, reads the metadata, processes it.
[1710.58 --> 1711.90] That's going to be really difficult.
[1712.56 --> 1716.02] How do we know that all three of those services require the same version of LibC?
[1716.42 --> 1721.54] How do we know that they require a specific version of Go, et cetera, et cetera?
[1721.86 --> 1725.74] You don't want to run into the situation where you're constantly looking at dependencies.
[1725.94 --> 1727.24] And that's what containers do.
[1727.24 --> 1735.06] So if you're doing a standalone box or standalone application, yeah, you know, doing the FAD install is perfectly fine.
[1735.36 --> 1742.38] But whenever you want to make sure that everything's going to work together and they're not going to butt heads, that's the real reason why containers were created.
[1742.94 --> 1754.54] Now, to answer your question about Docker compose files, the way I do it, and I'm sure Alex does it his way, is if the services need to speak to each other, they're in the same compose file.
[1754.54 --> 1758.26] I run 10 or 12 containers on my home lab.
[1758.74 --> 1763.02] And if the service does not need to talk to each other, it gets its own compose.
[1763.60 --> 1764.98] That's the way that I've always done it.
[1765.36 --> 1771.74] There's no reason for me to do a Docker compose up with AdGuard in the same exact compose as Plex.
[1772.22 --> 1773.40] They don't need to talk to each other.
[1773.54 --> 1775.12] They don't need to be on the same Docker network.
[1775.36 --> 1777.36] They can live in different Docker compose files.
[1778.16 --> 1782.06] I once had a colleague tell me that Docker was a solution looking for a problem.
[1782.06 --> 1793.86] Back then, this was like six years ago, I got really hot and steamy under the collar about this because Docker was the new hotness and I could see that it was going to solve all the world's problems.
[1794.74 --> 1798.18] And with a little bit of hindsight, I think I kind of agree with him in some ways.
[1798.96 --> 1805.96] It definitely has its use cases, but there are also places where VMs are probably better.
[1805.96 --> 1812.74] Now coming to another part of Mike's question, he asks about tips for organizing container volumes on ZFS.
[1813.60 --> 1816.14] I just create a data set per app, Mike.
[1816.36 --> 1817.26] It's as simple as that.
[1817.40 --> 1818.36] You can set quotas.
[1818.68 --> 1823.12] You can do snapshots, you know, using Jim Salter's Sanoid tool.
[1823.58 --> 1831.18] I have it set to do, I think, four hours worth of app data snapshots and then keep a daily snapshot and a monthly and an annual snapshot.
[1831.18 --> 1846.60] So the only thing to be aware of there is if you're doing something like InfluxDB or some kind of really chatty time series container or database that generates a lot of data, those snapshots will take up a lot of space because of how copy on write works.
[1846.78 --> 1851.18] So just make sure you're familiar with that concept before you dive into that one.
[1852.18 --> 1854.72] Ivan writes in, do you guys host your own email server?
[1855.10 --> 1856.46] And what are your thoughts on this?
[1857.26 --> 1859.04] This might be a good idea for the show.
[1859.04 --> 1863.14] I can tell you on a personal note, I love Gmail.
[1863.70 --> 1864.62] Why do I love Gmail?
[1865.54 --> 1866.28] It's easy.
[1866.80 --> 1867.96] They read my emails.
[1868.36 --> 1869.94] They tell me what I want to buy.
[1870.36 --> 1873.70] It works on my phone and they give me a bunch of storage.
[1874.78 --> 1879.46] But I can also tell you my private email is for my family only.
[1880.04 --> 1883.70] I don't give it out to anybody who isn't related to me by marriage or by blood.
[1884.58 --> 1887.26] And I run, therefore, my own email server.
[1887.26 --> 1888.96] It's been $5 a month.
[1889.10 --> 1889.92] It's on Linode.
[1890.32 --> 1891.92] I recommend everybody use it.
[1893.08 --> 1895.34] Do you, I want you to contact me for a job offer?
[1896.10 --> 1896.88] I have a Gmail.
[1897.32 --> 1899.08] Do I want to sign up for FPNL?
[1899.70 --> 1900.02] Gmail.
[1900.58 --> 1903.86] Do I want to send pictures to my mom, my kids?
[1904.54 --> 1905.16] Personal email.
[1905.16 --> 1907.66] I know that no one's ever going to get a hold of it.
[1908.56 --> 1911.30] I know that I'm not going to have to worry about getting spam.
[1912.14 --> 1914.96] Because, again, that's what Gmail is for.
[1915.20 --> 1916.08] It's for spam filtering.
[1916.98 --> 1919.28] My email that I host is for family only.
[1919.86 --> 1922.22] It's for things that I want for me and only my family.
[1923.04 --> 1925.30] And I recommend everybody to do the same.
[1925.64 --> 1927.14] Again, it's $5 a month.
[1927.76 --> 1928.92] Super easy to set up.
[1928.92 --> 1930.14] I like Gmail, too.
[1930.56 --> 1931.52] It just works.
[1932.38 --> 1935.08] So Thomas writes in with networking on his mind.
[1935.56 --> 1939.10] I wondered if either of you have touched VLANs on home networks.
[1939.44 --> 1941.94] I just got two Netgear Smart PoE switches.
[1942.08 --> 1944.28] And I'm thinking about how best to segment my network.
[1944.70 --> 1947.40] I've got a NUC with Fedora on it and a Windows laptop.
[1947.68 --> 1949.78] I've also got a NAS running some containers.
[1949.78 --> 1954.74] And I make use of WireGuard and Plex on there as well.
[1955.80 --> 1959.62] I've also got a Wi-Fi network that has a Google Nest and a pair of smart scales.
[1960.48 --> 1963.28] Thanks for an interesting show and inspiration for my home network.
[1963.58 --> 1963.86] Thomas.
[1964.56 --> 1968.10] VLANs and the home network is an interesting topic.
[1969.12 --> 1973.20] I think for 90 plus percentage of the world, you don't need them.
[1974.14 --> 1977.84] Until you start considering IoT devices and how insecure they are.
[1977.84 --> 1979.96] And who can get access to them.
[1980.86 --> 1987.04] And the second you have IoT devices that are a huge gaping security hole, you need to segment them.
[1987.24 --> 1988.36] And that's where VLANs come in.
[1988.66 --> 1989.96] And that's the number one thing I do.
[1990.58 --> 1993.64] My Wyze cameras, they're on separate VLAN and SSID.
[1994.88 --> 2000.96] My EcoVac Smart Vacuum on its own SSID and its own VLAN.
[2001.36 --> 2007.32] Because I want to segment anything on my network that is going to potentially open me up to attack.
[2008.08 --> 2012.16] The other reason why I use VLANs is, again, as I mentioned, I have a home lab.
[2012.64 --> 2013.94] I have all these services running.
[2014.36 --> 2017.16] Sometimes I have multiple THCP that I'm testing, etc.
[2017.56 --> 2020.42] I don't want that to conflict with my home network.
[2020.96 --> 2022.24] So that's where VLANs come in.
[2022.92 --> 2024.42] I use VLANs for DMZ.
[2024.62 --> 2027.20] Things that I want to expose outside my network.
[2027.90 --> 2029.04] VLANs are really about segmentation.
[2030.74 --> 2034.12] Take what you need that needs to talk to each other and put it on its own VLAN.
[2034.12 --> 2036.70] And that's the way that you should think about it.
[2037.34 --> 2041.76] Somehow I've managed to avoid the temptation of VLANs this whole time.
[2041.76 --> 2045.00] Because it requires a bit of extra hardware or a bit more advanced hardware.
[2045.14 --> 2047.90] So you've got to have a couple of switches that support VLANs.
[2048.18 --> 2053.74] And something to configure them at the router level as well.
[2054.14 --> 2055.76] So it's not just a plug and play thing.
[2055.80 --> 2057.80] You've got to have a bit more about you to do it.
[2057.80 --> 2062.82] And I've just kind of swept that one under the carpet and just opened up a bigger subnet
[2062.82 --> 2066.30] and put things in different subnets and just kind of prayed and hoped for the best, really.
[2067.02 --> 2068.02] That's been my approach.
[2069.02 --> 2075.04] I'm sure that most people who are running home labs, you know, they have Ubiquity, Microtech.
[2075.76 --> 2078.20] You know, a lot of the equipment that we already have can do it.
[2078.66 --> 2079.26] That's a good point.
[2079.68 --> 2085.08] I think the biggest issue is that people look at VLANs and they're a little hesitant
[2085.08 --> 2087.20] because they're afraid of what it can do.
[2087.84 --> 2092.62] I can definitely tell you I've gotten VLANs wrong and I've made a mess of things.
[2093.14 --> 2094.46] But that's what a home lab is for.
[2094.88 --> 2095.62] Break some eggs, eh?
[2096.70 --> 2097.14] All right.
[2097.16 --> 2099.18] Well, thank you very much for joining us this week, Morgan.
[2099.32 --> 2102.38] It was a very, very last minute that we had to call upon you.
[2102.80 --> 2106.12] Because we generally record the night before the show goes out on the Friday morning.
[2106.12 --> 2109.50] So we didn't have much time after Chris's laptop got flooded.
[2110.22 --> 2114.84] And also a big thank you to our members over at selfhosted.show.sre.
[2115.08 --> 2116.74] You can go over there and support the show.
[2116.88 --> 2121.72] And obviously we do appreciate that because it goes straight into the JB coffers to support
[2121.72 --> 2122.62] the network directly.
[2122.62 --> 2125.14] So we don't have to have as many sponsors on the shows.
[2125.80 --> 2127.92] Speaking of which, we have to thank A Cloud Guru.
[2128.18 --> 2130.56] And you can find them just about anywhere on social media.
[2130.72 --> 2135.64] They are slash A Cloud Guru on Facebook, YouTube, Twitter, just about everywhere.
[2136.64 --> 2140.72] So for all the different ways to go and get in touch with us, you can go to selfhosted.show
[2140.72 --> 2143.20] slash contact is the place to go to get in touch with us.
[2143.20 --> 2145.42] And you can find me on Twitter at ironicbadger.
[2146.10 --> 2148.94] And I don't have social media because I don't want to be cancelled.
[2152.14 --> 2156.04] Oh, well, I know you troll people on Reddit on a regular basis, but you can also find the
[2156.04 --> 2157.60] show at selfhosted.show.
[2158.00 --> 2159.10] Thanks for listening, everybody.
[2159.10 --> 2161.74] That was selfhosted.show slash 48.