Are you running these llms in containers completely cut off from the internet? My understanding was that the “local first” llms aren’t truly offline and only try and answer base queries offline before contacting their provider for support. This invalidating the privacy argument.
Do you by any chance faces a guide on how to get that running?
Do you need to reboot after every update or updates applied live? Only have experience with rpm-ostree on kinoite
AIO is the way
Or use caddy with a dns challenge. No need to open any ports and just use it completely locally without any annoying warning.
You need to set a trigger for tubearchivist-jf to run after you’ve downloaded a video.
The docker compose ist almost copy paste. Not quite sure what the difficulty is?
I’ve had major problems for days like half a year ago. Switched to dynv6.net with no issues so far.
My yellow is powered by a 4GB Ram compute module and it’s doing great. I was lucky to get it three months after release.
I manage zigbee directly from the yellow with no issues. The built in radio handles both zha or zigbee2mqtt. So whichever you prefer… Matter over thread also works once you tell the radio to support both simultaneously. (All described in the yellow docs)
Caddy combined with dns challenges are the dream!
Z or z. Depends on the scenario
Spiritual successor to podgrab is podfetch https://github.com/SamTV12345/PodFetch
My yellow has been updating for an hour now
How do you power your setup?
Are you loosing the mounts after a reboot? As in, are you mounting via /etc/fstab?