Wireguard has effectively zero impact on my setup.

@MightyCuriosity

Oh, well yeah, you can do that too. In fact, you may not even need a DDNS. I don't have one for my fedi server, and I only ever had to change the IP on my DNS after we got hit by an earthquake and all of the local datacenters went out.

I choose not to do the DNS option for 90% of the things I host. Partly because my ISP has limitations on which ports can be exposed and, in general, I prefer not to expose any ports especially when I am serving up my own data.

But that's just my paranoia talking. :cat_rock_on:

VPN + DDNS is what I do. You may be thinking about the perf hit of putting all your home connections through a VPN. That's not the idea here. For self hosted services you would set up a wireguard "server" at your house. Then you connect your phone back to it to access your services.

With Wireguard it's pretty easy to do a split tunnel, so that the VPN connection is only used for traffic to your home servers. Nothing else is affected, and you have access to your house all the time.

This is better for security than DDNS + open ports, because you only need a single open UDP port. Port scanners won't see that you are hosting services and you wouldn't need to build mitigations for service-specific attacks.

As far as podman, I am migrating to it from a mix of native and docker services. I agree with others that getting things set up with Docker first will be easier. But having podman as an end goal is good. Daemonless and rootless are big benefits. As are being able to manage it as systemd units via quadlets.