TRANSKRYPCJA 🔗
1
00:00:11,417 --> 00:00:16,197
Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris.
2
00:00:16,377 --> 00:00:17,017
My name is Wes.
3
00:00:17,237 --> 00:00:18,077
And my name is Jeff.
4
00:00:18,697 --> 00:00:22,837
Hello, gentlemen. Coming up on the show this week, one piehole,
5
00:00:22,997 --> 00:00:26,857
two VPNs, and zero public exposure. I'm pretty proud of this one.
6
00:00:27,197 --> 00:00:30,997
Then, it's our pitch to ditch your GUI-only monitoring system,
7
00:00:31,137 --> 00:00:34,797
and why we rolled out Prometheus and Grafana.
8
00:00:35,037 --> 00:00:37,417
And then we're going to round the show out with some great boosts,
9
00:00:37,577 --> 00:00:40,157
some great picks, and a whole lot more. So before we go any further,
10
00:00:40,357 --> 00:00:43,137
time-appropriate greetings to our virtual lug. Hello, Mumble Room.
11
00:00:43,677 --> 00:00:45,817
Hello, Wes, and hello, Brent.
12
00:00:46,137 --> 00:00:50,217
Hi. Yeah, you can join us in the Mumble Room or at jblive.tv.
13
00:00:50,837 --> 00:00:55,617
Make it a Tuesday on a Sunday. We have the times at jupiterbroadcasting.com slash calendar.
14
00:00:55,817 --> 00:00:59,197
And a big good morning to our friends over at Defined Networking.
15
00:00:59,497 --> 00:01:03,797
Go check out Nebula VPN. They have a full managed product, 100 devices,
16
00:01:04,017 --> 00:01:04,937
no credit card required.
17
00:01:05,097 --> 00:01:08,037
Support the show, defined.net slash unplugged.
18
00:01:08,517 --> 00:01:11,777
It is a great service. And, you know, when I've thought about it a lot,
19
00:01:11,837 --> 00:01:15,697
I talk about how Slack used it and they launched it in 2017 to build out the
20
00:01:15,697 --> 00:01:18,697
security around the Slack global empire. And I talk about how Rivian uses it
21
00:01:18,697 --> 00:01:21,677
for real time analytics for the cars to do securely on the road.
22
00:01:22,805 --> 00:01:27,825
And those are all really big-scale projects. But recently, I've appreciated
23
00:01:27,825 --> 00:01:33,045
how great Nebula is on a 1, 2, 3 node network.
24
00:01:33,205 --> 00:01:39,705
And the fact that I can set up a on-demand mesh network that has name resolution
25
00:01:39,705 --> 00:01:41,305
and everything. We'll talk more about this.
26
00:01:42,045 --> 00:01:47,085
And there's no big tech login. There's no third-party hosted admin dashboard.
27
00:01:48,105 --> 00:01:52,825
Nothing like that. It's just two machines using cryptographic keys talking to each other.
28
00:01:52,945 --> 00:01:54,245
It's just a couple of text files, really.
29
00:01:54,845 --> 00:02:00,265
It's so powerful for small home lab stuff, and it's so scalable to massive enterprise stuff.
30
00:02:00,405 --> 00:02:03,525
And you can try it out with our fully managed product and support the show by
31
00:02:03,525 --> 00:02:06,485
going to define.net slash unplugged.
32
00:02:06,545 --> 00:02:10,525
You're going to like it a lot. And I'll
Load full transcript
tell you, I've been using it on extremely
33
00:02:10,525 --> 00:02:12,145
limited bandwidth connections.
34
00:02:12,745 --> 00:02:16,265
And it's so much better, and it's so much more resource sensitive.
35
00:02:16,445 --> 00:02:22,705
It's way lighter. It's way lighter. Check it out, define.net slash Nebula.
36
00:02:22,945 --> 00:02:25,825
And thank you to Define for sponsoring the Unplugged program.
37
00:02:28,525 --> 00:02:34,245
All right, you know we've got to mention it. Planet Nix and Scale23x are 39 days away.
38
00:02:35,125 --> 00:02:39,665
That means 33 days until Brent needs to be going down the road, at least.
39
00:02:40,105 --> 00:02:41,445
Let's just round that to 30.
40
00:02:41,725 --> 00:02:45,505
And six, I believe, or five, actually, more Linux Unplugs, maybe,
41
00:02:45,605 --> 00:02:47,445
until we need to be on the road ourselves.
42
00:02:47,605 --> 00:02:47,905
Wow.
43
00:02:47,905 --> 00:02:48,625
So it's coming up.
44
00:02:48,825 --> 00:02:50,545
I think we better get in the Nixie mood.
45
00:02:50,825 --> 00:02:54,465
Yeah, and I am really looking forward. Planet Nix has a theme this year.
46
00:02:54,605 --> 00:02:55,925
It's where builders come together.
47
00:02:56,225 --> 00:03:00,465
And our Nix coverage is supported again by Phlox, who's focused on making reproducible
48
00:03:00,465 --> 00:03:02,065
dev environments actually usable.
49
00:03:02,125 --> 00:03:04,445
And it's a fantastic tool.
50
00:03:04,605 --> 00:03:10,085
So check out Phlox and come see us at Scale and Planet Nix. You do need to register at Scale.
51
00:03:10,765 --> 00:03:14,525
And you can take 40% off that registration with our promo code UNPLG,
52
00:03:14,725 --> 00:03:20,105
U-N-P-L-G. and we'd love to see you there. One other item.
53
00:03:22,031 --> 00:03:26,391
The meetup page is now live. The details are not yet locked in.
54
00:03:26,531 --> 00:03:28,571
The date, time, location likely to change.
55
00:03:29,531 --> 00:03:32,131
But you can join the meetup and you'll be the first to get updates.
56
00:03:32,431 --> 00:03:37,571
And if you are intending to join us at the meetup, please consider signing up
57
00:03:37,571 --> 00:03:39,931
for the meetup. Please. We'd love to see you there.
58
00:03:40,251 --> 00:03:43,811
Last time we had about 80 more people than we expected. Great problem to have.
59
00:03:44,571 --> 00:03:48,071
It was very stressful on the restaurant staff. And they thankfully could open
60
00:03:48,071 --> 00:03:51,871
up. They had to open up another wing for us, which they were able to do.
61
00:03:52,491 --> 00:03:55,651
but this time we wanted to give them a great heads up. So if you're planning
62
00:03:55,651 --> 00:03:58,191
to make it and I want to bring a guest, there's room for that too.
63
00:03:58,531 --> 00:04:00,391
Just let us know. And we'll plan accordingly.
64
00:04:00,871 --> 00:04:04,511
Meetup.com slash Jupiter broadcasting link in the show notes to the direct meetup.
65
00:04:05,191
--> 00:04:07,411
We'd really appreciate it. If you could make it, if you're in the area,
66
00:04:07,991 --> 00:04:10,751
even if you can't go to the event, you're welcome to join us at the meetup.
67
00:04:11,431 --> 00:04:16,451
We did get one submission for that. I saw for a swag idea that we could hopefully
68
00:04:16,451 --> 00:04:20,531
have together for scale and Linux fest. It was a nice one.
69
00:04:20,931 --> 00:04:24,091
I'll show it to you boys after the show but I'd like to see a few more send
70
00:04:24,091 --> 00:04:27,431
them in to unplugged at jupiterbroadcasting.com or tag Wes in Matrix,
71
00:04:29,191 --> 00:04:33,451
and let us know we'll try to put one together pretty soon so we all have a uniform
72
00:04:33,451 --> 00:04:37,951
that we can identify each other with and have easy conversation hey I know you
73
00:04:37,951 --> 00:04:39,331
you listen to the show are.
74
00:04:39,331 --> 00:04:40,031
We getting hats.
75
00:04:41,411 --> 00:04:44,671
Ooh you know I'm a hat guy now you know I'm a hat guy now that's right,
76
00:04:47,918 --> 00:04:52,478
Well, what is, in a name, gentlemen, in short, convenience, right?
77
00:04:52,838 --> 00:04:56,478
When you set up your home lab or your enterprise network, whatever it is,
78
00:04:56,578 --> 00:05:00,058
it is eventually inevitable that you need good name resolution.
79
00:05:00,338 --> 00:05:04,378
I suspect for you there might be a spousal approval factor in the mix for that too.
80
00:05:04,598 --> 00:05:08,058
Yeah, and also just a memory factor. It gets hard to remember,
81
00:05:08,118 --> 00:05:10,418
especially the mesh network VPNs and the LAN IPs.
82
00:05:11,298 --> 00:05:14,318
And, of course, I have to go and make it hard, and I have multiple mesh networks
83
00:05:14,318 --> 00:05:16,578
now, multiple locations.
84
00:05:17,618 --> 00:05:22,118
some behind double carrier grade NAT a couple of them behind double carrier
85
00:05:22,118 --> 00:05:27,658
grade NAT so I had to go and make it hard on myself and I want sensible name
86
00:05:27,658 --> 00:05:32,418
resolution that works on the LAN and works across the various mesh networks,
87
00:05:33,538 --> 00:05:38,598
so I can just you know connect by machine name to all of them and then I need
88
00:05:38,598 --> 00:05:43,318
something also that does fast forwarding out to the internet and then can cache
89
00:05:43,318 --> 00:05:44,938
that so then future queries are faster.
90
00:05:44,938 --> 00:05:47,458
And then was it something you wanted to, like, I don't know,
91
00:05:47,518 --> 00:05:51,318
do you have some of these services that depend on other services in a way where,
92
00:05:51,318 --> 00:05:53,198
like, DNS is how they find each other?
93
00:05:53,638 --> 00:05:55,938
Yeah, and there's a lot of things I've set up are just by name now.
94
00:05:57,198 --> 00:06:03,478
So, you know, I had a basic pie hole going on my tail net, and I had a basic pie hole going on my LAN.
95
00:06:04,578 --> 00:06:06,078
But then we set up my wife's clinic.
96
00:06:06,258 --> 00:06:12,338
And was the tail net pie hole was running, like, as a container on a VPS or something?
97
00:06:12,338 --> 00:06:16,438
Yeah, and it just only had an interface on the Tailnet. So it was just acting
98
00:06:16,438 --> 00:06:17,738
as name resolution for the Tailnet.
99
00:06:17,858 --> 00:06:21,378
And then I kind of combined that with MagicDNS and sort of had the whole Tailnet thing solved.
100
00:06:21,638 --> 00:06:23,678
Then I had to go set up another network and all of that.
101
00:06:24,298 --> 00:06:28,458
And I also just kind of wanted to take another look at this and see if I couldn't do this better.
102
00:06:28,938 --> 00:06:33,998
But when I had set it up for the Tailnet only on the VPN, I took a shortcut.
103
00:06:34,698 --> 00:06:38,678
And instead of having to worry about exposing a pie hole to the internet...
104
00:06:40,126 --> 00:06:43,266
I just only bound it to the tail net interface.
105
00:06:44,306 --> 00:06:49,106
So I didn't have to worry about public IP and the internet, you know,
106
00:06:49,186 --> 00:06:52,146
banging on my pie hole server that's on a VPS because it couldn't talk to it.
107
00:06:52,506 --> 00:06:56,306
But if I wanted to make this pie hole usable across multiple mesh networks,
108
00:06:56,646 --> 00:07:00,626
it meant undoing that sort of convenience in security I had and coming up with
109
00:07:00,626 --> 00:07:03,386
a better security architecture to go across multiple networks.
110
00:07:04,886 --> 00:07:08,366
That's where it got a little kind of more complicated because
111
00:07:08,366 --> 00:07:12,006
i went from the easy way to the hard way and so
112
00:07:12,006 --> 00:07:14,726
there's multiple uh layers i kind of took
113
00:07:14,726 --> 00:07:18,126
to this and i kind of like to hear your guys's feedback on this so the first
114
00:07:18,126 --> 00:07:23,726
step i took is i wasn't sure if this is the right call but i essentially put
115
00:07:23,726 --> 00:07:29,886
the pie hole container on host networking so it could see all the interfaces
116
00:07:29,886 --> 00:07:32,406
And then in the configuration,
117
00:07:32,866 --> 00:07:38,126
I limited by application configuration to only bind to the tail net and the
118
00:07:38,126 --> 00:07:41,706
Nebula VPN interfaces and to not bind to the WAN interface.
119
00:07:42,026 --> 00:07:44,846
So at an application configuration layer, I did that.
120
00:07:45,126 --> 00:07:51,906
And then at another layer, I also set up ACLs with IP tables,
121
00:07:52,166 --> 00:07:55,746
just real basic IP tables that blocks all traffic on port 53.
122
00:07:55,746 --> 00:07:59,486
So like just in case, you know, for a moment, like when PyHole's starting up,
123
00:07:59,646 --> 00:08:03,166
if for a brief moment it bound to port 53 on the WAN interface,
124
00:08:03,566 --> 00:08:06,826
this would essentially prevent that from happening. Or if I make a config change
125
00:08:06,826 --> 00:08:10,566
mistake in the future, it prevents it from exposing it to the public internet.
126
00:08:11,706 --> 00:08:13,906
And so that's sort of the...
127
00:08:15,147 --> 00:08:18,507
multi-layer approach in a way and then all the communications just happening
128
00:08:18,507 --> 00:08:22,687
over the mesh vpns i'm not communicating with the buy hole at all no admin interface
129
00:08:22,687 --> 00:08:24,207
nothing over any public interface,
130
00:08:25,087 --> 00:08:29,707
how do you feel i did is that too risky would you brent would you be comfortable
131
00:08:29,707 --> 00:08:31,747
with that deployment i suppose i.
132
00:08:31,747 --> 00:08:37,807
Mean to me that feels probably more fine than anything that i've probably deployed
133
00:08:37,807 --> 00:08:43,167
in the past so it seems okay but really i'm not the pro or anything like that
134
00:08:43,167 --> 00:08:48,147
but But what I'm getting from you is that this is upping your peace of mind with this.
135
00:08:48,287 --> 00:08:51,387
But there's also some hesitation. So I'm curious to hear what Wes has to say.
136
00:08:51,887 --> 00:08:54,907
I do think it seems totally reasonable. You could, you know,
137
00:08:55,447 --> 00:08:58,587
get with the times and use NF tables already. No, I'm just kidding.
138
00:08:59,047 --> 00:09:02,487
I did actually, that actually considered, I was like, ah, this is what I know. But yeah.
139
00:09:02,687 --> 00:09:08,187
I think from background discussions, I picked up maybe you were using a sidecar before?
140
00:09:08,467 --> 00:09:09,467
A tailscale sidecar, yeah.
141
00:09:09,987 --> 00:09:14,087
So I think maybe in like another version, if you were going like fully,
142
00:09:14,107 --> 00:09:19,767
you know, application mesh native could be to just double down on the sidecar.
143
00:09:19,847 --> 00:09:20,667
Do a nebulous sidecar.
144
00:09:20,787 --> 00:09:24,247
Yeah. Like have it serve those two interfaces just in its own containerized
145
00:09:24,247 --> 00:09:25,127
networking environment.
146
00:09:25,127 --> 00:09:25,707
I like that.
147
00:09:25,847 --> 00:09:28,827
Where things might get more complicated depending on exactly what you want and
148
00:09:28,827 --> 00:09:32,387
convenience, et cetera. What matters to you is what you're doing with that host.
149
00:09:32,567 --> 00:09:36,367
And is that host then wanting to query the pie hole? And are you going to let
150
00:09:36,367 --> 00:09:40,027
that happen over local host? Or in this scenario, you'd either need to replumb
151
00:09:40,027 --> 00:09:43,687
stuff and forward it or rely on it only querying it over the mesh,
152
00:09:43,727 --> 00:09:45,627
which would probably be fine, but maybe you don't want to do that.
153
00:09:45,767 --> 00:09:51,527
The host is also on the tail net. So there's that too. But yeah, that is a tricky part.
154
00:09:52,547 --> 00:09:57,147
Technically, the host OS can't talk to it over the network, which hasn't been an issue yet.
155
00:09:58,383 --> 00:10:01,023
But so that's the basic, that's the core network setup, okay?
156
00:10:01,163 --> 00:10:05,103
And then what I decided to do was I turned off the tailscale MagicDNS stuff
157
00:10:05,103 --> 00:10:12,923
and didn't like the results because I do not have DNS entries for every machine on my tail net.
158
00:10:13,023 --> 00:10:16,643
And that's what MagicDNS was solving for me. So my sort of compromise solution
159
00:10:16,643 --> 00:10:24,143
was I re-enabled MagicDNS and then I added this pie hole as the upstream DNS server for MagicDNS.
160
00:10:24,503 --> 00:10:26,903
And I think that worked seemingly pretty well.
161
00:10:27,403 --> 00:10:29,303
and then I enabled the DNS.
162
00:10:29,503 --> 00:10:33,003
Right, so in that setup, TailScale will answer sort of right away for the TailScale
163
00:10:33,003 --> 00:10:36,063
host and then forward to your setup for anything it doesn't know about where
164
00:10:36,063 --> 00:10:37,403
you have to find your own manual entries.
165
00:10:37,483 --> 00:10:39,563
And that's where you'll find entries for the Nebula devices.
166
00:10:39,863 --> 00:10:40,123
Nice.
167
00:10:40,323 --> 00:10:45,743
And then you can configure the Nebula lighthouse to suggest a DNS server to the clients.
168
00:10:46,990 --> 00:10:51,150
And, um, that is, that's a really simple, it's like two lines of configuration
169
00:10:51,150 --> 00:10:53,150
on the lighthouse and you just give it the DNS server.
170
00:10:53,550 --> 00:10:57,450
And then, so that's also helping the Nebula clients discover who they're supposed
171
00:10:57,450 --> 00:10:58,610
to talk to for name resolution.
172
00:10:58,950 --> 00:11:02,250
And since I only have like three nodes on this little tiny, maybe four nodes
173
00:11:02,250 --> 00:11:07,190
now on this little tiny network, I'll talk more about super easy to just add the entries manually.
174
00:11:07,250 --> 00:11:10,330
And I don't, if this is going to be for a private clinic, so I don't think I'll be adding more hosts.
175
00:11:10,450 --> 00:11:13,670
One thing we should play with, which I haven't yet, but I'd like to get more
176
00:11:13,670 --> 00:11:19,090
into is doing either delegation or maybe using an API to trigger updates because
177
00:11:19,090 --> 00:11:21,970
Nebula lighthouses can serve DNS.
178
00:11:22,330 --> 00:11:22,410
Yeah.
179
00:11:22,890 --> 00:11:26,350
So you could also, depending on if you want to, maybe the static has advantages
180
00:11:26,350 --> 00:11:29,070
too, of course, but you could also maybe set it up so...
181
00:11:29,070 --> 00:11:29,190
Yeah.
182
00:11:29,590 --> 00:11:32,930
You know, the pie hole would just query Nebula and be able to answer for the
183
00:11:32,930 --> 00:11:34,670
Nebula host without you having to hard code it.
184
00:11:34,750 --> 00:11:39,630
The advantage was on the pie hole DNS server, now I also have a bunch of entries
185
00:11:39,630 --> 00:11:41,810
for the
devices that are on my LANs.
186
00:11:41,950 --> 00:11:46,150
So it hosts here at the studio and hosts at the RV are also on this DNS server.
187
00:11:46,270 --> 00:11:50,730
So all the machines, if you're on the LAN, whichever LAN you're on,
188
00:11:50,870 --> 00:11:54,710
or whichever Mesh VPN network you're on, we all can resolve the same host names now.
189
00:11:55,070 --> 00:11:57,790
So that's kind of why I didn't go that direction.
190
00:11:58,490 --> 00:12:01,610
But I think that would be an easier setup if you just had a couple of machines.
191
00:12:01,870 --> 00:12:04,890
Well, I meant like integrating the two, like keeping the pie hole,
192
00:12:05,390 --> 00:12:08,090
just letting Nebula answer for the host it knows about.
193
00:12:08,310 --> 00:12:11,190
Oh, okay. And then would it upstream to the pie hole when it does?
194
00:12:11,290 --> 00:12:13,750
I see. Yeah, I like, okay. Oh my God, change.
195
00:12:13,750 --> 00:12:18,430
How do you feel, Chris, about the need for internet access here?
196
00:12:18,530 --> 00:12:23,990
Because occasionally you don't actually have access whenever a storm comes by
197
00:12:23,990 --> 00:12:25,430
or you're traveling, that kind of thing.
198
00:12:25,530 --> 00:12:29,230
So your name resolution internally on your local network would be affected.
199
00:12:29,230 --> 00:12:31,110
Is that a correct understanding?
200
00:12:31,630 --> 00:12:38,510
I did. Yeah. And so for that, I kept my pie hole on my LAN. And it forwards now to this guy.
201
00:12:38,710 --> 00:12:39,090
Nice.
202
00:12:39,370 --> 00:12:41,890
But for the most part, because that pie hole has been around so long,
203
00:12:41,950 --> 00:12:45,590
I have all these same DNS entries already. So, but I did keep it for that reason.
204
00:12:46,925 --> 00:12:52,905
And I'm very happy now. It adds complexity to have two mesh networks and,
205
00:12:52,905 --> 00:12:58,365
you know, multiple LANs, but it's seamless now to the end user now that I've done this.
206
00:12:58,565 --> 00:13:04,465
So I'm pretty happy, and the latency is pretty good even for LTE connections, really.
207
00:13:05,045 --> 00:13:07,805
Well, you know, it kind of makes sense, too. It's like, it'd be one thing if
208
00:13:07,805 --> 00:13:10,605
you didn't have the existing infrastructure and all that, but because you kind
209
00:13:10,605 --> 00:13:14,345
of have hosts that are positioned to fit into both of these networks or could
210
00:13:14,345 --> 00:13:16,225
bridge them, like it doesn't actually.
211
00:13:16,225 --> 00:13:18,425
You didn't have to stand up a bunch of new infrastructure. You kind of just
212
00:13:18,425 --> 00:13:22,245
had to reprovision some of it to better work with your new setup.
213
00:13:22,465 --> 00:13:25,225
I would like to actually ask, so if you want to boost in or send us a contact,
214
00:13:25,525 --> 00:13:29,225
if you were building this from scratch, so I already had a pie hole going.
215
00:13:29,525 --> 00:13:32,105
But if you out there, listener, were building this from scratch,
216
00:13:32,105 --> 00:13:34,565
what would you have used to do this name resolution?
217
00:13:34,885 --> 00:13:37,885
Because it did cross my mind. Like, maybe this is just a stupid DNS mask thing.
218
00:13:37,965 --> 00:13:39,265
I just set up a simple DNS mask.
219
00:13:39,885 --> 00:13:43,725
But then I like the idea of a little bit of ad blocking for the systems as well.
220
00:13:43,725 --> 00:13:45,525
That's nice. That's a nice feature that comes with it.
221
00:13:46,225 --> 00:13:49,165
And you can do dns mask configuration with.
222
00:13:49,165 --> 00:13:53,105
Pot all right because it uses like a forks version that was my conclusion yeah
223
00:13:53,105 --> 00:13:57,425
i was like yeah well i might i kind of get and i know how to use it yep and
224
00:13:57,425 --> 00:14:00,965
it's worked fine for me and it's survived multiple major upgrades now so it's
225
00:14:00,965 --> 00:14:05,025
past those tests as well so it's a good project but i would be curious like
226
00:14:05,025 --> 00:14:07,385
i think you probably would use tectidium or technically that would least.
227
00:14:07,385 --> 00:14:11,145
Be not or like because i know can do sort of like delegate zones where it will
228
00:14:11,145 --> 00:14:14,825
say like hey for anything in this sub you know maybe you have like dot nebula
229
00:14:14,825 --> 00:14:18,345
demands or whatever, go query this server for those and then return those.
230
00:14:18,485 --> 00:14:21,885
It also has some plugin capability, which I haven't really explored. Um,
231
00:14:23,215 --> 00:14:25,255
Or, you know, there's a lot of good options these days.
232
00:14:25,295 --> 00:14:27,935
Yeah, I saw some people that were solving this with AdGuard.
233
00:14:28,895 --> 00:14:31,095
Okay, yeah. Yeah, you could totally use Bind, of course.
234
00:14:31,495 --> 00:14:33,895
So I'd just be interested to know how people are solving this.
235
00:14:35,055 --> 00:14:37,975
I would also like to know if anybody has a way to solve this declaratively,
236
00:14:38,015 --> 00:14:40,175
you know, so that would also be a winner in my book.
237
00:14:40,635 --> 00:14:41,855
But while we were talking about
238
00:14:41,855 --> 00:14:45,235
Nebula, you've been working on something that's kind of slick, Wes Pano.
239
00:14:46,015 --> 00:14:50,055
Yeah, it was just an idea we had while we were toying around with setting up
240
00:14:50,055 --> 00:14:51,255
the clinic the other week.
241
00:14:51,255 --> 00:14:56,755
was, well, what if you just had like a low-key, you know, not crazy production
242
00:14:56,755 --> 00:15:00,555
scale, not being like a whole control plane for Nebula necessarily,
243
00:15:01,155 --> 00:15:05,175
but just something to make printing new host certs easier.
244
00:15:05,515 --> 00:15:09,595
Yeah, could you explain that a little bit? So if I'm not using the managed product,
245
00:15:09,915 --> 00:15:11,855
there's sort of some cert exchanges that have to happen.
246
00:15:12,375 --> 00:15:16,435
Yeah, right. So you have to, you're basically managing a CA.
247
00:15:16,735 --> 00:15:16,775
Right?
248
00:15:16,835 --> 00:15:20,875
So you have your own certificate authority, and then to get hosts onto the network,
249
00:15:21,535 --> 00:15:25,455
they generate their own private key but then you kind of have to sign the public
250
00:15:25,455 --> 00:15:28,815
part of that and that's how they get blessed with a host name and an IP address
251
00:15:28,815 --> 00:15:31,855
on the network and then that's how anything trusts them,
252
00:15:32,675 --> 00:15:35,635
when you try to communicate with something you need to be able to present that
253
00:15:35,635 --> 00:15:39,035
public side that is signed by the CA that they all mutually trust and.
254
00:15:39,035 --> 00:15:43,315
The beauty is the simplicity is it's really coming down to files you're moving
255
00:15:43,315 --> 00:15:47,455
around that have keys in them and that is the totality of the infrastructure
256
00:15:47,455 --> 00:15:48,955
actually required to get this working,
257
00:15:49,895 --> 00:15:54,395
And if you sit with the amazingness of that for a moment, it really is very impressive.
258
00:15:54,555 --> 00:15:56,495
These machines are discovering themselves.
259
00:15:56,675 --> 00:15:58,635
You need a lighthouse, but they're discovering or use a public one.
260
00:15:59,035 --> 00:16:04,455
And they're communicating and creating a mesh VPN just by exchanging these key files.
261
00:16:04,715 --> 00:16:08,275
Yep. And, you know, just simple concepts of groups and you have stuff signed
262
00:16:08,275 --> 00:16:10,095
by the right thing and it kind of all just works. But...
263
00:16:11,582 --> 00:16:14,342
For simple static networks, that works pretty well. But, you know,
264
00:16:14,562 --> 00:16:19,202
I'd been playing around with my sidecar mesh setup on NixOS.
265
00:16:19,582 --> 00:16:21,862
And especially for like the demos I was doing and testing it out,
266
00:16:21,982 --> 00:16:22,682
it was pretty convenient.
267
00:16:22,862 --> 00:16:26,922
You know, products like Tailscale or Netbird, they have this UX you get with
268
00:16:26,922 --> 00:16:30,482
basically all you need is one secret, right? Like an API key,
269
00:16:30,622 --> 00:16:31,962
and you can put that in somewhere.
270
00:16:32,162 --> 00:16:36,642
And then when the client launches, it goes and uses that to an API and then can onboard itself.
271
00:16:36,782 --> 00:16:41,202
And I was just like, well, I wonder if we could get that same workflow with Nebula.
272
00:16:41,822 --> 00:16:47,902
So NACME, or ACME for Nebula, is my little attempt at that. It's super early
273
00:16:47,902 --> 00:16:49,482
days. I need to do a bunch more testing.
274
00:16:49,942 --> 00:16:52,562
Eventually, it'd be great to do renewals too. But right now,
275
00:16:52,702 --> 00:16:56,102
it's at the initial testing stage of
just being able to, you run a little server,
276
00:16:56,302 --> 00:17:01,462
you configure an API key that's bound to certain groups, and then you have a
277
00:17:01,462 --> 00:17:06,282
little client that can run and go get a new host onboarded.
278
00:17:06,602 --> 00:17:09,242
And so if you configure that, I also want to set up a bunch of this stuff,
279
00:17:09,242 --> 00:17:13,442
especially with nick's side but configure it to run before nebula uh you could
280
00:17:13,442 --> 00:17:17,482
have it go item potently check to see if it needs to configure the the host
281
00:17:17,482 --> 00:17:20,802
for the first time set up the keys and everything and then have nebula start
282
00:17:20,802 --> 00:17:23,462
and be ready to go or at least that's the idea.
283
00:17:24,102 --> 00:17:29,442
Yes this is really neat so it's automated certificate minting and it gives you
284
00:17:29,442 --> 00:17:33,442
essentially like you said it's a like an api key type type exchange.
285
00:17:33,442 --> 00:17:36,502
The goal too would be like it's sort of best effort right it's meant for like
286
00:17:36,502 --> 00:17:39,502
home lab or you know stuff where you maybe you're not going to go the full like
287
00:17:39,502 --> 00:17:41,382
crazy it automation it's.
288
00:17:41,382 --> 00:17:43,802
Great for like a small business network like we were just setting.
289
00:17:43,802 --> 00:17:46,522
And the whole thing with nebula right is like there are some
290
00:17:46,522 --> 00:17:49,482
trade-offs you have less with those certs and the way it's kind of like more
291
00:17:49,482 --> 00:17:53,562
like a jwt kind of style of trust you know you don't necessarily have this one
292
00:17:53,562 --> 00:17:57,222
database that determines all of the truth right in a sort of less eventually
293
00:17:57,222 --> 00:18:01,602
consistent way but the upside is nebula will just keep working right as long
294
00:18:01,602 --> 00:18:06,422
as the certs aren't expired like there's no the control plane nothing happens nothing goes down what.
295
00:18:06,422 --> 00:18:09,122
Freaked me out recently was the idea that maybe,
296
00:18:10,316 --> 00:18:16,996
My Google account could be suspended because, so PayPal decided to flag my account
297
00:18:16,996 --> 00:18:18,436
for like re-verification.
298
00:18:19,076 --> 00:18:21,916
And it's a very complicated process. It's not just like a regular,
299
00:18:22,096 --> 00:18:24,616
it's like a very in-depth, multiple types of documentation.
300
00:18:24,616 --> 00:18:26,216
What did you do? Nothing.
301
00:18:26,356 --> 00:18:26,856
I don't know, man.
302
00:18:26,876 --> 00:18:27,416
That's usually what it is.
303
00:18:27,496 --> 00:18:32,556
I don't know. But it occurred to me that if our Google Workspace account payment
304
00:18:32,556 --> 00:18:36,556
got bounced because of PayPal, then I might not be able to authenticate to my tail net anymore.
305
00:18:37,516 --> 00:18:39,136
And that freaked me out a little bit.
306
00:18:39,296 --> 00:18:39,516
Yeah.
307
00:18:39,516 --> 00:18:42,876
And that's where I was like, oh, the simplicity of these keys and the fact that
308
00:18:42,876 --> 00:18:47,376
they'll work for as long as I issue these keys for is very reassuring.
309
00:18:47,616 --> 00:18:50,376
And so my thought was this was like worst case, you know, like even if this
310
00:18:50,376 --> 00:18:54,316
is down, you can still manually add things like this is just a convenience functionality
311
00:18:54,316 --> 00:18:55,656
to make it easier to onboard hosts.
312
00:18:55,656 --> 00:19:00,016
So this is not setting up routing. This is not setting up the networking layer
313
00:19:00,016 --> 00:19:03,636
stuff. This is just keys to get you going to then build that stuff.
314
00:19:03,796 --> 00:19:04,016
Exactly.
315
00:19:04,596 --> 00:19:07,396
That's really cool. NACME. I like the name, too. It's very clever.
316
00:19:07,496 --> 00:19:08,336
I think that could take off.
317
00:19:08,996 --> 00:19:14,896
so uh we'll put a link in the show notes it's on wes's github n-a-c-m-e mit
318
00:19:14,896 --> 00:19:20,876
licensed indeed indeed uh and uh version 0.10 was released just recently.
319
00:19:20,876 --> 00:19:25,596
Yeah we'll see i should cut a new version it's move it's you know it's moving
320
00:19:25,596 --> 00:19:27,356
fast and uh needs more tests.
321
00:19:30,795 --> 00:19:34,635
I want to say thank you to our members and our boosters. Next week,
322
00:19:34,655 --> 00:19:36,355
I'm calling it a birthday episode, boys.
323
00:19:36,575 --> 00:19:38,915
I don't know what we're going to do, but check this out.
324
00:19:39,175 --> 00:19:44,255
So Brian and I started podcasting in January, right around my actual birthday,
325
00:19:44,255 --> 00:19:48,595
almost exactly 20 years ago to the day for next week's episode.
326
00:19:49,455 --> 00:19:52,775
20 years of podcasting on my birthday next week.
327
00:19:52,915 --> 00:19:56,275
So if that's not a long-term commitment to the space, I don't know what is.
328
00:19:56,455 --> 00:19:57,855
So send a birthday boost.
329
00:19:58,055 --> 00:20:01,735
We'd love that. or become a member and use the promo code bootleg.
330
00:20:01,855 --> 00:20:04,095
We have a couple of, well, we have a handful of redemptions left.
331
00:20:05,415 --> 00:20:09,735
And, you know, you become a member at the party or a core contributor and support
332
00:20:09,735 --> 00:20:10,835
the show at a great discount.
333
00:20:11,315 --> 00:20:14,455
And if you'd like to get your company or product in front of the world's largest
334
00:20:14,455 --> 00:20:16,595
and best Linux audience, show me an email.
335
00:20:16,975 --> 00:20:19,935
Chris at jupiterbroadcasting.com. This space could be yours.
336
00:20:20,275 --> 00:20:24,575
And thank you to everybody who supports the show. We greatly appreciate it.
337
00:20:27,683 --> 00:20:30,883
Now, Chris, for the last two episodes, you've been talking about deploying,
338
00:20:30,883 --> 00:20:35,723
you know, a bunch of new machines at a clinic, making sure you have the responsibility
339
00:20:35,723 --> 00:20:39,243
for keeping your wife's business happy from a tech perspective.
340
00:20:39,723 --> 00:20:44,863
And now you're putting up, you know, some infrastructure that you also need
341
00:20:44,863 --> 00:20:50,143
to be working at all times. I would imagine now is the time to make sure all
342
00:20:50,143 --> 00:20:52,943
that stuff yells at you whenever it's not in good health.
343
00:20:52,943 --> 00:20:54,003
Right he.
344
00:20:54,003 --> 00:20:57,883
Wanted to uh just leave a business card with my phone number on it but i didn't
345
00:20:57,883 --> 00:20:58,803
think that was a great idea.
346
00:20:58,803 --> 00:21:02,723
And part of me is like well we should do this why it's still fresh in the mind
347
00:21:02,723 --> 00:21:08,563
because this stuff fades oh yeah and i thought well if we're going to do this for hadia's clinic,
348
00:21:09,383 --> 00:21:12,643
um maybe i should do this for my own infrastructure and then i thought wouldn't
349
00:21:12,643 --> 00:21:17,003
it be great if we could build something that if we ever did this you know on
350
00:21:17,003 --> 00:21:19,543
occasion for audience members or whoever,
351
00:21:20,003 --> 00:21:23,363
wouldn't it be nice if we could also offer to monitor their stuff and i could
352
00:21:23,363 --> 00:21:26,703
build something that was pretty flexible like this and i'm sure you boys are
353
00:21:26,703 --> 00:21:28,343
familiar with uptime kuma,
354
00:21:29,163 --> 00:21:34,123
we actually use it at jb alex set it up for us a while ago and we like it it's
355
00:21:34,123 --> 00:21:38,983
pretty simple and it alerts us when something goes offline like one of our websites
356
00:21:38,983 --> 00:21:43,843
via telegram bot and it creates a nice dashboard super easy to self-host and
357
00:21:43,843 --> 00:21:48,563
they have a demo i'll put a link in the show notes And it does monitoring for HTTP, TCP.
358
00:21:49,023 --> 00:21:54,843
It can search website keywords, check WebSockets, do ping, check DNS records, stuff like that.
359
00:21:55,023 --> 00:21:56,663
Very easy, straightforward to get going.
360
00:21:56,883 --> 00:22:00,863
Yes. So obviously that was the first thing I decided because this is what I
361
00:22:00,863 --> 00:22:02,003
have the most experience with.
362
00:22:02,423 --> 00:22:06,783
And I thought this will be the way to go. Can you guess what the problem was?
363
00:22:07,003 --> 00:22:11,303
Well, I think I know because it's been a longstanding issue we've had with the project.
364
00:22:11,423 --> 00:22:12,403
In fact. What's that?
365
00:22:12,603 --> 00:22:14,943
A lack of declarative configuration.
366
00:22:15,463 --> 00:22:19,323
Yeah, man, it's just really gooey. Well, I had to set up something like,
367
00:22:19,323 --> 00:22:25,323
you know, 45 hosts and services to monitor and I was sitting there
creating
368
00:22:25,323 --> 00:22:30,423
all the entries and I'm like, this is going to take me to two days to do.
369
00:22:31,530 --> 00:22:34,890
And also because I wanted them to be actionable and all this stuff. So it's like, oh, my God.
370
00:22:35,030 --> 00:22:40,230
And then I also wanted tiered escalating alerts. So first ping me via notify.
371
00:22:40,710 --> 00:22:43,610
So because I have a lot of stuff coming in via NTFY these days.
372
00:22:44,190 --> 00:22:47,210
And so that's sort of a feed of just checking on my systems.
373
00:22:47,230 --> 00:22:48,750
And if I'm available, I check it.
374
00:22:49,150 --> 00:22:54,390
But if I'm not presently thinking about my infrastructure, my systems, I don't check it.
375
00:22:54,590 --> 00:22:57,850
So I needed something that would break through to Telegram and kind of, you know, kick it up.
376
00:22:57,850 --> 00:22:58,110
Yeah.
377
00:22:58,250 --> 00:23:01,730
And so I wanted and I wanted it based on different thresholds and trends.
378
00:23:01,950 --> 00:23:06,190
And so when I started getting into I need to add, let's just say 45 ish host
379
00:23:06,190 --> 00:23:11,530
combination services, maybe more and more complex alerting with a little bit more nuance.
380
00:23:13,395 --> 00:23:17,135
I really started to hit two different walls. Like my GUI exhaustion kicked in.
381
00:23:17,315 --> 00:23:19,435
Like if I was adding like five systems, I would just done it.
382
00:23:19,895 --> 00:23:23,675
And then trying to get complex logic around alerts started to get frustrating.
383
00:23:24,395 --> 00:23:28,055
Yeah, you combine those two. That could be pretty annoying, especially if you
384
00:23:28,055 --> 00:23:31,695
have to like go configure it and then go run the test and then go see if it
385
00:23:31,695 --> 00:23:34,895
did the thing you want and then go repeat that cycle a whole bunch.
386
00:23:35,555 --> 00:23:40,515
Yeah, man. So I decided to break the seal on something that I have never,
387
00:23:40,515 --> 00:23:45,035
I've never bothered learning. I've never wanted to embrace because of the overhead.
388
00:23:45,035 --> 00:23:47,575
It's been a long time coming on the show. I'm excited for this.
389
00:23:47,595 --> 00:23:53,035
It has. Ladies and gentlemen, I have finally deployed my first Prometheus instance.
390
00:23:53,395 --> 00:23:53,815
Woohoo!
391
00:23:54,115 --> 00:23:58,155
And of course, once you have a Prometheus instance, you want pretty dashboards
392
00:23:58,155 --> 00:23:59,475
and you want all the details.
393
00:23:59,675 --> 00:24:04,255
So along with that, I have also finally deployed my first Grafana instance.
394
00:24:04,795 --> 00:24:07,355
Yeah, something tells me you really deployed the Grafana and then you just got
395
00:24:07,355 --> 00:24:08,815
the Prometheus, so you had something to fill it.
396
00:24:09,375 --> 00:24:12,375
It feels like that deserves a round of applause, really, there,
397
00:24:12,475 --> 00:24:13,955
Chris. Give yourself, yeah.
398
00:24:14,175 --> 00:24:14,475
Thank you.
399
00:24:14,735 --> 00:24:15,375
Everybody, yeah.
400
00:24:15,755 --> 00:24:19,595
I mean, uptime Kuma is good, but I needed a little bit more than that.
401
00:24:19,635 --> 00:24:23,415
And I also have kind of a complex situation that I thought Prometheus was a
402
00:24:23,415 --> 00:24:24,175
little better at solving.
403
00:24:24,575 --> 00:24:26,795
I have set up a federated configuration.
404
00:24:27,515 --> 00:24:32,295
And I had a problem where I have my Odroid on my home lab that doesn't have
405
00:24:32,295 --> 00:24:35,695
a lot of available resources. as it has some, but now it's doing frigging a bunch of other stuff.
406
00:24:36,515 --> 00:24:39,855
And I'm on LTE on two different ends of the connection, not all of them,
407
00:24:39,955 --> 00:24:41,795
but two different ends are on LTE networks.
408
00:24:41,935 --> 00:24:45,315
So they're slow and I can't just be blasting a bunch of data.
409
00:24:45,435 --> 00:24:49,275
My original idea was I'll set up a central VPS connected to all the mesh networks,
410
00:24:49,275 --> 00:24:52,715
and then it will monitor everything. And I just go to the VPS dashboard.
411
00:24:52,915 --> 00:24:56,795
But then I actually started running the math on that. And I realized the overhead
412
00:24:56,795 --> 00:25:00,615
would be somewhere between 40 megabytes to 100 megabytes a day,
413
00:25:01,395 --> 00:25:05,095
best case, plus the overhead and latency it adds and slows down the whole LTE
414
00:25:05,095 --> 00:25:06,375
connection while it's doing that stuff.
415
00:25:06,555 --> 00:25:09,695
And that's only going to grow as you add more stuff that you monitor, surely.
416
00:25:10,295 --> 00:25:17,315
Exactly. So the solution was a federated setup where I had local monitoring on my home lab system,
417
00:25:18,372 --> 00:25:24,392
monitoring on a VPS, and then light remote monitoring on my wife's clinic network.
418
00:25:24,792 --> 00:25:29,392
And I set up a Prometheus system with a black box exporter that does some additional
419
00:25:29,392 --> 00:25:33,852
like HTTP, TCP, ping checks, and can do some API authentication for me.
420
00:25:33,972 --> 00:25:36,672
And that all feeds into Grafana to give me dashboards.
421
00:25:36,852 --> 00:25:40,592
And then that all talks to alert manager. So let me zoom out.
422
00:25:41,812 --> 00:25:46,712
Prometheus is running on two different systems. plus a little Prometheus client
423
00:25:46,712 --> 00:25:52,092
is running on my wife's clinic and I have a Prometheus integration now running on Home Assistant.
424
00:25:52,332 --> 00:25:52,712
Oh yeah.
425
00:25:52,872 --> 00:25:53,372
So this is collecting.
426
00:25:53,372 --> 00:25:54,012
You knew that was coming.
427
00:25:54,112 --> 00:25:56,912
Yeah, buddy. And that's really useful. I could talk more about that.
428
00:25:57,012 --> 00:26:01,272
But the Prometheus agent is essentially collecting all of the
metrics,
429
00:26:01,452 --> 00:26:06,332
the CPU, the disk usage, and it allows me to trend and alert on these over time.
430
00:26:06,772 --> 00:26:11,532
And with Home Assistant, I'll just mention this quickly, that integration is
431
00:26:11,532 --> 00:26:16,712
pretty awesome because you can export a lot of different things from automation
432
00:26:16,712 --> 00:26:18,772
details, log, all these types of things.
433
00:26:19,012 --> 00:26:22,792
I mean, it basically has a whole bunch of stats in its own stats engine to begin with, right?
434
00:26:22,932 --> 00:26:23,352
Oh, yeah.
435
00:26:23,472 --> 00:26:25,232
You can kind of just dump those out to Prometheus.
436
00:26:25,552 --> 00:26:29,412
It's a sensor machine, yeah. And so the way I use that now is I am using,
437
00:26:29,412 --> 00:26:31,512
via Prometheus data export into
438
00:26:31,512 --> 00:26:35,872
Grafana, I have dashboards on how long my different climate entities run.
439
00:26:36,332 --> 00:26:39,232
So since it's winter, we have some electric heat out in different areas,
440
00:26:39,232 --> 00:26:41,772
and I want to make sure that they're not running excessive because that would
441
00:26:41,772 --> 00:26:42,972
tell me the heater isn't keeping up.
442
00:26:43,132 --> 00:26:45,772
I want to know how long we're running electric heat. I want to compare that
443
00:26:45,772 --> 00:26:48,832
to our intake from solar. And I want to have all that on one dashboard.
444
00:26:49,072 --> 00:26:54,672
And now I have just not only a beautiful display, but good historical data that I can work with.
445
00:26:54,872 --> 00:26:58,912
And all of this is pulled in on my local Prometheus incident that's running on my home lab.
446
00:26:59,712 --> 00:27:03,272
Then I have Prometheus running on the VPS. That's doing some remote checks to
447
00:27:03,272 --> 00:27:05,412
make sure that the remote systems are up.
448
00:27:05,552 --> 00:27:09,692
And it has some logic to understand that if the mesh network is down, don't freak out.
449
00:27:10,052 --> 00:27:12,932
don't alert about every single host. You know, I wanted some of this tiered
450
00:27:12,932 --> 00:27:15,772
logic in there so it knows if one network connection is down,
451
00:27:15,832 --> 00:27:17,392
then everything that's on that network is down.
452
00:27:18,559 --> 00:27:20,519
which is going to hopefully save me a lot of notifications.
453
00:27:20,779 --> 00:27:23,919
Yeah, and you've saved yourself that first night, right? Where the network goes
454
00:27:23,919 --> 00:27:25,339
down and suddenly everything's on fire.
455
00:27:25,519 --> 00:27:29,039
And then everything it's observing about the VPS itself, the mesh networks,
456
00:27:29,039 --> 00:27:33,759
and the wife's clinic is getting federated back to my Grafana instance.
457
00:27:34,039 --> 00:27:39,699
So I have just one dashboard to view everything. And that's running on my local instance. Oh, man.
458
00:27:40,079 --> 00:27:45,519
And the difference is, according to my calculations, boys, the difference is
459
00:27:45,519 --> 00:27:49,779
about two megabytes a day of data usage. nicely done yeah that's.
460
00:27:49,779 --> 00:27:50,659
At least a power of 10.
461
00:27:50,659 --> 00:27:55,819
It's it was a nice little savings and it's less it's less running on my home lab or on the vps i do.
462
00:27:55,819 --> 00:27:59,559
Like that you kind of went from zero to not uh you know.
463
00:27:59,559 --> 00:28:03,939
Yeah unsophisticated setup i think the real deal breaker was,
464
00:28:05,359 --> 00:28:09,059
everything could be done declaratively and i could do this sort of hybrid federated
465
00:28:09,059 --> 00:28:12,859
setup and those flexible yeah coming together those two things like it's like
466
00:28:12,859 --> 00:28:16,679
to create all the dashboards I didn't create a single dashboard in the GUI.
467
00:28:16,739 --> 00:28:20,559
There's so many community examples that you can modify and get started with.
468
00:28:20,659 --> 00:28:24,099
And then you drop them in a folder and that becomes a dashboard and Bob's your
469
00:28:24,099 --> 00:28:26,059
uncle. You got all the things and bells and whistles you'd want.
470
00:28:26,219 --> 00:28:28,519
And then I have alert manager, last piece.
471
00:28:28,779 --> 00:28:34,099
I have alert manager running on the VPS and everything forwards to that.
472
00:28:34,239 --> 00:28:37,999
So I only have to have one alert instance and it can communicate with notify.
473
00:28:37,999 --> 00:28:41,279
It can communicate with telegram because I set up a little bot thing and all of that.
474
00:28:41,799 --> 00:28:45,739
and it handles all that stuff. And it will also let me know if any of the remote
475
00:28:45,739 --> 00:28:48,099
hosts are down or if any of the mesh networks go down.
476
00:28:49,038 --> 00:28:54,818
And the results have been, there's about 31 services that I'm getting real-time
477
00:28:54,818 --> 00:28:58,698
visibility into their performance and their metrics, all in beautiful Grafana dashboards.
478
00:28:59,198 --> 00:29:02,958
And I also have real-time alerts anytime any service goes down.
479
00:29:03,318 --> 00:29:06,998
And I'm now very carefully monitoring storage, which is very tight these days.
480
00:29:07,198 --> 00:29:10,138
And so I have different thresholds for storage alerts. And I have different
481
00:29:10,138 --> 00:29:13,878
thresholds for like if home assistance at 80% CPU for X amount of time.
482
00:29:13,998 --> 00:29:17,778
And if it gets to 85 or 90 for X amount of time, we do different styles of escalation.
483
00:29:17,778 --> 00:29:22,238
and then there's follow-up for when things recover i get a recovery alert so
484
00:29:22,238 --> 00:29:23,438
that's all working really beautiful.
485
00:29:23,438 --> 00:29:24,738
Yeah i'm curious how you tested it.
486
00:29:24,738 --> 00:29:35,358
The entire well by shutting things down i did excellent all right docker compose down you know.
487
00:29:35,358 --> 00:29:39,578
The next version of this is you give your agent access and you ask it to stop a random service.
488
00:29:39,578 --> 00:29:43,618
Right just chaos monkey oh my god that'd be fun basically just give west your credentials,
489
00:29:45,218 --> 00:29:48,178
yeah that's to most of it um but so i measured
490
00:29:48,178 --> 00:29:51,238
the whole stack across all the machines 400 megabytes of
491
00:29:51,238 --> 00:29:54,838
ram totally fine not even
492
00:29:54,838 --> 00:29:57,538
making really an impact at all in my home lab system and i was worried because i'd heard some
493
00:29:57,538 --> 00:30:00,538
stories about grafana but i really really
494
00:30:00,538 --> 00:30:03,398
like the home assistant integration with prometheus it's
495
00:30:03,398 --> 00:30:06,158
something else i've put off for a while if you have been tempted to
496
00:30:06,158 --> 00:30:09,418
try this the insights are fantastic and then
497
00:30:09,418 --> 00:30:12,478
the other thing that's really fun is frigate which
498
00:30:12,478 --> 00:30:15,558
i also set up recently also has an
499
00:30:15,558 --> 00:30:18,398
api where i can export all the
500
00:30:18,398 --> 00:30:21,318
information to prometheus and grafana
501
00:30:21,318 --> 00:30:24,518
so i have details on how my coral is doing
502
00:30:24,518 --> 00:30:28,678
inference wise and my different cameras and their connectivity and i can and
503
00:30:28,678 --> 00:30:33,098
their detection frames per second the camera's overall health when the automations
504
00:30:33,098 --> 00:30:36,738
execute and how frequently for like arming and disarming the recording if they
505
00:30:36,738 --> 00:30:41,098
are available at all is all coming into this dashboard so i have essentially
506
00:30:41,098 --> 00:30:42,878
a camera health dashboard now.
507
00:30:43,919 --> 00:30:46,219
It's so great because you have dashboards.
508
00:30:46,219 --> 00:30:46,959
For your dashboards.
509
00:30:47,119 --> 00:30:50,959
I do. And a lot of the RAR projects, it's great. Oh, I'm like,
510
00:30:51,079 --> 00:30:52,839
I'm inception dashboards over here.
511
00:30:52,999 --> 00:30:57,079
A lot of the RAR projects out there that we don't talk about also have APIs
512
00:30:57,079 --> 00:31:00,539
and health API endpoints that also plug into this.
513
00:31:00,619 --> 00:31:03,439
So you can get all that kind of information in there.
514
00:31:04,219 --> 00:31:09,299
And it, it really struck me like how, now I get it, why people go through setting all this up.
515
00:31:09,379 --> 00:31:13,079
And yes, it's a lot of YAML and all of that, but there's so many great examples out there.
516
00:31:13,739 --> 00:31:21,519
And I now have an enterprise grade monitoring stack that I just never even thought I would get into.
517
00:31:23,080 --> 00:31:27,800
Zero dollars spent, you know, one day I've set up really a lot of documentation
518
00:31:27,800 --> 00:31:30,620
and maybe five to eight hours of
fiddling to get it all working.
519
00:31:31,440 --> 00:31:36,160
And it really makes me feel a lot better about my self-hosted infrastructure.
520
00:31:36,500 --> 00:31:39,980
I have built quite a little empire now of things I depend on and my family depends
521
00:31:39,980 --> 00:31:41,540
on and my wife and whatnot.
522
00:31:41,960 --> 00:31:45,420
And I probably haven't been monitoring it as seriously as I should.
523
00:31:45,800 --> 00:31:49,340
And I just thought that, eh, it's fine. But honestly, it does feel a lot better
524
00:31:49,340 --> 00:31:53,000
because I'm getting insights before things go wrong.
525
00:31:53,080 --> 00:31:55,620
Now I'm getting ideas of trends.
526
00:31:55,880 --> 00:31:58,080
So stuff I know, Oh, this is actually something I need to address.
527
00:31:58,460 --> 00:32:02,020
And I know something's a problem before the wife has to tell me it's a problem.
528
00:32:02,260 --> 00:32:05,140
So I know if jellyfin isn't working for some reason or et cetera,
529
00:32:05,420 --> 00:32:08,200
or I know if her system isn't backing up before she has to tell me.
530
00:32:09,060 --> 00:32:13,920
So if you have a self-hosted setup, definitely uptime Kuma is a pretty good
531
00:32:13,920 --> 00:32:18,740
starting point. But if you have the ambition and the time Prometheus and Grafana
532
00:32:18,740 --> 00:32:22,700
get a double recommendation from me, I waited way too long.
533
00:32:23,080 --> 00:32:29,160
There is a real learning curve, but the visibility you get out of it, it's just so useful.
534
00:32:29,480 --> 00:32:33,480
Plus, like I've revisualized my entire infrastructure once again.
535
00:32:33,660 --> 00:32:37,480
All the stuff I've built, like I know how many services and how many hosts and
536
00:32:37,480 --> 00:32:39,100
I know how they're doing.
537
00:32:39,320 --> 00:32:42,480
I have a much more concrete picture once again of everything I've done over
538
00:32:42,480 --> 00:32:43,420
the last five, six years.
539
00:32:43,620 --> 00:32:47,500
Well, I think as you're discovering, right, a lot of things publish Prometheus metrics.
540
00:32:47,860 --> 00:32:48,000
Yeah.
541
00:32:48,000 --> 00:32:54,020
So actually, as Tiny points out in our chat room, Uptime Kuma itself can publish to Prometheus.
542
00:32:54,060 --> 00:32:55,580
Yes, I thought about that for a second.
543
00:32:55,760 --> 00:32:59,100
And Nebula does as well. I don't know if you've integrated that yet.
544
00:32:59,780 --> 00:33:04,440
Hmm. Hmm. Hmm. Should look to see what Tailscale can do too,
545
00:33:04,480 --> 00:33:05,340
but that would be really useful.
546
00:33:05,840 --> 00:33:08,720
Yeah, I'm pretty happy with this. I did have to kind of, you know,
547
00:33:08,780 --> 00:33:09,680
be tight on the retention.
548
00:33:09,900 --> 00:33:13,980
So I don't have, I think I have like 30 or 60 days. I couldn't go crazy because
549
00:33:13,980 --> 00:33:14,820
of storage constraints.
550
00:33:15,720 --> 00:33:17,660
And
I did, I will admit, Wes...
551
00:33:20,447 --> 00:33:26,007
I feel a little guilty, but I did a lot of it with Docker. And the reason was,
552
00:33:26,107 --> 00:33:27,427
and it's always what gets me,
553
00:33:30,047 --> 00:33:36,387
is a lot of the community add-ons and plugins all assume you're using the Docker instance.
554
00:33:36,827 --> 00:33:39,187
And it's one of those things where it's like, well, yeah, I could come up with
555
00:33:39,187 --> 00:33:41,787
a way to declaratively do that with Nix every single time.
556
00:33:42,887 --> 00:33:48,687
Or I just start the container and it works, right? And so all of the OS-level
557
00:33:48,687 --> 00:33:51,447
stuff to make it work is all declarative, obviously.
558
00:33:52,107 --> 00:33:56,687
But then, like, Prometheus, Grafana, and Alert Manager, they're all in,
559
00:33:56,707 --> 00:33:57,927
like, one big Docker compose.
560
00:33:58,287 --> 00:33:58,647
Ah, yeah.
561
00:33:59,787 --> 00:34:00,947
I felt bad about that.
562
00:34:01,047 --> 00:34:04,487
No, I mean, as long as you're dabbling, I think, a little bit and seeing that
563
00:34:04,487 --> 00:34:06,927
Nix can play very nicely with these things.
564
00:34:07,107 --> 00:34:09,427
And it was a no-brainer for the Nginx. Like, some of the stuff,
565
00:34:09,547 --> 00:34:13,547
I had to add some more stuff behind a reverse proxy and get SSL certs for it
566
00:34:13,547 --> 00:34:15,247
that I didn't have before just so I could keep consistent.
567
00:34:15,827 --> 00:34:18,127
So I wasn't doing IP for some stuff and name for other stuff.
568
00:34:18,247 --> 00:34:21,327
I wanted names for everything. So I just got all the DNS set up anyways.
569
00:34:22,167 --> 00:34:26,567
And that was really, really nice to just configure all of the Nginx stuff via Nix.
570
00:34:26,787 --> 00:34:29,467
And, I mean, it should be easy, right? Like any of your Nix hosts,
571
00:34:29,467 --> 00:34:33,067
you can just add in a bit to have it run a Prometheus exporter for the node
572
00:34:33,067 --> 00:34:35,127
and send the node metrics too.
573
00:34:35,707 --> 00:34:37,787
And I know between the three of us,
574
00:34:38,826 --> 00:34:43,466
I'm also the Git Luddite, but the other thing I liked and appreciated about
575
00:34:43,466 --> 00:34:48,506
having declarative config for my monitoring setup is that I could use Git to manage that.
576
00:34:48,826 --> 00:34:52,626
And if I F it up in the future, you know, I've got some recoverability there.
577
00:34:52,726 --> 00:34:56,746
So the more I can define via text, I feel like the safer it is to experiment
578
00:34:56,746 --> 00:34:59,146
and the easier it is to roll back.
579
00:34:59,986 --> 00:35:02,986
And so that's, I just, that's something I just, food of thought.
580
00:35:03,126 --> 00:35:05,586
One of the lessons I took away from the setup is that gave me a little bit of
581
00:35:05,586 --> 00:35:08,066
comfort level to experiment with something that I didn't fully understand yet.
582
00:35:08,066 --> 00:35:09,066
that has a big learning curve.
583
00:35:09,446 --> 00:35:12,566
And now that you have it captured, you can watch as it evolves too,
584
00:35:12,686 --> 00:35:15,286
right? So you have rollbacks, but you can also then go, well,
585
00:35:15,346 --> 00:35:17,026
what did I tweak? Was that what broke it?
586
00:35:17,286 --> 00:35:21,266
And I did catch a couple of things already, I will say too. I had some choral
587
00:35:21,266 --> 00:35:24,946
performance degradation issues that I tracked down to Wi-Fi actually,
588
00:35:25,146 --> 00:35:28,806
but it started a whole process of like breaking down where the problem was at.
589
00:35:28,966 --> 00:35:33,026
What is the maintenance going to be like for this? Like how likely are you if
590
00:35:33,026 --> 00:35:38,266
you're just booting up a new container for some kind of new system you're playing
591
00:35:38,266 --> 00:35:43,046
with that may last a long time are you likely to have that to the dashboard here in
592
00:35:43,426 --> 00:35:48,506
the process of setting it all up or is this just going to fade a little bit
593
00:35:48,506 --> 00:35:51,746
and then you'll have the problem where you've got a bunch of services that aren't
594
00:35:51,746 --> 00:35:54,226
actually integrated in this how do you think that's going to go.
595
00:35:54,226 --> 00:35:57,966
That's a great question that's a great question um because
596
00:35:57,966 --> 00:36:01,346
my current thinking so i haven't thought a lot about that because
597
00:36:01,346 --> 00:36:06,126
i've been thinking i need to really freeze the state of my odroid and i need
598
00:36:06,126 --> 00:36:10,006
to stop adding stuff because every single effing thing i add i need to migrate
599
00:36:10,006 --> 00:36:15,666
to a one liter pc one day and i just went and made it a lot more complicated
600
00:36:15,666 --> 00:36:20,466
right so i have been thinking i was actually going to hit the pause button for a while,
601
00:36:20,966 --> 00:36:25,186
until i get to that migration but you raise a good point of like what if i find
602
00:36:25,186 --> 00:36:29,666
it in my new favorite self-hosted app and i get it all set up do i throw it
603
00:36:29,666 --> 00:36:33,806
into the monitoring system and i I think my answer for that is I don't know if you guys do this.
604
00:36:34,951 --> 00:36:40,171
This is probably just a Chris thing, but I have, I have two tiers for self-hosted
605
00:36:40,171 --> 00:36:41,531
applications. You know where I'm going?
606
00:36:41,671 --> 00:36:42,231
I think so.
607
00:36:44,771 --> 00:36:47,791
And it's like, if I'm just playing around or if it's just something for me or
608
00:36:47,791 --> 00:36:50,191
really, you know, maybe I want to, I don't know, for whatever reason,
609
00:36:50,191 --> 00:36:54,531
I'll just put it on a port and I'll just go to the local IP and I'll put the
610
00:36:54,531 --> 00:36:55,731
colon in the browser like an animal.
611
00:36:57,311 --> 00:37:01,031
but then when it becomes like oh this is something that's serious then i go
612
00:37:01,031 --> 00:37:05,011
ahead and i set up the reverse proxy and i get an ssl cert for it and i even
613
00:37:05,011 --> 00:37:06,331
register a dns name because.
614
00:37:06,331 --> 00:37:08,431
Some stuff just doesn't survive to that level you know.
615
00:37:08,431 --> 00:37:13,231
Right so i think that is the threshold in which i now need to say and i'm going
616
00:37:13,231 --> 00:37:14,491
to add it to the monitoring system.
617
00:37:14,491 --> 00:37:17,431
There'll probably be a natural point where you realize that it's down and you
618
00:37:17,431 --> 00:37:19,391
wanted it to be out but then oh right okay.
619
00:37:19,391 --> 00:37:24,291
Better ahead that other people do this let us know send a booster contact form
620
00:37:24,291 --> 00:37:27,311
and let us know if you guys do this I just wonder if it's a sus thing.
621
00:37:27,771 --> 00:37:31,891
Because I've definitely seen some other folks that we know be like, oh, why do you do that?
622
00:37:32,171 --> 00:37:35,391
I think my other question I have for you guys is, do you honestly think I did
623
00:37:35,391 --> 00:37:37,631
it overkill? Do you think I went too far with this?
624
00:37:37,991 --> 00:37:39,991
I think, is that implicit in your question there, Brent?
625
00:37:40,111 --> 00:37:41,971
How many more pie holes would you have run?
626
00:37:42,431 --> 00:37:43,091
Yeah, right?
627
00:37:43,311 --> 00:37:48,351
I guess it is a little bit, because there seems like there's such a gap between
628
00:37:48,351 --> 00:37:52,391
where you started solving this problem versus where you ended up.
629
00:37:54,051 --> 00:37:59,491
but as long as it's well your requirements were quite specific as well right
630
00:37:59,491 --> 00:38:04,031
so I think had you loosen those requirements especially with the notifying you
631
00:38:04,031 --> 00:38:05,171
know the tiered notifications,
632
00:38:05,691 --> 00:38:09,871
that probably would have made this much much easier for you however you probably
633
00:38:09,871 --> 00:38:13,551
would have hated your life every day of the monitoring system after that so
634
00:38:13,551 --> 00:38:15,531
I think if you're looking long
635
00:38:15,531 --> 00:38:18,591
term which it sounds like you are with this kind of monitoring then I'm,
636
00:38:19,472 --> 00:38:24,052
It sounds like you made the right choice, because your digital life and your
637
00:38:24,052 --> 00:38:27,692
maintenance of that life will just get better.
638
00:38:28,172 --> 00:38:31,672
You know, I saw this morning over on the BcacheFS subreddit,
639
00:38:31,672 --> 00:38:33,392
a couple different folks working
640
00:38:33,392 --> 00:38:37,332
on both for Telegraph and then for Prometheus, BcacheFS collectors.
641
00:38:37,872 --> 00:38:38,352
Cool.
642
00:38:38,752 --> 00:38:40,432
So a little incentive for you in the future.
643
00:38:40,552 --> 00:38:42,212
So you don't think I've overdone it?
644
00:38:43,452 --> 00:38:45,272
Not if you install BcacheFS, no.
645
00:38:45,272 --> 00:38:49,432
I mean, if I could pull BcacheFS metrics in, that would be pretty neat.
646
00:38:49,512 --> 00:38:50,532
I think that justifies your setup.
647
00:38:50,572 --> 00:38:55,212
But you see, I'm a little worried about that. But because, again,
648
00:38:56,072 --> 00:39:00,352
it feels it's like one of these things where when it's when it's all declared,
649
00:39:00,352 --> 00:39:04,332
I can kind of re pick it up and read through it and understand it.
650
00:39:04,432 --> 00:39:08,312
Where when it's the GUI, I have to really dig through it and really,
651
00:39:08,512 --> 00:39:12,492
really, really have to grind again to get it figured out again.
652
00:39:12,692 --> 00:39:14,712
I don't know. Maybe that's just me convincing myself.
653
00:39:14,712 --> 00:39:18,612
Well, no, and I mean, there's a lot of pieces, but I think one of the benefits
654
00:39:18,612 --> 00:39:22,392
of a Prometheus-style setup is, right, you're building on top of time series,
655
00:39:22,432 --> 00:39:25,532
and that's a fairly universal format for a lot of things.
656
00:39:25,672 --> 00:39:26,152
Yeah, yeah, yeah.
657
00:39:26,572 --> 00:39:30,052
Wes didn't answer your simple question. Do you think that he went overkill?
658
00:39:31,132 --> 00:39:33,532
No, I mean, how many services did you say you had?
659
00:39:33,792 --> 00:39:38,592
Around 37, and then, you know, five or six hosts in there, something like that. Yeah.
660
00:39:38,752 --> 00:39:41,552
I mean, it seems like maybe if anything, it's more of like, um,
661
00:39:41,692 --> 00:39:45,792
like a reckoning with the level of infrastructure you're already providing and
662
00:39:45,792 --> 00:39:48,812
that it deserves a similar class of monitoring.
663
00:39:49,132 --> 00:39:51,012
Yeah. And it's like, it's not only is it running a clinic, right?
664
00:39:51,072 --> 00:39:53,752
But the home assistant stuff is really integrated into the function of the home
665
00:39:53,752 --> 00:39:58,072
to a degree that like prevents freezing and, and, and other damage occurring.
666
00:39:58,272 --> 00:39:59,352
So it's pretty significant.
667
00:39:59,912 --> 00:40:04,492
Uh, yeah, I think I probably was underdoing it. Yeah, I think I might've been.
668
00:40:05,112 --> 00:40:08,792
And yeah, it did need, it did need a better solution. I would be curious to
669
00:40:08,792 --> 00:40:10,632
know if maybe there was a better way to go though.
670
00:40:10,792 --> 00:40:13,352
So, and how people are doing it. Always love to hear that.
671
00:40:13,652 --> 00:40:17,112
I'm not opposed to coming up with a better way. Could always make for a good segment.
672
00:40:19,816 --> 00:40:23,836
All right. Well, check this out. Linux Unplugged has been here for over 12 years.
673
00:40:23,996 --> 00:40:25,616
And I think I figured out why.
674
00:40:25,816 --> 00:40:29,016
Right. We focus on a few things. And I think this is one of our strengths.
675
00:40:29,356 --> 00:40:32,236
Real use cases for Linux. We can get value out of it.
676
00:40:32,636 --> 00:40:35,896
Free software that's actually free. And we talk about the differences there.
677
00:40:36,196 --> 00:40:40,636
And we try to focus on self-hosting that's practical and just works and not
678
00:40:40,636 --> 00:40:44,736
like the hype stuff. And I think you'll also find that we have honest conversations
679
00:40:44,736 --> 00:40:48,016
that try to help you make sense of the big shifts in the Linux landscape.
680
00:40:48,016 --> 00:40:49,896
And you can look over the 12-year history of the show.
681
00:40:50,751 --> 00:40:55,671
And we don't chase the outrage. We don't chase the hype. We don't go for the drama clickbait.
682
00:40:56,191 --> 00:41:00,491
We just try to focus on the signal there. And so when you support the Unplugged
683
00:41:00,491 --> 00:41:03,551
program, you're keeping something that's a bit rare alive.
684
00:41:03,771 --> 00:41:07,171
It's focused, thoughtful Linux podcasts that tries to stay in its lane,
685
00:41:07,351 --> 00:41:10,651
respects your time, and treats the community like adults.
686
00:41:11,311 --> 00:41:14,031
And that's probably not as common as it should be.
687
00:41:14,511 --> 00:41:19,031
So this here show, it runs on value for value, time, talent, or treasure.
688
00:41:19,471 --> 00:41:22,971
listening and sharing the show, spreading the word, time, participating in the
689
00:41:22,971 --> 00:41:25,191
community, helping create maybe show swag.
690
00:41:25,491 --> 00:41:28,011
That's time. It could be a little bit of talent in there too, right?
691
00:41:28,351 --> 00:41:32,571
Also your feedbacks, corrections, things like that. Also helpful.
692
00:41:32,731 --> 00:41:33,931
And of course, treasure.
693
00:41:34,751 --> 00:41:38,571
Boosts, membership, direct support at meetups, all of those things make a big
694
00:41:38,571 --> 00:41:40,451
difference right now. The reason why I'm talking to you right now is because
695
00:41:40,451 --> 00:41:41,671
we don't have a sponsor for this slot.
696
00:41:41,911 --> 00:41:46,831
So every bit helps the show continue and ideally thrive and grow.
697
00:41:47,431 --> 00:41:51,531
Better coverage, bigger experiments, more room to explore what's next before
698
00:41:51,531 --> 00:41:54,871
it's obvious without all the hype. I mean, look at the history of the show.
699
00:41:55,151 --> 00:41:58,811
So if it's helped you understand Linux better or avoid bad tech decisions or
700
00:41:58,811 --> 00:42:01,571
feel more confident about running your own systems, consider supporting the
701
00:42:01,571 --> 00:42:04,071
show to keep that going. You can send us a boost.
702
00:42:04,331 --> 00:42:07,771
You can become a core contributor or a Jupyter.party member.
703
00:42:07,791 --> 00:42:11,951
Or, of course, if you use the promo code bootleg while it lasts,
704
00:42:12,051 --> 00:42:12,911
you get it at a great price.
705
00:42:13,351 --> 00:42:18,131
That's linuxunplugged.com membership to support this show directly or jupiter.party.
706
00:42:18,131 --> 00:42:20,391
You get the perks and you keep the show going.
707
00:42:20,511 --> 00:42:23,711
And of course you can send us a boost to support each episode directly.
708
00:42:24,031 --> 00:42:26,931
Thank you everybody who does that. It makes all the difference.
709
00:42:30,051 --> 00:42:35,131
Well, AJ wrote in this week, long-time listener, Mobile Linux Survivor reporting
710
00:42:35,131 --> 00:42:37,071
in here. Hey, Chris, JB Crew.
711
00:42:37,571 --> 00:42:41,551
Been a long-time member, watching and listening since about the Matt Hartley
712
00:42:41,551 --> 00:42:44,711
era. So not quite a Lunduk graybeard, but almost.
713
00:42:46,371 --> 00:42:51,671
I'm extremely jaded about Linux phones, and for some good reasons.
714
00:42:52,371 --> 00:42:56,591
I backed the Librem 5, lawyers got involved there, and still no phone.
715
00:42:56,591 --> 00:43:00,851
I owned a PinePhone and a PinePhone Pro, which were underwhelming at best.
716
00:43:01,031 --> 00:43:05,011
So I assume we're all pretty burned on mobile Linux by now.
717
00:43:05,391 --> 00:43:10,031
But then I heard about the FLX1. Last spring, I learned about it.
718
00:43:10,151 --> 00:43:12,711
It's the FLX1 from Fury Labs.
719
00:43:12,991 --> 00:43:17,091
Didn't expect much there, but I believe in the idea of mobile Linux.
720
00:43:17,931 --> 00:43:22,311
So I backed it. A month or two later, though, the FLX1 was cancelled.
721
00:43:22,651 --> 00:43:25,251
So cue that purism-era PTSD.
722
00:43:26,191 --> 00:43:29,151
But here's where it gets a little weird in a good way.
723
00:43:29,411 --> 00:43:34,371
Fury Labs announced a replacement device, the FLX1S for slim.
724
00:43:34,931 --> 00:43:40,011
It offers refunds or a spot in the new queue. And so I stayed in,
725
00:43:40,231 --> 00:43:42,351
fully expecting another disappointment.
726
00:43:43,440 --> 00:43:48,800
But then they delivered. My FLX1S just arrived January 2nd, and I've been daily
727
00:43:48,800 --> 00:43:50,280
driving it since that weekend.
728
00:43:50,720 --> 00:43:54,180
Not testing, not tinkering, but daily driving it.
729
00:43:54,460 --> 00:43:58,480
So here's a little report. Does it actually work? Yes, calls seem to work.
730
00:43:58,580 --> 00:44:02,120
SMS and MMS, mobile data, GPS, most Bluetooth works.
731
00:44:02,460 --> 00:44:05,420
Many Android apps also via WayDroid.
732
00:44:05,780 --> 00:44:11,060
They use a fork called Andromeda. The battery lasts about a full day with normal
733
00:44:11,060 --> 00:44:15,020
use as well. The software stack, as I understand it, is FOSH,
734
00:44:15,480 --> 00:44:19,780
customized Debian base built on the Helium project.
735
00:44:20,240 --> 00:44:23,100
Those details might be slightly off, but that's the gist I understand.
736
00:44:23,340 -->
00:44:27,580
Is it perfect? Nope. Is it real? Shockingly, yes, it's real.
737
00:44:28,040 --> 00:44:31,860
There's a compromise, of course, but they're shrinking pretty quickly.
738
00:44:32,080 --> 00:44:35,400
Some issues get fixed day to day, not month to month.
739
00:44:35,700 --> 00:44:39,760
I even submitted a bug fix that'll ship by default on the next release.
740
00:44:39,760 --> 00:44:42,900
that alone felt wildly refreshing compared
741
00:44:42,900 --> 00:44:45,600
to my previous experiences so why am i
742
00:44:45,600 --> 00:44:49,980
reaching out well i have zero affiliation no financial interest and no incentives
743
00:44:49,980 --> 00:44:55,260
i just genuinely am a happy customer which feels rare enough to mention fury
744
00:44:55,260 --> 00:45:00,140
labs has restored some of my hope in mobile linux they're active in the matrix
745
00:45:00,140 --> 00:45:05,040
room with a small but engaged community and i really think you should get your hands on a device,
746
00:45:05,560 --> 00:45:10,120
maybe invite someone from that team onto the show and talk about what they did
747
00:45:10,120 --> 00:45:11,740
differently this time around.
748
00:45:12,220 --> 00:45:17,440
Oh, that's an interesting suggestion. Boy, I would appreciate a contact if you have one, AJ.
749
00:45:17,840 --> 00:45:21,580
That is a good report, right? Isn't it nice to hear that possibly a Linux phone
750
00:45:21,580 --> 00:45:23,820
out there that people are happy with and gets the basics done?
751
00:45:23,960 --> 00:45:28,120
And I think about how much I could do in a web browser if I didn't have an app.
752
00:45:28,280 --> 00:45:32,020
And I start to think maybe it's not crazy maybe it's maybe the dream is possible
753
00:45:32,020 --> 00:45:36,600
aj makes me believe again faith restored thank you aj appreciate that report
754
00:45:36,600 --> 00:45:40,380
great example of value contribute to the show right there with a in the field
755
00:45:40,380 --> 00:45:43,640
report another great example of course is la boost,
756
00:45:48,212 --> 00:45:52,332
And Daja's back with a row of McDucks as our baller booster this week.
757
00:45:55,852 --> 00:45:58,972
And he writes, I just wanted to share a little Linux and self-hosted success
758
00:45:58,972 --> 00:46:01,212
story. Oh, here we go. I love these.
759
00:46:01,272 --> 00:46:01,372
Yeah.
760
00:46:01,932 --> 00:46:04,892
Thanks to what I've learned from the crew, our community, and our community
761
00:46:04,892 --> 00:46:09,012
over the last six years, I was able to migrate off of a GCP,
762
00:46:09,292 --> 00:46:14,592
oh, a Google Cloud, to a combo of our own Infra and Colo, resulting in monthly
763
00:46:14,592 --> 00:46:16,172
savings of this boost amount.
764
00:46:16,552 --> 00:46:16,992
Wow.
765
00:46:17,932 --> 00:46:23,732
But it was in dollars instead of sats that's a big number and all foss you guys
766
00:46:23,732 --> 00:46:27,712
are awesome thank you love to hear that that that really
you know that kind
767
00:46:27,712 --> 00:46:30,872
of stuff makes our day also regarding the on-site you guys did at his clinic
768
00:46:30,872 --> 00:46:34,792
it was super interesting and it's always those small gotchas that get you.
769
00:46:34,792 --> 00:46:36,592
Ain't that the truth it's always networking.
770
00:46:36,592 --> 00:46:40,312
That is such a great boost also i mean because it's just really great to hear
771
00:46:40,312 --> 00:46:43,952
that we made a little difference there but also uh appreciate the signal on
772
00:46:43,952 --> 00:46:47,152
that type of topic it's the first time we've ever done something like that so
773
00:46:47,152 --> 00:46:48,472
we always appreciate the feedback.
774
00:46:48,472 --> 00:46:51,832
Optical gre comes in.
775
00:46:51,832 --> 00:46:52,952
With 21.
776
00:46:52,952 --> 00:46:55,652
703 satoshis,
777
00:46:58,352 --> 00:47:03,252
i forgot where i live so i need west to check his map for me and then relay
778
00:47:03,252 --> 00:47:07,552
that information to brent so he can help me with the many unfinished projects
779
00:47:07,552 --> 00:47:09,152
if he ever works his way through here.
780
00:47:09,152 --> 00:47:13,192
Uh-oh here we go don't tell me with.
781
00:47:13,192 --> 00:47:13,812
A good time.
782
00:47:13,812 --> 00:47:16,952
Did you uh yes actually oh i.
783
00:47:16,952 --> 00:47:17,772
Keep it in my back pocket.
784
00:47:17,772 --> 00:47:21,452
There it is nice okay watch out watch out i don't want that on camera because
785
00:47:21,452 --> 00:47:25,392
that did sharpen the edges yeah all right do we have a location yes.
786
00:47:25,392 --> 00:47:28,792
We do uh 21703 looks like,
787
00:47:29,970 --> 00:47:33,630
A postal code from Frederick County, Maryland.
788
00:47:33,970 --> 00:47:34,270
Oh.
789
00:47:34,850 --> 00:47:35,170
Wow.
790
00:47:35,350 --> 00:47:35,750
There you go, Brent.
791
00:47:36,030 --> 00:47:38,450
Well, what you have to do with these messages is also tell me,
792
00:47:38,530 --> 00:47:42,190
you know, some temptations as to why I should come through the area. Well, mostly food.
793
00:47:42,210 --> 00:47:43,690
Well, you swing by on your way to the Capitol.
794
00:47:43,950 --> 00:47:46,350
If they have gluten-free pizza, then you got me.
795
00:47:46,990 --> 00:47:50,350
Just, he has a few allergies he'd like you to know about. If you consider those
796
00:47:50,350 --> 00:47:52,930
and work them into your boost, there's probably a good chance you'll stop by.
797
00:47:53,030 --> 00:47:56,450
Oh, and if you have a plug, outdoor plug, he can make 120 work.
798
00:47:56,950 --> 00:48:00,170
If you have good cat snacks, that's usually a big help.
799
00:48:00,390 --> 00:48:02,230
Liking cats helps, too. That is true.
800
00:48:03,150 --> 00:48:09,130
Well, Gene Bean sent in, this is just a little row of ducks, 2,222.
801
00:48:09,810 --> 00:48:14,690
He says, can you share that Nix config for the clinic? I'd love to get some ideas off there.
802
00:48:14,830 --> 00:48:18,530
We could, yeah. I think we would probably just want to do a quick sanitization
803
00:48:18,530 --> 00:48:22,650
check, since it is for a clinic and all of that. But I think we could give a
804
00:48:22,650 --> 00:48:23,370
look at that after the show.
805
00:48:23,470 --> 00:48:23,670
Totally.
806
00:48:23,670 --> 00:48:27,050
And if it passes the sniff test, we'll just put it in the show notes for this
807
00:48:27,050 --> 00:48:29,350
episode. Does that make sense? Yeah.
808
00:48:30,210 --> 00:48:33,150
So I guess the answer is, if the answer is yes, it'll be in the show notes,
809
00:48:33,230 --> 00:48:34,870
Gene Bean. Good question.
810
00:48:35,590 --> 00:48:36,910
Show notes for 651.
811
00:48:37,070 --> 00:48:41,150
You know, I've talked, yeah, linuxonplugged.com slash 651. I've thought about this.
812
00:48:41,750 --> 00:48:45,970
There's not a lot that's going to be revealed because anything that's like a
813
00:48:45,970 --> 00:48:49,750
secret gets stored outside the main config that goes in the repository.
814
00:48:51,410 --> 00:48:56,290
But, it is the type of thing that if I had access to someone's network,
815
00:48:56,290 --> 00:48:59,770
I would use the hell out of this to get everywhere I wanted to go.
816
00:49:00,190 --> 00:49:04,090
And I just, like, this for me, when I, I don't mean to be this guy,
817
00:49:04,170 --> 00:49:08,330
but like when I was hired to do penetration testing, this, I would have loved
818
00:49:08,330 --> 00:49:09,730
a map like this. I would have.
819
00:49:10,892 --> 00:49:14,652
This would be like, oh, you just gave me the job for easy, free, you know, basically.
820
00:49:16,152 --> 00:49:18,732
First I'll own his couple of pie holes and then I will.
821
00:49:18,932 --> 00:49:23,292
Right. It's really, well, it just gives you time to research and it's easier
822
00:49:23,292 --> 00:49:26,232
than ever to drop these configs into a machine and say, hey,
823
00:49:26,312 --> 00:49:29,612
machine, what's the first thing I could pick on, right? Like you got to think
824
00:49:29,612 --> 00:49:31,252
about the tools that are available to people now.
825
00:49:31,672 --> 00:49:36,232
And so it crosses my mind that there is a level of information that's being exposed.
826
00:49:36,852 --> 00:49:42,232
And so I have some consideration there. But it relies on breaking into the infrastructure.
827
00:49:42,512 --> 00:49:47,352
And then most of what gets exposed is just internal non-routable IP addresses
828
00:49:47,352 --> 00:49:50,972
and things like that, or perhaps where secrets get stored and whatnot.
829
00:49:51,352 --> 00:49:55,332
But it's something I think about, and I would love the audience's thoughts about it as well.
830
00:49:55,392 --> 00:49:58,372
And if you guys are concerned, I know there's a culture around sharing your
831
00:49:58,372 --> 00:50:01,472
Nix configs and your Ansible configs, and I like that. And I use that.
832
00:50:01,472 -->
00:50:03,032
We've benefited a lot from it.
833
00:50:03,452 --> 00:50:07,172
And I know I could do a sanitized version. So, I mean, maybe we'll try that.
834
00:50:07,172 --> 00:50:11,152
But then I'm not – I prefer if I'm going to put it up on GitHub,
835
00:50:11,492 --> 00:50:15,492
I would prefer to actually use it.
836
00:50:16,492 --> 00:50:21,032
You know, like – and then it's – anyways. Good question. Check the show notes,
837
00:50:21,132 --> 00:50:24,452
Gene, and I would love people's feedback on that. Thank you very much.
838
00:50:25,372 --> 00:50:29,832
Is it my turn now? I don't remember. Sifeseeker comes in with – I got all distracted.
839
00:50:30,012 --> 00:50:33,272
Comes in with 2,500 sats.
840
00:50:35,319 --> 00:50:38,499
Hi guys, I've been kicking around the idea of a NixOS router,
841
00:50:38,699 --> 00:50:40,279
and an example would be great, Leo, there you go.
842
00:50:41,879 --> 00:50:47,899
Would you be willing to share your config? The router config is interesting, right? It's in there.
843
00:50:48,019 --> 00:50:52,899
I will also mention that Bearded Tech in our community has a really cool NixOS-based router project.
844
00:50:53,239 --> 00:50:55,539
And if you're actually thinking about using it for your home router...
845
00:50:55,539 --> 00:50:56,779
Yeah, this might be something to consider.
846
00:50:56,819 --> 00:50:58,019
That might be something worth looking at.
847
00:50:58,019 --> 00:51:00,179
We were kind of doing a bunch of stuff all at the same time,
848
00:51:00,319 --> 00:51:03,419
so we took a peek, but we kind of wanted to start a little more minimal and
849
00:51:03,419 --> 00:51:06,279
work our way up. But it looks great, especially if you just want,
850
00:51:06,379 --> 00:51:08,699
like, a standalone router that is NixOS powered.
851
00:51:08,879 --> 00:51:14,819
Yes. And you've got to remember, we were building something that was a VM first, VM server first.
852
00:51:15,059 --> 00:51:17,159
It wasn't going to be the router first.
853
00:51:17,359 --> 00:51:21,539
Yeah, yeah, right. Exactly. Yeah. All right. But, yeah, all right.
854
00:51:21,639 --> 00:51:25,099
We'll take a look at that, Cypher. Thank you very much. I guess there's some demand.
855
00:51:25,519 --> 00:51:28,079
Hybrid Sarcasm comes in with 10,000 SATs.
856
00:51:33,668 --> 00:51:36,068
You asked for some feedback regarding actual budget.
857
00:51:36,208 --> 00:51:36,328
Yeah.
858
00:51:36,528 --> 00:51:41,048
It's been a pretty good replacement for you need a budget with spousal approval so far.
859
00:51:41,688 --> 00:51:44,888
That's $9 a month I don't have to spend on a cloud service.
860
00:51:45,148 --> 00:51:49,368
You'll also appreciate that the actual devs have a sustainable funding model
861
00:51:49,368 --> 00:51:52,848
for their core contributors, and they are looking to expand it to others.
862
00:51:53,048 --> 00:51:54,588
And then we've got a link we'll put in the show notes.
863
00:51:54,788 --> 00:51:56,528
Oh, interesting. I'm looking. I'm trying. There it is. Yeah.
864
00:51:56,628 --> 00:51:58,688
So they have in their documentation here. Hmm.
865
00:51:59,408 --> 00:52:04,428
Thank you. I did not know that. That's a good little bit of information there. I appreciate that, Mr.
866
00:52:04,448 --> 00:52:04,488
Zark.
867
00:52:04,588 --> 00:52:05,328
I appreciate the report.
868
00:52:05,328 --> 00:52:07,588
Are you saying those are the actual, actual devs?
869
00:52:08,568 --> 00:52:09,868
No, the actual, actual, actual.
870
00:52:10,008 --> 00:52:10,348
No, yeah.
871
00:52:10,388 --> 00:52:16,148
Oh, actually, okay. Well, adversaries came in with 8,441 sats.
872
00:52:20,368 --> 00:52:24,108
Adversaries responding to our question last week, Chris, you were asking for
873
00:52:24,108 --> 00:52:26,688
Wi-Fi analyzers for Android.
874
00:52:27,568 --> 00:52:31,088
adversaries says unify makes a great wi-fi analyzer
875
00:52:31,088 --> 00:52:34,208
app called wi-fi man it doesn't require unify
876
00:52:34,208 --> 00:52:37,448
gear to work it just uses your phone's radios and
877
00:52:37,448 --> 00:52:41,588
i can second this one this is the application i've been using for about the
878
00:52:41,588 --> 00:52:47,388
last year i used it just this week to that's good to know hey hey you didn't
879
00:52:47,388 --> 00:52:50,428
give me time to answer your question nor did you ask me while you were working
880
00:52:50,428 --> 00:52:57,088
on this project so oh wow dude anyways it's fantastic i use it just this week uh to I fixed my parents'
881
00:52:57,228 --> 00:53:00,248
Wi-Fi, and it's got some sweet features.
882
00:53:00,388 --> 00:53:03,208
So I would say put this on your phone, play with it.
883
00:53:03,308 --> 00:53:07,808
It's pretty amazing. It took me a few uses to discover all of the different
884
00:53:07,808 --> 00:53:10,528
crazy features that are hidden in it. It's really quite good.
885
00:53:10,968 --> 00:53:14,628
This makes you the buddy that shows up with a water hose after I put the fire
886
00:53:14,628 --> 00:53:15,888
out. You realize that, right?
887
00:53:16,108 --> 00:53:16,468
You're welcome.
888
00:53:16,768 --> 00:53:18,688
All right. That makes you – that's what you – I.
889
00:53:18,688 --> 00:53:19,468
Could start a new fire.
890
00:53:20,228 --> 00:53:26,708
No doubt we will. No doubt about that at all. Anonymous comes in with 2,021 sats.
891
00:53:27,468 --> 00:53:31,528
No message, just value. Thank you very much. And then Tomato comes in with a row of duckles.
892
00:53:32,875 --> 00:53:36,675
And writes, I loved this old network segment. I'd be curious to hear if Brent
893
00:53:36,675 --> 00:53:38,075
started to automate his van yet.
894
00:53:38,275 --> 00:53:41,215
Mine is completely unautomated. I'm not sure where to start.
895
00:53:41,655 --> 00:53:43,655
Oh, well, he needs to start with sensors, right, Brent?
896
00:53:44,195 --> 00:53:48,975
Sensors is great. Yeah, I did the opposite this
week and pulled my lithium batteries
897
00:53:48,975 --> 00:53:54,415
out of my van. So I've unautomated everything only because it got really,
898
00:53:54,515 --> 00:53:55,555
really, really, really cold.
899
00:53:55,775 --> 00:53:58,915
And this is not very good for them. So I feel like this week I went backwards.
900
00:53:58,915 --> 00:54:03,355
but I'm going to kind of build all the automation here in the workshop,
901
00:54:03,355 --> 00:54:07,595
just as winter's here, then I can just plunk it in the van, you know?
902
00:54:08,315 --> 00:54:13,415
But I would say, Chris, you've got much more opinions on this than I do,
903
00:54:13,515 --> 00:54:16,655
but I would say start with the problems that you feel like you want to solve
904
00:54:16,655 --> 00:54:18,475
or have visibility into, right?
905
00:54:18,555 --> 00:54:22,255
If you want exterior temperatures versus interior temperatures,
906
00:54:22,575 --> 00:54:23,795
and that's really important to you, start there.
907
00:54:24,095 --> 00:54:27,795
If you want to, I don't know, have some other solution to a problem,
908
00:54:27,795 --> 00:54:29,435
That's always the best place to start.
909
00:54:29,715 --> 00:54:34,015
And plus one sensors. And then if you really want to see what's capable and
910
00:54:34,015 --> 00:54:37,655
way, way far out there, check out smartyvan.com.
911
00:54:38,295 --> 00:54:44,795
He's also a YouTuber and he has created some really inspired automations around van living.
912
00:54:44,955 --> 00:54:49,655
I mean, absolutely high end tech stuff that you could build from for years.
913
00:54:49,655 --> 00:54:53,895
He's also released some code. He has examples and automations and video tutorials
914
00:54:53,895 --> 00:55:01,135
and all of that. So it's smartyvan.com, S-M-A-R-T-Y, van.com.
915
00:55:01,235 --> 00:55:02,475
And you get some good inspiration there.
916
00:55:02,595 --> 00:55:07,975
I think my next step, if you're curious, is likely getting some visibility and
917
00:55:07,975 --> 00:55:11,475
automation around keeping these batteries charged and healthy.
918
00:55:12,290 --> 00:55:16,250
One of them is how to keep them warm while they're charging in the winter or,
919
00:55:16,250 --> 00:55:19,050
you know, in the after winter season.
920
00:55:19,530 --> 00:55:23,270
So that's the main problem I have that I'm going to solve that will get me,
921
00:55:23,430 --> 00:55:28,890
you know, some open hardware experience and also diving more into what Home
922
00:55:28,890 --> 00:55:31,570
Assistant can do to automate all this. So that's my next step.
923
00:55:31,710 --> 00:55:34,010
But write in and let me know what problem you're solving.
924
00:55:34,310 --> 00:55:37,630
I would also add, like, if you want something to rabbit hole into for a while
925
00:55:37,630 --> 00:55:42,050
before you get into all this, go learn the ESP platform. So that is a skill
926
00:55:42,050 --> 00:55:43,750
that will pay dividends years.
927
00:55:44,050 --> 00:55:44,850
And relays, relays.
928
00:55:44,970 --> 00:55:45,110
Yeah.
929
00:55:45,430 --> 00:55:46,210
ESVs and relays.
930
00:55:46,690 --> 00:55:49,150
And the little sensors and there's kits you can get on, you know,
931
00:55:49,230 --> 00:55:51,990
the big box websites for super cheap and all of that.
932
00:55:52,110 --> 00:55:53,310
And buy some epoxy too.
933
00:55:54,430 --> 00:55:55,310
While you're at it.
934
00:55:56,710 --> 00:56:00,990
All right. Thank you, everybody who boosted the show. We do appreciate you very much.
935
00:56:01,070 --> 00:56:05,330
And, of course, shout out to our SAT streamers as well. We had 26 of you stream
936
00:56:05,330 --> 00:56:10,210
sats, and collectively you came in with 26,866 sats, which does technically
937
00:56:10,210 --> 00:56:13,370
make our streamers the baller booster again this week. Thank you, everybody.
938
00:56:13,590 --> 00:56:18,810
When you combine that with our boosters, we raised a total of 109,354 sats.
939
00:56:19,010 --> 00:56:22,930
Pretty humble, but we're very appreciative and gives us an opportunity to make
940
00:56:22,930 --> 00:56:24,750
our birthday episode a banger.
941
00:56:27,590 --> 00:56:31,370
There's real, real easy ways to boost in these days. Fountain FM is making it
942
00:56:31,370 --> 00:56:36,290
easier and easier, including making it just all kind of dollar-based, simple stuff.
943
00:56:36,410 --> 00:56:39,470
And, of course, there's the entire awesome self-hosted infrastructure.
944
00:56:39,470 --> 00:56:41,190
You can find that when you go
945
00:56:41,190 --> 00:56:44,290
to newpodcastapps.com. You'll go down that rabbit hole. You get AlbiHub.
946
00:56:44,450 --> 00:56:46,830
It's really awesome. And, of course, we have the membership program,
947
00:56:47,350 --> 00:56:52,330
linuxunplugged.com slash membership, or jupiter.party for the whole dang network.
948
00:56:54,245 --> 00:56:56,245
All right. Would you guys like a few picks?
949
00:56:56,585 --> 00:56:58,145
Yeah, what'd you get in your bag today?
950
00:56:58,345 --> 00:57:03,445
Well, you've heard me mention my Hypervibe, which is a NixOS-based Hyperland
951
00:57:03,445 --> 00:57:05,545
desktop and still rocking it.
952
00:57:05,605 --> 00:57:09,365
Got it running on three machines these days and it's in a great state and I like it a lot.
953
00:57:09,525 --> 00:57:12,985
But perhaps you are an Arch person.
954
00:57:13,585 --> 00:57:15,845
Well, Rich Arch has a Hypervibe spin.
955
00:57:16,045 --> 00:57:19,925
They say we at Rich Arch Project are re-releasing our Hypervibe spin.
956
00:57:20,205 --> 00:57:26,005
We now have taken the Hypervibe configs and enriched them with the Noctelis shell on Hyperland.
957
00:57:26,585 --> 00:57:30,605
You can try it in a VM, and it includes some screenshots, or some instructions
958
00:57:30,605 --> 00:57:32,905
and a screenshot, which we'll put a link to in the show notes.
959
00:57:33,925 --> 00:57:37,665
It's better looking than the way I
have it configured. I'll tell you that. It's really nice.
960
00:57:37,725 --> 00:57:42,645
So now you're going to re-Nixify, Hypervibe-ify, the rich Arch Hypervibe-based config?
961
00:57:42,805 --> 00:57:47,065
I like the way you think. You basically start with a base Linux,
962
00:57:47,605 --> 00:57:50,025
or a base Arch ISO, just base install.
963
00:57:50,545 --> 00:57:53,345
And then he has some kickoff scripts that you can curl onto that basic system
964
00:57:53,345 --> 00:57:58,005
and turn it into a Hypervibe desktop based off of what I set up to run on Nix.
965
00:57:58,225 --> 00:58:01,105
But with Arch. Kind of neat. Thank you, Rich, for sending that in.
966
00:58:01,225 --> 00:58:01,445
That's great.
967
00:58:01,625 --> 00:58:05,245
It's beautiful. It's beautiful. And then I've got one that.
968
00:58:06,545 --> 00:58:07,585
This looks really nice.
969
00:58:07,905 --> 00:58:10,745
This is nice to see. It's good to have another one of these.
970
00:58:11,005 --> 00:58:14,165
I've talked about Junction before. Now we're going to talk about Switchyard,
971
00:58:14,405 --> 00:58:19,585
a modern rules-based URL launcher that replaces your default browser.
972
00:58:20,025 --> 00:58:24,245
So wrap your noodle around this. Instead of having one browser as your default,
973
00:58:24,485 --> 00:58:27,225
you set switchyard as the default browser.
974
00:58:27,505 --> 00:58:32,205
And then when you click a link, it brings up a little window and it lets you
975
00:58:32,205 --> 00:58:34,505
choose which browser you want to open in.
976
00:58:34,725 --> 00:58:38,765
But on top of that, they have added a really nice graphical interface,
977
00:58:38,925 --> 00:58:43,425
a GTK graphical interface, where you can have rules to just automatically send
978
00:58:43,425 --> 00:58:45,505
some URLs right to a particular browser.
979
00:58:45,645 --> 00:58:49,665
And this is exactly how I work. And this is why I really appreciate this Because
980
00:58:49,665 --> 00:58:51,765
there's some stuff I always open in Firefox.
981
00:58:52,125 --> 00:58:55,265
There's one site and only one site I use Brave for right now.
982
00:58:55,385 --> 00:58:57,145
And then there's other stuff I open in Zen.
983
00:58:58,579 --> 00:59:02,259
And it's very, it's always that stuff. So this is really, really great.
984
00:59:02,459 --> 00:59:05,779
It's a super fast app and it has a simple configuration.
985
00:59:05,839 --> 00:59:10,019
If you do want to do it by text, they have a flat pack and a Nixflake ready
986
00:59:10,019 --> 00:59:12,359
to go. So I thought I might get your approval on that one too.
987
00:59:12,539 --> 00:59:16,659
Oh yeah, absolutely. And it's written in Go, GPL 3.0.
988
00:59:16,819 --> 00:59:20,479
Yeah. So this is so nice if you do live the multi-browser lifestyle.
989
00:59:20,859 --> 00:59:26,119
And I do. And I probably would say Firefox is 90% everything.
990
00:59:26,119 --> 00:59:28,979
but then there's those, or maybe like if I'm going to do a Google Meet,
991
00:59:29,099 --> 00:59:30,079
I might actually do that in Chrome.
992
00:59:30,479 --> 00:59:34,599
And I maybe don't use Google Chrome for literally anything else on that machine,
993
00:59:34,619 --> 00:59:35,899
but I use it for Google Meet.
994
00:59:36,339 --> 00:59:39,519
And it's nice to have something. I just click a link and switch art, it'll send it to that.
995
00:59:39,619 --> 00:59:42,759
But if I don't have any rules set, it gives you a really lean,
996
00:59:42,859 --> 00:59:47,059
mean, fast UI and you big icons and you just select the browser you do want
997
00:59:47,059 --> 00:59:49,939
to open and it sends a link to that browser. So it's, ha ha.
998
00:59:50,179 --> 00:59:52,739
I think especially, right, they kind of keyed in on work or other stuff,
999
00:59:52,839 --> 00:59:55,179
but even just maybe you're doing, you're in a mode where you're doing show notes.
1000
00:59:55,179 --> 00:59:58,779
You want to make sure you, you know, you're clinking some of the Brent sends.
1001
00:59:58,839 --> 00:59:59,879
You want it to open the right spot.
1002
01:00:00,059 --> 01:00:02,419
Yeah. Something that's in private browsing mode for sure.
1003
01:00:02,639 --> 01:00:04,579
Well, yeah, no JavaScript either.
1004
01:00:04,859 --> 01:00:05,179
Containerized.
1005
01:00:05,359 --> 01:00:05,679
Definitely.
1006
01:00:07,232 --> 01:00:09,772
All right. Well, that's pretty much the end. I just want to remind everybody
1007
01:00:09,772 --> 01:00:10,792
that the meetup page is up.
1008
01:00:10,872 --> 01:00:13,592
If you're going to be in the Pasadena area around March 5th,
1009
01:00:13,612 --> 01:00:17,592
we'll be at Planet Nixon scale and hanging out with our buddies from Phlox.
1010
01:00:17,692 --> 01:00:20,012
We'd love to see you there. Meetup.com slash Jupiter Broadcasting.
1011
01:00:20,012 --> 01:00:23,252
We'll get the details locked in soon for all of that.
1012
01:00:23,432 --> 01:00:26,352
I'm very much looking forward to it. It's going to be nice, especially as it's
1013
01:00:26,352 --> 01:00:30,572
very cold right now. I'm picturing the nice sunshine. It's a beautiful time to be in Pasadena.
1014
01:00:30,812 --> 01:00:31,312
Seeing a wonderful audience.
1015
01:00:31,632 --> 01:00:36,152
Mm-hmm. Mm-hmm. Good crew down there, too. Wes, is there some pro tips we could
1016
01:00:36,152 --> 01:00:37,132
leave with them? you know things
1017
01:00:37,132 --> 01:00:40,912
where they could get more data more information around the show like.
1018
01:00:40,912 --> 01:00:42,872
Some sort of enriched xml file.
1019
01:00:42,872 --> 01:00:43,972
Yeah something links.
1020
01:00:43,972 --> 01:00:45,752
To uh text and json files.
1021
01:00:45,752 --> 01:00:46,532
Could be yeah.
1022
01:00:46,532 --> 01:00:47,452
With like chapter.
1023
01:00:47,452 --> 01:00:51,512
Information and transcript information yeah could have all of that.
1024
01:00:51,512 --> 01:00:54,432
Like an srt for however you want to consume this.
1025
01:00:54,432 --> 01:00:57,612
It's that if you've got a um podcast client there's more and more of them that
1026
01:00:57,612 --> 01:01:00,392
supports transcripts we have that in the feed for you and of course if you have
1027
01:01:00,392 --> 01:01:03,612
a podcasting toodle client you get all kinds of stuff like the cloud chapters
1028
01:01:03,612 --> 01:01:08,512
like the live item entry pending information and a whole bunch of good stuff.
1029
01:01:08,672 --> 01:01:09,752
And of course we are live.
1030
01:01:12,932 --> 01:01:16,532
Yeah, we love it. If you make it a Tuesday on a Sunday, join us Sunday at 10
1031
01:01:16,532 --> 01:01:20,432
a.m. Pacific, 1 p.m. Eastern, jupiterbroadcasting.com slash calendar for your time.
1032
01:01:21,072 --> 01:01:23,432
If you want to, I don't know, read about what we talked about.
1033
01:01:23,592 --> 01:01:24,572
You want more show? I don't know.
1034
01:01:25,092 --> 01:01:31,852
Linuxunplugged.com. This was episode, geez, 651. So Linuxunplugged.com slash 651.
1035
01:01:32,132 --> 01:01:36,432
We get together every Sunday with our Mumble room. That information's on our website as well.
1036
01:01:36,732 --> 01:01:40,112
You can get in there, get a low latency Opus stream. We tell you about it. Try it out.
1037
01:01:40,432 --> 01:01:44,192
And last but not least, we have that Matrix room going 24-7.
1038
01:01:44,392 --> 01:01:47,352
You can find details to that. It's a great community. And if you're already
1039
01:01:47,352 --> 01:01:48,812
in the Federation, why not join us?
1040
01:01:49,092 --> 01:01:51,592
Thanks so much for joining us on this week's episode of Unplugged.
1041
01:01:51,692 --> 01:01:53,612
See you right back here next Sunday!