They fucked up by making their robots last seemingly forever, due to the fact they spy on you and get stuck every 15 mins so you never want to turn them on.

What about multiple Pis? Seriously asking. I love having a Pi as a dedicated server (small footprint, low energy, low temp). Do I really need to switch to a more traditional ITX/ATX form factor to get real reliability?

Let’s be honest, not all races are equal<br> 🫲🍊🫱

Be aware you might have to resort to nftables if firewalld doesn’t work. I use localhost a lot and the routing rules are different in that case.

Thanks for mentioning Wolf. I’m pretty happy with Sunshine but I do have those occasions where it can’t stream because my monitor is turned off (upstairs) when I’m downstairs.

As soon as I saw Plex show media that wasn’t part of my personal library I knew it was becoming enshitified.

I convert my files to avoid transcoding but my Raspberry Pi 4B handles Jellyfin just fine.

Even if it isn’t an OpenWRT router if you have a hardwired server it can probably do a soft reset of the router or even modem (most modems I’ve used have had a web interface). If your router is in such a bad state it only responds to a hard reset it’s probably reaching EoL.

As I’ve found out recently, finding true alternatives can be difficult. Take bread for instance. I just discovered Bimbo Bakeries own at least 26 brands. So when you’re on the bread aisle you probably have a moderate to high chance of buying one of their products.

For me it really depends on the use-case. A lot of times I want persistence but don’t really care to access the data outside of the container. So rather than using the extra brainpower to make up folders myself and ensure paths don’t change I just let Docker handle those details for me. Also I use Podman a fair amount and it seems to be more troublesome when it comes to bind mounts.

I probably made a small mistake in setting that up but I tried making the dedicated “home movies” folder and it wouldn’t show my videos.

Only issues I’ve had with Jellyfin are reduced flexibility in naming/organizing files and inability (for me at least) to detect personal media.

These are a good alternative to RPis. Just be aware some of these are sort of haphazardly assembled so they might have cooling issues or bad power supplies.

In addition to other advice you could also use SSH over Wireguard. Wireguard basically makes the open port invisible. If you don’t provide the proper key upfront you get no response. To an attacker the port might as well be closed.

Here’s at least one article on the subject: https://rair.dev/wireguard-ssh/

I like named volumes, externally created, because they are less likely to be cleaned up without explicit deletion. There’s also a few occasions I need to jump into a volume to edit files but the regular container doesn’t have the tools I need so it’s easier to mount by name rather than hash value.

I did this and the fun thing about it is that your runner can access things inside your network that a regular GitLab runner can’t. I’ve used it to manage a k8s cluster that isn’t exposed to the Internet at all.

I don’t think it necessarily needs to be either or. Organizing the playbooks and folders myself can be stressful so an extra layer of organization might work best for you. There are other tools like Semaphore that are specifically built for Ansible executions though. Might need a lot of duct tape for Jenkins to run Ansible.

And if you’re not a fan of yaml you can always nope out and embed shell scripts into your Playbooks. You can even put Docker compose yaml inside a playbook but it’s a bit inception-y and I don’t really recommend that.

Ansible is nice but I’ll repeat (as I said in another thread) it’s kind of advanced and gives a much better return on investment if you manage several hosts, plan to switch hosts regularly, or plan to do regular rebuilds of the environment.

Programming is generally not needed when self-hosting. At best you might learn Ansible, Puppet, Salt, or Terraform, but that’s for advanced scenarios (e.g. easily shifting the workloads between machines or into the cloud).

Learning the ins-and-outs of containers will get you the biggest return on investment. They’re not strictly necessary but most tools will expect that is the common use-case and the community won’t be as much help. Until you know more about containers I would also recommend Docker over Podman. It has a few more “conveniences” than Podman and orgs like LinuxServer will target Docker as the engine.

Right. When a request comes in, Traefik, for one, will hold the connection until the service is back up then forward the request as usual. This works for UIs as well. You’ll get a temporary loading page then redirected to the requested UI when the service is up.