Partner and CEO of Find the Path Ventures (https://find-path.com). Voice actor, software engineer, and general nerd.

  • 3 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle






  • 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.










  • You primarily need Docker, specifically (unless you want to set it all up by hand) Docker Compose. All installation options for Lemmy utilize Docker to host the components (db, API, UI, etc.). Depending if you go the Ansible or Docker/manual route you will need Nginx as well.

    You will need disk space to store content (including pictures). The CPU/RAM needs are super low unless you have a lot of people on your instance.

    You will need a domain for federation to work (like my instance is at lemmy.wizjenkins.com).

    Lastly you will need an SSL certificate but Lemmy can generate this for you assuming you have your domain pointed to your server before you start everything up.

    I’m not familiar with QNAP but generally NAS servers don’t support Docker Compose so you might be better off with a raspberry pi or VM or something.