+1 all my servers run Linux or FreeBSD, I use macOS as desktop (most of the stuff is neat and out of the box and it uses less resources) and I use Windows while working with my customers and some of their servers. I would definitely not choose Linux for desktop (I tried and gave up), but it is great for the servers.

No problem, if you run into issues let me know I may be able to help. Not an expert at Docker, but I do have a handful of containers running here and there.

Well if you are using docker-compose you could probably get rid of the nginx container and only deploy the other four: lemmy, lemmy-ui, pictrs, postgres. You would then use the nginx.conf stuff you have in place for the docker container of nginx to proxy to lemmy-ui and lemmy on ports 1234 and 8536. Or if you plan to keep using the docker container for nginx then you can change the listening port in the nginx.conf of the container:

listen 80;

to something different like

listen 1080;

Also in the docker-compose.yml you would update the nginx ports to 1080:1080.

Hope this answers your question.

HaProxy for most of the stuff and Nginx for very limited stuff. Or a combination between HaProxy and Nginx in some very special cases.

Mlem looks promising, if it can develop the save functionality that Apollo has then it gets my vote.

I used docker-compose version and had to work around a couple of bugs like needing to redundantly install Nginx and Let’s Encrypt for it to work properly with SSL and also having to add the lemmy container to the internet facing network due to the DNS not working on it and subsequently loosing federation capability. Overall a bit of a struggle, but this is common with FOSS.

Debian