![](https://lemmy.world/pictrs/image/4ebf2397-acf9-43ec-b026-7a00e5bb735e.jpeg)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
The thing is, people might not know that they have to look for the Docker setup. Now if they search for “Lemmy on Synology NAS” they land on this guide, telling them to use Docker.
The thing is, people might not know that they have to look for the Docker setup. Now if they search for “Lemmy on Synology NAS” they land on this guide, telling them to use Docker.
Afaik this is not an error from Lemmy but from nginx, which is not able to relay the request to Lemmy and therefore returns a 502 bad gateway response. Imo this just means the servers are over capacity, so most likely a scaling/infrastructure issue.
I had a quick read of the code and it looks pretty solid to me. Not the most “enterprise” code imaginable, but definitely no code smell or quick hacking job.
Same. Having all their custom software available and just one click away is amazing, and with Docker you can install everything else just like a regular server. It’s the best of both worlds imo.
If you don’t have any restrictions (limited subdomains, service only works on the server root etc.) then it’s really just a personal preference. I usually try paths first, and switch to subdomains if that doesn’t work.
My server is a DiskStation, so I use HyperBackup to do an encrypted backup of the important data to their Synology C2 service every night.