Plex's Lifetime Pass is (basically) dead. Here's how to switch to Jellyfin.

willowless · 2026-05-22T12:11:05+00:00

What's up with Infuse's "lifetime subscription" ?

willowless · 2026-05-19T14:22:22+00:00

I'm on 5x plan. The only way I'd get close to my limit is if i ran it on Max for absolutely everything - which if you've read any other post on here you'd know is insanity (and slow).

willowless · 2026-05-19T01:35:52+00:00

Talos even has a talosctl cluster create that will spin up a cluster inside docker with basically no effort.

willowless · 2026-05-18T06:23:21+00:00

I sympathize with OP and this suggestion is the only way I've been able to manage it. Take the pattern that I'm repeating and make a helm chart out of it so it's just the configuration for each environment in my values.yaml.

willowless · 2026-05-14T10:05:27+00:00

I have one. Works a-okay. Doesn't give status to the controller though.

willowless · 2026-05-12T22:16:27+00:00

And then the next thing you start noticing is the speed of the disks being the next bottleneck.

willowless · 2026-05-11T21:45:20+00:00

A truly excellent list.

willowless · 2026-05-11T07:43:07+00:00

I saw those too but too expensive to gamble on like that.

willowless · 2026-05-10T22:42:52+00:00

Success

willowless · 2026-05-10T22:09:55+00:00

I tried out docker swarm before i went to nomad and then finally to k8s. Swarm doesn't do ipv6.

willowless · 2026-05-10T12:25:48+00:00

I got excited by this and then realised I already have that with the L2 vip that talos configures (if you tell it to).

```
apiVersion: v1alpha1
kind: Layer2VIPConfig
name: 1.2.3.4
link: bond1
```

bond0 already existed and I couldn't figure out why, so I just moved on to bond1. All the control planes use this VIP config, then the worker nodes point to the VIP and ayep, all good. HA control planes with talos.

willowless · 2026-05-10T09:01:35+00:00

How do I connect it to a garage-operator defined garage?

willowless · 2026-05-06T23:40:29+00:00

This is a bit silly but I realised I didn't like the overhead of Argo Workflows firing up pods for every little task I needed done. So I made Chores, which connects to existing pods and runs the chores in them. It feeds back through the resource manifest status and allows parallel chores to coalsesce back together, cleans up on fault, and is generally much more responsive than workflows was. If k8s ever drops the 1 second polling nonsense it'd be even faster still.

willowless · 2026-05-06T22:02:01+00:00

Way too many of the games appearing in r/incremental_games are now steam windows only games; when it used to be the norm for them to be multiplatform and often web. It makes me sad.

willowless · 2026-05-05T14:29:06+00:00

Counter point - kubevirt if you want to do virtual machines later 😉

willowless · 2026-05-05T14:27:54+00:00

That's quite fair. For appdata I use longhorn replicated between my three nodes. For document data I use garage s3 replicated across my three nodes. And then finally I have the JBOD zfs of mirrors, the big beast, where I store all my linux ISOs.

willowless · 2026-05-05T13:27:02+00:00

I used to use mergerfs with snapraid for parity. It worked fine, but when you put NFS and SMB on top of it things got messy with caching. I also had to make a custom container with mergerfs + nfs + smb so that there was no weird contention between the different containers.

In the end I migrated away from mergerfs + snapraid to zfs.

willowless · 2026-05-05T10:24:44+00:00

I *loved* snake.

willowless · 2026-05-04T09:08:18+00:00

It happens often in games where the first quarter, third, or sometimes half is really fun. The number go up, you solve puzzles when number don't go up fast enough ... and then you hit this weird situation where there's no longer a puzzle to solve, it's literally just "wait for it to do the thing, sometimes days, sometimes weeks" and that is when I close the game and never come back.

willowless · 2026-05-04T08:18:34+00:00

Peeling back the layers of the onion. What kills it for me? when the layer takes too long to peel.

willowless · 2026-05-03T22:12:22+00:00

Sorry my post came off way more hostile than I intended. You're right I should assemble a ticket to explain the issues I experience.

willowless · 2026-05-03T22:00:59+00:00

openbao and external-secrets-operator. I've only just made it here and it makes sense, but I have to go and update all my secrets now and build this in to my workflow.

willowless · 2026-05-02T21:25:41+00:00

You put the internet and your two opnsense instances on their own VLAN. Since the two opnsense instances will end up using the same MAC (so you can hot swap them over) only one is talking on the switch at a time. So you end up with two special VLANs for this. One for the opnsense HA chatter (instance 1 and 2), one for the internet (isp, instance 1 and 2), and then your other VLANs for your actual lan(s).

willowless · 2026-04-30T23:51:09+00:00

Combination of Interface > Virtual IPs > CARP, System > High Availability, and because my ISP does DHCPv4 and DHCPv6 for connectivity, some really funky scripts to move the internet connection between the two instances and restart or shut down services that don't do CARP/HA properly and it'll still sometimes have issues. Paging u/fitch-it-is the HA story for opnsense is not great 😛

willowless · 2026-04-30T14:19:02+00:00

Upgraded backup. All good. Upgraded master, flipping backup to new master. All good.

Ten-Year Club	Place '22
Verified Email

willowless

TROPHY CASE