It is only resolving for devices in the Tailnet. Kuma is checking they are all up, and this Ansible playbook is checking they have all their updates. I wouldn’t have thought that was an unusual arrangement - and it’s worked perfectly for about a year till about three weeks ago.

> go to the cinema
> empty.jpg
> Jay Kay comes in and sits directly in front of me

Yes, this.

Thanks yes - that’s exactly what I needed.

Thanks - this is exactly what I needed.

Yes - we’re “I’ll let you use my electricity for your computer thing” friends, not “I’m okay with seeing your printer on my home network” friends.

Yes - it seems odd not to report both.

Spot on. I guess that’s one of those lead smurf hats.

Kavita is for ebooks - it’s not perfect, has some weirdness with series sometimes because of it’s manga heritage.

For me, AudioBookShelf is the clear standout for audio books, and I ended up going with Kavita for ebooks.

I have it in a git repo, broken down by the nodes and vps names. In each of these folders is a mixture of Ansible playbooks, docker compose or just markdown files with the descriptions. Some is random stuff - my VPS allows the export of the cloud firewalls as JSON for instance. All the secrets needed by Ansible are in an Ansible vault, the rest in KeePass.

Or just trotting, we don’t know.

Taxidermists hate this one trick.

Prediction: data about measles cases stops being collected and published.

Just squirt him with the water bottle if he starts asking questions like this.

Guide to Self Hosting LLMs with Ollama.

• Download and run Ollama
• Open a terminal, type ollama run llama3.2