Of course security comes with layers, and if you’re not comfortable hosting services publically, use a VPN.

However, 3 simple rules go a long way:

1. Treat any machine or service on a local network as if they were publically accesible. That will prevent you from accidentally leaving the auth off, or leaving the weak/default passwords in place.

2. Install services in a way that they are easy to patch. For example, prefer phpmyadmin from debian repo instead of just copy pasting the latest official release in the www folder. If you absolutely need the latest release, try a container maintained by a reasonable adult. (No offense to the handful of kids I’ve known providing a solid code, knowledge and bugreports for the general public!)

3. Use unattended-upgrades, or an alternative auto update mechanism on rhel based distros, if you don’t want to become a fulltime sysadmin. The increased security is absolutely worth the very occasional breakage.

4. You and your hardware are your worst enemies. There are tons of giudes on what a proper backup should look like, but don’t let that discourage you. Some backup is always better than NO backup. Even if it’s just a copy of critical files on an external usb drive. You can always go crazy later, and use snapshotting abilities of your filesystem (btrfs, zfs), build a separate backupserver, move it to a different physical location… sky really is the limit here.

https://mailcow.email/

Isn’t that mainly a problem with recursive DNS servers? The authoritative servers are only aware of the few domains they’re hosting.

What’s wrong with miracast? Almost every device sold these days has some kind of radio, but no way to talk to each other. Releasing a new standard every few years won’t help much.

Running for 6 days, save_pieces: false

My database is currently 184 GB

Back in the windows 2012 era, we knew every time a major windows update was pushed, because the same set of customers would always create a ticket, complaining about inaccessible RDP. Windows firewall is just opinionated like that.

I think we’re going backwards. Back in the day, we were grabbing and indexing the data directly from DHT.

You can easily integrate the jellyfin to kodi, and have both - consistent library across multiple devices AND beautiful UI.

There are 2 addons for it.

One will allow you to browse your jellyfin media using the api, and to reencode on the fly, but it’s annoyingly slow to browse the library this way.

The other one will integrate your jellyfin library to local kodi database. You just need to specify the path to your samba share in the jellyfin library. It’ll fetch the metadata from jellyfin, but access the media using SMB directly. It’s pretty fast, since kodi doesn’t have to scrape the metadata itself, and it keeps itself up to date, no need for periodic library rescans.

You obviously know a thing or two about Kubernetes. I’m trying to learn. I’ve been at the cloud native conference, I attended the vmware tanzu course, even played with microk8s on my laptop. I still look for the “aha!” moment, when I understand the point of it all, and everything clicks into place.

However, whenever I see somebody describe their setup, I just cringe. It all just feels like we’re doing simple things in an obscure and difficult way.

The technology has been here for almost a decade, and it’s obviously not going away. How can I escape the misery, and start loving k8s?

Picture somehow related…