Hey, take a look at this user's post, they set up their instance with docker and posted their compose and config files. I was able to get up and running using that.

I am fairly sure you can customize the nginx.conf that is bundled with the docker installation method, to add some virtual host directives to add any subdomains you want and forward to the appropriate backend.

You could also run another nginx instance on your host to handle all the subdomain virtual hosts and forward to the lemmy containers. It’s a bit more complicated but definitely should be possible. You will have to do the research and figure it out via trial and error though, unfortunately. Not a lot of documentation and how-to articles out there yet. This is all still fairly new, relatively speaking.

Note: posted using mlem for iOS, sorry if this comment is messed up in any way.

I have not done this exactly but I recommend Treafik for setting up a reverse proxy. The reason I like it is because it's quite simple and visual.

You have three things. Entrypoints (listeners on a port), Routers (rules for how traffic should go) and Services (your stuff, like Lemmy).

https://traefik.io/traefik/

The visual part is quite nice. And you route traffic using ordinary docker labels if you use docker for example.

I am running Lemmy in a Kubernetes cluster. You can find the helm charts and a short documentation here: https://github.com/grouvie/lemmy_help

I am happy to help should anyone have further questions. :)

@paulie420 Don't forget that there are alternatives out there that are (almost) fully compatible, I'm just using my #Friendica instance that I set up years ago.

I host my instance exactly like this with Nginx Proxy Manager. Here's my config:

• Block Common Exploits and Websockets Support - on
• Add a custom location with the following settings:
  • proxy_set_header X-Real-IP $remote_addr;
  • proxy_set_header X-Forwarded-For $remote_addr;
  • proxy_set_header X-Forwarded-Host $remote_addr;
  • real_ip_header X-Real-IP;
  • real_ip_recursive on;
• for SSL turn on HTTP/2 Support

I had to add the custom config so that I would get the IP address of the clients and federated servers. Otherwise I was hitting rate limits on the Lemmy server.