Datasets:
willtheorangeguy
/
2022-SelfHosted-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
7
369
[2579.82 --> 2584.64] The best thing is like every device gets a network IP that is assigned to it and remains
[2584.64 --> 2589.68] consistent no matter where I'm at, no matter where I'm at in the country, all of my bookmarks
[2589.68 --> 2590.48] still work.
[2590.48 --> 2594.18] And Tailscale works with whatever your single sign-on provider is.
[2594.30 --> 2598.36] So if you want to use a single sign-on provider you already have with two-factor authentication,
[2598.84 --> 2599.90] that's going to work too.
[2600.56 --> 2601.96] You're going to be really impressed.
[2602.32 --> 2606.66] You'll probably get it going in a matter of minutes, regardless of your device or operating
[2606.66 --> 2607.06] system.
[2607.56 --> 2608.78] So go try it for yourself.
[2609.32 --> 2615.80] Protect your data with WireGuard Scale encryption and build a flat mesh network in seconds for free,
[2615.80 --> 2622.68] up to 20 devices, and you support the show when you go to tailscale.com slash self-hosted.
[2622.96 --> 2624.50] Go see why I love it so much.
[2624.72 --> 2628.76] It's going to change how you think about networking, and it's going to change how you can get access
[2628.76 --> 2631.56] to your data, and it's going to help keep you private and secure.
[2632.20 --> 2634.72] Tailscale.com slash self-hosted.
[2634.72 --> 2639.64] I'm still finding it weird that I'm in the same room as you two gentlemen.
[2639.84 --> 2641.04] This is nice.
[2641.12 --> 2642.00] I could get used to this.
[2642.20 --> 2646.80] We need to get like six more sponsors on every episode, and we just do every episode like
[2646.80 --> 2647.10] this.
[2647.28 --> 2647.54] Yeah.
[2647.98 --> 2648.82] We just pay for the flights.
[2648.96 --> 2650.22] Turn it into an LTT video.
[2650.40 --> 2654.14] Probably need a time machine too, to make that five-hour flight each way work.
[2654.28 --> 2656.80] Well, think about the automations we could do in the JB Private Jet.
[2657.06 --> 2657.42] Right.
[2657.60 --> 2658.46] Oh, that's where we go.
[2658.68 --> 2659.24] We need a jet.
[2659.32 --> 2659.88] We need one.
[2660.32 --> 2661.98] We keep flying west.
[2662.04 --> 2664.20] If we always fly west, then it will be fine.
[2664.26 --> 2665.16] We can make that work, right?
[2665.16 --> 2665.42] Oh, yeah.
[2665.50 --> 2666.90] I think because it's a globe, that's how it works.
[2667.12 --> 2667.34] Yeah.
[2667.34 --> 2668.34] Or is it east?
[2668.60 --> 2668.96] I don't know.
[2669.14 --> 2671.28] I mean, you just go one direction long enough.
[2671.30 --> 2671.78] It doesn't matter.
[2672.72 --> 2673.02] True.
[2674.06 --> 2675.82] So we have some feedback from Josh today.
[2676.16 --> 2677.32] Hi, Chris and Alex.
[2677.32 --> 2678.58] Thank you for the podcast.
[2678.76 --> 2683.14] I've recently been starting out in the world of self-hosting, and I've listened to every episode.
[2683.60 --> 2686.64] I am fortunate enough to be able to keep something small at my dad's house.
[2686.64 --> 2693.12] Now, given the chat on a previous episode, I've been looking towards an SBC, single board computer, based NAS.
[2693.92 --> 2698.56] Hopefully, this will consume very little power and should be able to cope with semi-regular incremental backups.
[2698.96 --> 2702.36] I'm thinking about something maybe in the weekly backup range.
[2703.30 --> 2711.02] There seems to be mixed advice about this online, including a lot of feedback suggesting that using an SBC is flawed as these disks will be hanging off the USB bus.
[2711.02 --> 2714.06] Do you feel this is something to be concerned about?
[2714.64 --> 2719.48] Or is this an acceptable compromise to reach the low power and small form factor solution I'm looking for?
[2719.48 --> 2722.78] I'm hearing low power a couple of times in here.
[2723.10 --> 2726.54] So it sounds like that is a primary concern for Josh here.
[2726.94 --> 2729.54] And so you probably are going down the right path, Josh.
[2729.58 --> 2734.58] But I wonder, have you considered the magnificent world of the Compute Module 4?
[2734.96 --> 2738.84] Because there are carrier boards where you can get PCI slots.
[2739.30 --> 2740.56] You can get a SATA.
[2740.56 --> 2745.94] You can have an EMMC, which is much superior to an SD card for a boot drive.
[2746.60 --> 2757.48] And so, you know, if I were going to build a NAS today based around some sort of SBC, it would take a really, really, really strong argument for me to consider anything else but the CM4.
[2757.92 --> 2763.78] Simply because nothing else has the network effect, the community effect, the software support.
[2764.08 --> 2768.34] And when you're building something that you want to run solid and run for a while, that matters.
[2768.34 --> 2773.42] You know, there may be faster SBCs out there, ones that already have PCI slots, for example.
[2774.40 --> 2781.30] But the CM4, the Compute Module 4, combined with a carrier board that can accommodate you, in my experience, is such a solid setup.
[2781.40 --> 2782.76] It's really hard to argue against that.
[2783.02 --> 2783.62] What do you think, Alex?
[2784.64 --> 2786.66] It's just a backup, right?
[2786.74 --> 2787.32] Yeah, true.
[2787.54 --> 2792.68] If you have something hanging off the USB bus and it fails, it shouldn't matter.
[2792.90 --> 2793.74] It is your backup.
[2793.74 --> 2804.92] As long as you have monitoring in place to let you know that something's gone south, you know, the backup is the perfect place to experiment and do something that's slightly more risky.
[2805.86 --> 2810.12] So long as maybe, I don't know, like maybe have two.
[2812.04 --> 2813.38] You know, three, two, one.
[2813.38 --> 2816.32] Yeah, and the prices, you probably could, too, right?
[2816.36 --> 2818.10] I mean, the most expensive thing here is going to be the storage.
[2818.80 --> 2820.18] That's going to be the most expensive thing.
[2820.66 --> 2822.06] So let us know what you do, Josh.
[2822.14 --> 2824.84] Because, you know, sometimes we get these questions, but we don't always get the follow-ups.
[2824.98 --> 2826.42] So we'd love to know.
[2826.98 --> 2828.02] Kevin writes in,
[2828.02 --> 2830.58] I have five or so VPS servers on Linode.
[2831.24 --> 2835.58] I have one domain name at my DNS provider with subdomains pointing to each server.
[2835.86 --> 2837.32] It's great for SSH access.
[2837.78 --> 2839.94] I want to run a web server from each one of them.
[2840.30 --> 2846.46] I've obtained a wildcard TLS certificate from Let's Encrypt on the first server using Lego.
[2846.94 --> 2850.80] I've confirmed the wildcard cert works on the first server where Lego is installed.
[2851.20 --> 2855.14] It serves a new page with HTTPS on the subdomain with that cert.
[2855.14 --> 2859.78] I then set a cron job to run Lego and renew that cert monthly.
[2860.62 --> 2867.82] What is the safest way, though, to propagate that wildcard cert from one server to all four other servers automatically each month?
[2868.04 --> 2869.10] I've got WireGuard.
[2869.22 --> 2870.04] I've got SSH.
[2870.74 --> 2871.60] Just not keys.
[2871.70 --> 2874.00] I've got Ansible Vault I could potentially use.
[2875.28 --> 2878.72] I've thought about doing these with cron jobs that copy these over SSH.
[2878.78 --> 2880.94] But how do I automate communicating between the servers?
[2880.94 --> 2886.92] How do I protect the SSH keys, the SSH certificate, and other connection credentials and move all of this around?
[2888.14 --> 2891.76] This feels like one of those where there's like a thousand ways you could solve this problem.
[2892.68 --> 2900.26] You could do it the proper way, the established way, and move the certificates around between the servers.
[2900.70 --> 2903.34] But we were talking about this as a group before we recorded.
[2903.92 --> 2906.08] And Wes, you came up with an interesting idea.