Tiny PC, Huge Problems
Jul 20, 2025
Everything wrong with our homelabs, and how we're finally fixing them. Plus: two self-hosted apps you didn't know you needed.
Sponsored By:
- Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love.
- Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility.
- 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps.
- Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility.
Links:
- 💥 Gets Sats Quick and Easy with Strike
- 📻 LINUX Unplugged on Fountain.FM
- Home Assistant — Open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts.
- ODROID-H4 – ODROID — A powerful and versatile board that supports Intel's latest Alder Lake processors with AVX2 extensions. It features DDR5 memory, 4 SATA ports, dual BIOS, and up to 3 display outputs.
- Home Assistant Yellow
- UGREEN NASync DXP2800 2-Bay Desktop NAS
- MINISFORUM S100 Mini PC Stick
- GEEKOM Air12 Mini PC
- Nebula Quick Start
- Debugging with Nebula SSH commands
- Using Experimental Lighthouse DNS with Nebula
- Upgrading a Nebula network to IPv6 overlay addresses
- Using Dedicated Relays for Total Connectivity
- nebula NixOS Module
- norohind.nebula: — Ansible role to manage nebula vpn hosts
- dracut-nebula — dracut-nebula integrates the Nebula overlay networking tool (VPN, tunnel) into the initramfs
- nebula-gen: — Simple script to initialize a CA and quickly sign host keys and certificates for the Nebula VPN
- AndrewPaglusch/Nebula-Ansible-Role — Nebula VPN Overlay Network Installer With Ansible
- nebula-lighthouse-service — This server is a public Nebula VPN Lighthouse Service. You can use it in case you don’t have a publicly accessible server to run your own Nebula Lighthouse.
- nebula-vpn-helm — Helm chart for managing Nebula VPN
- vpn-dashboard-react-nebula — This project demonstrates a secure, lightweight, peer-to-peer VPN architecture using the Nebula overlay network integrated with a React-based front-end dashboard.
- ChrisLAS/bluenix — Build your own custom Universal Blue Image!
- Linkwarden — ⚡️⚡️⚡️ Self-hosted collaborative bookmark manager to collect, read, annotate, and fully preserve what matters, all in one place.
- Announcing Linkwarden 2.11
- Linkwarden Browser Extension
- neko — A self hosted virtual browser that runs in docker and uses WebRTC.
- Soltros-OS — My personal RPM-OStree based OS.
- Miniflux — Minimalist and Opinionated Feed Reader
- miniflux/v2 — Minimalist and opinionated feed reader
- [Bug]: "External link" should point to the audio file
- feat(rss): fallback to enclosure URL when entry URL is missing
- 5 Best Reference Management Tools for Linux in 2024
- Zotero — Your personal research assistant
- Aeon — The Linux Desktop for people who want to "get stuff done"
- winapps — Run Windows apps such as Microsoft Office/Adobe in Linux (Ubuntu/Fedora) and GNOME/KDE as if they were a part of the native OS, including Nautilus integration.
Transcript
WEBVTT
00:00:11.693 --> 00:00:16.393
Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris.
00:00:16.573 --> 00:00:17.313
My name is Wes.
00:00:17.513 --> 00:00:18.213
And my name is Brent.
00:00:18.913 --> 00:00:23.293
Hello, gentlemen. Well, coming up on the show today, there might be more than
00:00:23.293 --> 00:00:28.753
just a couple of things wrong with our home labs, but we do have a plan to fix them up.
00:00:28.873 --> 00:00:34.853
Today, we'll talk about what needs a fixin' and then what hardware might just do the job.
00:00:35.313 --> 00:00:40.913
Plus, we have two great self-hosted apps we've come across recently you didn't even know you needed.
00:00:40.913 --> 00:00:43.993
and then we're going to round the show out with some great shout outs and boosts
00:00:43.993 --> 00:00:48.313
and picks and more so before we go any further let's say time appropriate greetings
00:00:48.313 --> 00:00:53.033
to our virtual lug hello mumble room hey chris hey wes and hello brent hello
00:00:53.033 --> 00:00:54.973
mumble room thank you for joining us,
00:00:56.393 --> 00:00:58.353
boys i gotta break format for a second.
00:01:00.633 --> 00:01:02.553
Get out of here brent come on squeeze it.
00:01:02.553 --> 00:01:04.213
Oh it's what's with the.
00:01:04.213 --> 00:01:07.813
I'm a little i'm a little nervous is that all right is it okay yeah it is it's
00:01:07.813 --> 00:01:12.613
kind of a big deal uh we have something exciting and I don't know I don't want
00:01:12.613 --> 00:01:16.133
to blow it I don't want to blow it you know because this is something we've
00:01:16.133 --> 00:01:21.333
been thinking about for a while we have an opportunity to bring on a new sponsor,
00:01:22.113 --> 00:01:26.973
and this project was co-created by a listener of the show it's something we followed for years,
00:01:27.933 --> 00:01:31.853
and it's it's tremendously good and the company is great too they're building
00:01:31.853 --> 00:01:35.813
the company the right way you know they're not like hooked on that VC crack
00:01:35.813 --> 00:01:41.193
right they're doing in a smart sensible way and so i'm i don't know i'm just i don't want to mess it up.
00:01:41.193 --> 00:01:42.353
You got this.
00:01:42.353 --> 00:01:43.113
You think so uh-huh.
00:01:43.113 --> 00:01:43.893
Just be yourself.
00:01:43.893 --> 00:01:47.713
All right i'll give it a go so let me tell you go ahead what is it don't.
00:01:47.713 --> 00:01:49.273
Forget about the reverse code i believe.
00:01:49.273 --> 00:01:53.393
You got a tip for me i think what oh that's it that's your that's your motivation you've.
00:01:53.393 --> 00:01:59.333
Not royally messed it up previously i know this might be a big deal but i believe
00:01:59.333 --> 00:02:00.473
in you i think you got this.
00:02:00.473 --> 00:02:03.993
I feel like it's a big deal too because we're like the only podcast in the world
00:02:03.993 --> 00:02:08.473
yeah we're at wow you know i know that's a big deal actually.
00:02:08.473 --> 00:02:09.373
Okay now i'm feeling.
00:02:09.373 --> 00:02:13.973
Nervous i know they're reaching a new stage and it's just it's super exciting all right okay thanks.
00:02:13.973 --> 00:02:14.593
Guys you got that.
00:02:19.681 --> 00:02:25.841
Check out defined.net slash unplugged. Go check out Nebula, and they have managed
00:02:25.841 --> 00:02:27.301
Nebula from Defined Networking.
00:02:27.441 --> 00:02:33.801
It's a decentralized VPN built the right way on the open source Nebula platform that we love.
00:02:34.161 --> 00:02:39.861
And it is optimized for speed and efficiency where the nodes use less network
00:02:39.861 --> 00:02:43.841
activity, less battery life, and it's using industry-leading encryption.
00:02:43.841 --> 00:02:47.881
It's built on top of the noise protocol, which is super cool.
00:02:48.021 --> 00:02:52.221
So that's what they're using to exchange keys, do the symmetric encryption.
00:02:52.221 --> 00:02:54.861
And all of that's open source, independently audited.
00:02:55.601 --> 00:03:01.121
And unlike traditional VPNs, you can host what are called the lighthouses,
00:03:01.341 --> 00:03:04.521
if you like, or you can use their managed products. So you are in complete control.
00:03:05.141 --> 00:03:08.021
They built this for Slack back in the day.
00:03:08.641 --> 00:03:13.601
And it had to be great from the start because Slack has a global infrastructure, as you can imagine.
00:03:13.601 --> 00:03:16.441
they're across so many different data
00:03:16.441 --> 00:03:19.361
centers around the world and they need all of
00:03:19.361 --> 00:03:23.141
that stuff to be able to communicate and they're dealing with corporate
00:03:23.141 --> 00:03:28.321
private information so the requirements to get it right are astronomical could
00:03:28.321 --> 00:03:32.701
break the company if they get it wrong kind of stuff so nebula has been engineered
00:03:32.701 --> 00:03:37.221
for scale and performance from day one each host connects directly to each other
00:03:37.221 --> 00:03:39.881
and then it queries lighthouse nodes for routing information.
00:03:40.681 --> 00:03:43.221
Which you can host that yourself. That's a big deal.
00:03:43.441 --> 00:03:46.641
And these lightweight queries, they hit all available lighthouses simultaneously,
00:03:46.641 --> 00:03:48.821
so you have uninterrupted operation.
00:03:49.441 --> 00:03:53.441
Even if one of your nodes is down, if you have five other nodes online or two
00:03:53.441 --> 00:03:55.701
other nodes online, everything continues to hum right along.
00:03:56.961 --> 00:04:01.781
So if you go over to define.net slash unplugged, you can check out Nebula and
00:04:01.781 --> 00:04:06.001
manage Nebula for 100 hosts, absolutely free, no credit card required.
00:04:06.861 --> 00:04:12.041
Nothing matches Nebula's level of resilience, speed, and scalability.
00:04:12.201 --> 00:04:16.021
I am super thrilled that they're joining the Unplugged program because this
00:04:16.021 --> 00:04:21.061
is a project we've been watching since like almost the day it was announced.
00:04:22.121 --> 00:04:27.801
We very quickly brought the co-creator on to talk about it and have been tracking
00:04:27.801 --> 00:04:28.841
their progress ever since.
00:04:30.041 --> 00:04:33.161
I think you're going to love it. It redefines the VPN experience.
00:04:33.341 --> 00:04:37.621
Check it out at defined.net slash unplugged. Support the show.
00:04:38.841 --> 00:04:42.721
And it's great too because it's from the community. It's really something special.
00:04:42.841 --> 00:04:45.461
Defined.net slash unplugged.
00:04:47.361 --> 00:04:50.941
Do we have any last-minute housekeeping? I know you're going to be at the Knicks
00:04:50.941 --> 00:04:52.761
event attached to DEFCON.
00:04:52.921 --> 00:04:56.661
Yeah, that's right. Knicks Vegas. So if you go to DEFCON, reach out and see you there.
00:04:56.801 --> 00:04:58.881
That's coming up real soon, West Payne.
00:04:58.941 --> 00:05:00.061
That's right. Next month.
00:05:00.401 --> 00:05:01.401
Wow. Are you flying?
00:05:01.681 --> 00:05:01.861
Uh-huh.
00:05:02.361 --> 00:05:03.021
You got a hotel?
00:05:03.261 --> 00:05:03.641
I do.
00:05:03.821 --> 00:05:05.221
You're already done then.
00:05:05.341 --> 00:05:06.181
I know. Surprisingly organized.
00:05:06.201 --> 00:05:07.621
Now you just need to get the presentation done.
00:05:07.741 --> 00:05:08.081
That's right.
00:05:08.561 --> 00:05:12.041
Okay. All right. That's it, right? That's all we have for the housekeeping, I think? All right.
00:05:14.121 --> 00:05:19.141
All right. Let's do a home lab check-in. There's a lot that's been going on behind the scenes.
00:05:19.801 --> 00:05:22.801
Brent got his home assistant up and running again in the van.
00:05:23.681 --> 00:05:28.721
And he's actually been using some of the sensors to test different systems on the van. So I don't know.
00:05:29.181 --> 00:05:32.121
Walk us through. You got the system going again. And how are you using it, Brent?
00:05:32.641 --> 00:05:36.141
Yeah, we together got the system going. Oh, that feels like...
00:05:37.151 --> 00:05:42.731
months ago now. And the idea is to have a permanent home assistant set up in
00:05:42.731 --> 00:05:47.791
this crazy van that I somehow have in my possession that I'm putting lots of love into.
00:05:48.151 --> 00:05:56.071
And I wanted to do some testing on the fridge that is from the nineties and is still in this thing.
00:05:56.351 --> 00:05:59.631
And it's like this bizarre absorption fridge.
00:05:59.871 --> 00:06:02.691
I don't have any experience with those kinds of things. that can run propane
00:06:02.691 --> 00:06:06.411
and 12 volts and 120 volts. I just had so many mysteries.
00:06:06.571 --> 00:06:15.191
And I thought, what a perfect use case to use Home Assistant to track how good this thing is.
00:06:15.371 --> 00:06:18.371
Like, what does it do with temperatures? Can it get down to the right temperatures?
00:06:18.471 --> 00:06:19.951
Can it keep it there, et cetera, et cetera?
00:06:20.671 --> 00:06:24.651
It's worth noting that when you bring sensor data into Home Assistant,
00:06:24.831 --> 00:06:28.751
like a temperature sensor, it automatically graphs, charts, and logs that for
00:06:28.751 --> 00:06:33.971
you. So not only do you get real-time information, but you get historical data automatically.
00:06:34.291 --> 00:06:34.571
So great.
00:06:34.811 --> 00:06:39.891
And I'm, you know, compared to some who are listening very relatively new to
00:06:39.891 --> 00:06:43.851
Home Assistant, I feel slightly ashamed about that. But I have a project and it's getting me there.
00:06:44.311 --> 00:06:47.391
And I didn't realize this graphing was just built in.
00:06:47.591 --> 00:06:53.791
So such a win for me because I could just plug a couple sensors in and just
00:06:53.791 --> 00:06:55.291
get exactly what I needed right away.
00:06:56.071 --> 00:07:03.811
I did randomly meet a stranger with almost an identical van who offered to purchase this fridge off me.
00:07:03.971 --> 00:07:07.171
So I had extra incentive to be like, hey, this thing works really well.
00:07:07.331 --> 00:07:11.311
But I wanted to make sure that I was tracking this stuff in a way that,
00:07:11.411 --> 00:07:15.371
I don't know, I could provide a cool little graph of ambient temperature versus
00:07:15.371 --> 00:07:16.571
this fridge temperature.
00:07:16.811 --> 00:07:21.671
So having a little project like this is a perfect way to dive into Learning
00:07:21.671 --> 00:07:26.371
Home Assistant. You know, there's, I'm probably using 2% of what it can do,
00:07:26.591 --> 00:07:30.331
maybe less, but it's been super fun to get it up and running again.
00:07:30.851 --> 00:07:36.331
I feel like the power system in the van can maybe handle it a bit more.
00:07:36.331 --> 00:07:38.151
I was really quite nervous about that previously.
00:07:39.731 --> 00:07:45.051
But I think I can say I now have a home assistant setup that is going to be
00:07:45.051 --> 00:07:50.631
on full time 24 hours a day unless all my batteries die. So I think that's a big step for me.
00:07:51.051 --> 00:07:52.411
Yes. Yes, welcome to the club.
00:07:52.611 --> 00:07:56.431
Thank you. That's great. I feel like I have lots to learn.
00:07:56.591 --> 00:07:57.391
I'm not a long-time member, but I'm just, you know.
00:07:57.451 --> 00:08:00.091
Yeah, I'm so proud of you both recently getting Home Assistant going.
00:08:00.231 --> 00:08:02.091
So that's the good news in the Home Lab.
00:08:02.591 --> 00:08:06.211
Now, the bad news is you've got this project that's stalled out,
00:08:06.351 --> 00:08:08.271
in part because we ran out of time while I was visiting.
00:08:09.191 --> 00:08:13.931
And the idea is you want to create an off-site backup server that does essentially
00:08:13.931 --> 00:08:15.351
server-to-server replication.
00:08:16.271 --> 00:08:19.871
And I kind of want to hear more about that because I think it's still kind of
00:08:19.871 --> 00:08:21.791
up in the air exactly how to solve that problem.
00:08:21.891 --> 00:08:24.511
So tell us what you're trying to accomplish and then maybe we can kick around a few ideas.
00:08:24.691 --> 00:08:27.511
Yeah, I have talked about this on the network before, on Self-Hosted.
00:08:28.830 --> 00:08:36.110
I really just want to provide backups for my family and myself included that have an offsite option.
00:08:36.330 --> 00:08:40.750
So my parents have a super stable home environment, super stable internet,
00:08:40.750 --> 00:08:44.730
and we visit there a couple times a year.
00:08:44.930 --> 00:08:48.830
So that's a perfect location, but it's like thousands and thousands of kilometers
00:08:48.830 --> 00:08:50.250
away or miles, if you will.
00:08:50.710 --> 00:08:53.830
And so it's a perfect spot for a little like
00:08:53.830 --> 00:08:56.890
offsite backup at least for me and if
00:08:56.890 --> 00:08:59.770
that's a service i can provide you know throw up a
00:08:59.770 --> 00:09:02.990
machine that isn't uh an old laptop for their
00:09:02.990 --> 00:09:05.830
own backups that would give me peace of mind being their main support
00:09:05.830 --> 00:09:11.510
people and so i've had this dream if you'll put it because uh i haven't quite
00:09:11.510 --> 00:09:15.630
got there of having two near identical systems at least identical from a software
00:09:15.630 --> 00:09:19.770
perspective the hardware i thought oh having identical would be good too but
00:09:19.770 --> 00:09:24.270
i'm just at this point using old parts that i have for the computer on my end,
00:09:24.370 --> 00:09:28.590
and I bought what I'm hoping is a very stable platform to put on their end.
00:09:28.870 --> 00:09:36.190
So that includes an H4, Odroid, H4 Plus, and a couple new hard drives,
00:09:36.330 --> 00:09:37.790
20 terabytes that'll be mirrored.
00:09:37.910 --> 00:09:43.830
And the idea is to just be able for my family to back up to the local computers
00:09:43.830 --> 00:09:46.330
and those to just mirror to each other on a regular basis.
00:09:46.350 --> 00:09:48.790
It seems simple on the surface. Okay.
00:09:49.010 --> 00:09:53.990
So you want to mirror your data to that machine, but you also want to backup
00:09:53.990 --> 00:09:56.230
data from how many computers of your parents?
00:09:56.830 --> 00:10:02.390
Oh, they've got, you know, two, you know, one cell phone each and one laptop
00:10:02.390 --> 00:10:04.530
each. And I think that's about it.
00:10:05.090 --> 00:10:05.870
Cell phones.
00:10:06.110 --> 00:10:10.090
Well, why not? Why should you not backup cell phone data? Like photos is mostly
00:10:10.090 --> 00:10:11.570
the thing they care about, photos and videos.
00:10:11.690 --> 00:10:15.430
Well, what I'm mapping in my head now is three different backup systems.
00:10:15.430 --> 00:10:17.690
Because you have one to do the server-to-server replication,
00:10:17.690 --> 00:10:22.270
you have one to back up the computers, and then a separate one to back up the
00:10:22.270 --> 00:10:25.150
phones, right? I'm seeing this is three different systems you'd be managing.
00:10:25.350 --> 00:10:28.350
Yeah, the dream seems simple until you start implementing, and then all of a
00:10:28.350 --> 00:10:32.350
sudden it's like, oh, wait a second. This is multifaceted, isn't it?
00:10:33.050 --> 00:10:38.070
I feel like the server-to-server is probably the easiest because that you could
00:10:38.070 --> 00:10:40.250
just do like a ButterFS send-receive.
00:10:40.350 --> 00:10:40.450
True.
00:10:41.817 --> 00:10:46.357
And for the parents' backup, you do have some experience with,
00:10:46.517 --> 00:10:48.717
which backup software was it that you were using? Was it Borg?
00:10:48.957 --> 00:10:55.197
Yeah, I've got them set up currently with Borg, and I'm using Vorda as the main GUI interface.
00:10:55.517 --> 00:10:59.837
And they have, well, my father especially, have been pretty cozy with that.
00:11:00.357 --> 00:11:04.737
And it's been working well, and I don't think about it until I get on their
00:11:04.737 --> 00:11:08.037
systems every couple months, and it just seems to be working, which is great.
00:11:08.037 --> 00:11:13.997
So could that be just you set up borg backup on this new server and then reconfigure
00:11:13.997 --> 00:11:16.337
their clients to use that to back up to this that.
00:11:16.337 --> 00:11:22.697
Is at least for me at this point well tested well uh received on their part
00:11:22.697 --> 00:11:25.417
and like the super stable simple part of this backup system.
00:11:25.417 --> 00:11:30.477
Okay so desktops are solved what is your what is your thought on backing up
00:11:30.477 --> 00:11:32.977
i assume they have two android devices yeah.
00:11:32.977 --> 00:11:36.617
They have identical android devices and previously
00:11:36.617 --> 00:11:40.537
backups have been done manually by my father who's a bit tech savvy and he's
00:11:40.537 --> 00:11:46.497
using kd connect to uh just manually drag files he cares about he likes to sort
00:11:46.497 --> 00:11:50.777
all his photos like sit down one sunday morning with a coffee and move photos
00:11:50.777 --> 00:11:56.377
from both phones onto his laptop and then he just you know in vortigot just goes go and then.
00:11:56.377 --> 00:11:56.957
That backs.
00:11:56.957 --> 00:12:03.737
Up uh the android photos that are now on his laptop to the server so it's you know he's he's doing.
00:12:03.737 --> 00:12:09.477
That manually but it's happening oh let's pause let's pause let's zoom in as
00:12:09.477 --> 00:12:15.777
they say and double click what is it on the Android device they need backed up is it just photos I.
00:12:15.777 --> 00:12:21.257
Mean I think we in modern times should have the ability to back up all of our
00:12:21.257 --> 00:12:25.297
apps on Android but that is strangely difficult so if.
00:12:25.297 --> 00:12:26.557
You had a minimal set.
00:12:26.557 --> 00:12:27.157
Then I would.
00:12:27.157 --> 00:12:27.837
Say just.
00:12:27.837 --> 00:12:28.937
Photos and videos but.
00:12:28.937 --> 00:12:31.997
Why not if you've got like notes and contact information in
00:12:31.997 --> 00:12:35.357
Nextcloud already then it's just
00:12:35.357 --> 00:12:38.537
a matter of the photos and there yes
00:12:38.537 --> 00:12:41.197
you could use nextcloud obviously but it could be
00:12:41.197 --> 00:12:43.917
a great opportunity for image it's pretty
00:12:43.917 --> 00:12:47.457
straightforward to set up it does require some updates but it's pretty straightforward
00:12:47.457 --> 00:12:51.397
to set up um the experience is really great for the end user because the app
00:12:51.397 --> 00:12:55.957
is also a photo viewer that's really good great and fast uh but then there's
00:12:55.957 --> 00:13:00.017
also fun things you can do like you could set up an image kiosk and a few other
00:13:00.017 --> 00:13:02.237
ancillary containers or apps,
00:13:02.837 --> 00:13:06.817
that let you view different albums in image on different devices.
00:13:06.817 --> 00:13:10.477
So it could just be like on the computer, but it can also be on tablets. It can be on displays.
00:13:10.717 --> 00:13:13.657
There's fun things you can do with the pictures once you get them in image.
00:13:13.757 --> 00:13:16.717
Plus it also supports all the location information. It's private.
00:13:17.677 --> 00:13:21.097
Yeah. So it's, and it just works in the background, right? They take a photo
00:13:21.097 --> 00:13:23.237
and image uploads it when they're on wifi.
00:13:23.577 --> 00:13:26.457
Image could totally work. I had sync thing recommended to me about a hundred
00:13:26.457 --> 00:13:28.117
times to solve this problem.
00:13:28.277 --> 00:13:33.877
It does seem like it's a popular one in the audience, but it seems to me kind
00:13:33.877 --> 00:13:37.337
of like a blunt tool for the job, especially if you have everything else getting synced.
00:13:38.243 --> 00:13:42.603
I think the easier workflow is you get the new phone. Unfortunately,
00:13:42.603 --> 00:13:44.883
you set it up, you sign in or whatever the crap you got to do.
00:13:45.523 --> 00:13:48.423
And then you just sync your stuff, right? I mean, it's just what,
00:13:48.503 --> 00:13:49.883
I don't know, just seems to be.
00:13:50.463 --> 00:13:55.183
I'd be interested in tips from the audience on utilities that would let you
00:13:55.183 --> 00:14:02.383
do like an image backup or some kind of full backup to a Samba share or some kind of local NAS.
00:14:02.783 --> 00:14:05.363
If the audience knows, boost in or email us and let us know.
00:14:05.363 --> 00:14:10.663
I find it wild that this is not a standard thing. Wild. Once you get used to
00:14:10.663 --> 00:14:12.943
Linux computers, like, come on, we don't have this?
00:14:12.943 --> 00:14:15.943
This i mean it seems if you can get the hardware running
00:14:15.943 --> 00:14:18.623
it seems like a pretty easy thing to at least get
00:14:18.623 --> 00:14:22.343
the server to server backup going on your lan maybe
00:14:22.343 --> 00:14:25.403
using like some sort of you know like a nebula vpn
00:14:25.403 --> 00:14:28.063
or something to make that work so they're
00:14:28.063 --> 00:14:31.463
talking to each other over that vpn on your lan and
00:14:31.463 --> 00:14:35.043
then get that syncing while you're you know node to node right there so you
00:14:35.043 --> 00:14:39.283
do the bulk of the syncing first then ship it off but i don't know about the
00:14:39.283 --> 00:14:42.423
borg stuff like we'd have to talk more about that but I think that seems pretty
00:14:42.423 --> 00:14:46.683
achievable if they've already got a workflow then later on it would just be
00:14:46.683 --> 00:14:49.183
moving them over to image you could even do that later,
00:14:49.803 --> 00:14:52.243
as a phase two staged rollout mm-hmm,
00:14:53.080 --> 00:14:53.680
That might be it.
00:14:53.840 --> 00:14:58.840
Yeah, I like the image idea. I hadn't even considered that. I think that is a wonderful idea.
00:14:59.060 --> 00:15:02.400
The hardware is an upgrade to what they're currently using, which is an ancient
00:15:02.400 --> 00:15:07.460
T61 laptop that my father used to use way back.
00:15:07.600 --> 00:15:11.180
And yeah, that fan has been replaced several times. But it's still kicking.
00:15:11.400 --> 00:15:12.980
Are you doing any jellyfin on this thing?
00:15:13.200 --> 00:15:17.260
Not yet. Mostly because the hardware hasn't been up to the task.
00:15:17.800 --> 00:15:19.040
And that's where I feel like.
00:15:19.220 --> 00:15:20.420
This H4 is no problem.
00:15:20.480 --> 00:15:23.420
That's where image wasn't really an option previously. either
00:15:23.420 --> 00:15:26.340
but because of the hardware upgrade i feel
00:15:26.340 --> 00:15:29.300