In part 1, and part 2, I’d got Forgejo running on my Synology NAS, with HTTPS and SSH access. It’s not being backed up (or restored); let’s fix that.

In part 1, I’d got Forgejo running on my Synology NAS, but SSH access wasn’t working properly. In this part, I’m going to fix that by using HAProxy.

I want to install Forgejo on my Synology NAS. I’m going to attach it to the macvlan network I createed yesterday. I’m not going to use Synology’s built-in Web Portal (reverse proxy thing). Here’s how I did it.

If you use the bridge or host network drivers in Docker, containers must use different port numbers to be accessible on the host network. Here’s how to use the macvlan driver to assign a unique IP address to each container, allowing containers (and the host) to use the same port numbers.

Pushing a simple node.js-based image to my private docker registry failed.

The default option for persistent volumes on k3s is local-path, which provisions (on-demand) the storage on the node’s local disk. This has the unfortunate side-effect that the container is now tied to that particular node.

I wanted to get Erlang running on my Synology NAS, for various reasons, and was struggling with the cross compiler.