

Is there a reason not to use Tailscale for this?
Is there a reason not to use Tailscale for this?
Great job on the banner - I could hear the theme in my head.
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.
Me in the break room stopping the microwave before the beeps:
Here future microwave user, have these free nine seconds I’m leaving you.
Me finding the timer is not cleared when I want to use the microwave:
Ugh, now I have to press the reset button before I can enter the length of time to warm my lunch. Who was the accursed person who left time on here?
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.
> afterallwhynot.jpg
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.
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.
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
I’m also on Silverbullet, and from OP’s description it sounds like it could be a good fit. I don’t use any of the fancy template stuff - just a bunch of md files in a directory with links between them.
Your workload (a NAS and a handful of services) is going to be a very familiar one to members of the community, so you should get some great answers.
My (I guess slightly wacky) solution for this sort of workload has ended up being a single Docker container inside an LXC container for each service on Proxmox. Docker for ease of management with compose and separate LXCs for each service for ease of snapshots/backups.
Obviously there’s some overhead, but it doesn’t seem to be significant.
On the subject of clustering, I actually purchased three machines to do this, but have ended up abandoning that idea - I can move a service (or restore it from a snapshot to a different machine) in a couple of minutes which provides all the redundancy I need for a home service. Now I keep the three machines as a production server, a backup (that I swap over to for a week or so every month or two) and a development machine. The NAS is separate to these.
I love Proxmox, but most times it get mentioned here people pop up to boost Incus/LXD so that’s something I’d like to investigate, but my skills (and Ansible playbooks) are currently built around Proxmox so I’ve got a bit on inertia.
Is that a mini? I love those little 1L HP’s. I run 3 G2 800’s. These are very nicely built and therefore a joy to work on, and sip power when idling. Highly recommend. Also +1 for Proxmox.
I just do one Docker container per LXC. All the convenience of compose, plus those sweet Proxmox snapshots.