I managed to solve the ingress-nginx issues mentioned in the previous post. The solution was found in this blog post and it was actually a recent security-related addition for ingress-nginx. And being the decisive person I am, the homeserver is once again powered by k3s.

Nextcloud, the go-to for most self-hosters, doesn’t really need introductions. This post has been long in the making, mainly due to my recent change from running everything with Podman to Kubernetes with k3s. Long story short, k8s is fun and interesting, but Podman pods are rock solid. I had an accident on new year configuring cluster ingress, and had to make a quick decision on whether to spend the night figuring it out, or switch back to trusty old ways. I chose the latter.

I’ve recently moved almost all of my self-hostings under Kubernetes, k3s to be specific. One of the things that’s not so nice on Kubernetes is serving static sites. Since there’s no “regular” NGINX in front of the services anymore, serving a static site would basically need a separate web server container running behind ingress-NGINX. It’s a perfectly valid way to serve a static site, but I wanted something a bit more automated.

The site has had an RSS feed since the beginning, being built with Hugo. I’ve been really busy with work since the last post about Immich, so no writing new content here has been on the backburner.

A popular problem privacy-minded self-hosters are trying to solve is photo management and automatic backup from mobile devices. The big players, specifically Google and Apple dominate this field, with their main advantage being full control over the respective mobile operating systems. I haven’t used Apple devices after iPhone 5s, but on Android you just sign in to you Google account to be able to use the Play store, and Google Photos is already there, with all your old photos available.

The previous posts laid the basis, now it’s time for the first real example.

There’s one thing I’ve been missing while running GrapheneOS , passkey support. There was a period shortly after the release of Android 14 when I went back to stock Pixel OS. Before this, Vanadium, the default browser of GrapheneOS did not support passkeys at all. To be honest, I’m not 100% sure if there was some level of support, but since I don’t use Google Passwords, and Bitwarden didn’t have any support for passkeys at the time on mobile, I didn’t really look very hard. Nowadays I’m back on GrapheneOS, and trying hard to steer clear of Google Services.

The layout

I like to keep all the relevant files for each respective service under a single filesystem tree. The first obvious reason is keeping things organized, but since the underlying file system is ZFS, it allows to snapshot the whole tree in one go, as the directory is a ZFS dataset.

I self-host some stuff, using Podman. There are a whole bunch of guides online, and it feels like most of them have consolidated on docker-compose. This is understandable, considering how Docker was the first in the field, and docker compose provides a nice way to do multi-container infrastructure as code-type deployments with just a single file.

After a couple years of keeping this site in cold storage, I decided it’s time to bite the bullet and put it back online.