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.
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.
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.
Yep, from the first button press, because it’s easier, an it doesn’t really matter which you do as long as it’s the same each time.
It’s mind-bogglingly convenient, especially compared to the before times. Consider donating to them if you can.
Guide to Self Hosting LLMs with Ollama.
ollama run llama3.2
Forgejo - actively developed open source. It’s what powers Codeberg. Easy to set up and manage with Docker. I moved to it from Gogs and skipped Gitea after reading about the forks.