Dodecahedron December

I try things on the internet.

rarely, shit just works.

  • 0 Posts
  • 42 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle






  • 1 contributor’s opinion and the existence of one community does not an argument make.

    the devs don’t care about laws, if you want to put it so broadly, because the devs aren’t the ones who would get in trouble here, anyway. instance owners would likely catch the most trouble, especially because you can also add your own gdpr compliance if you want to.

    also most devs aren’t facebook. most devs don’t really care too much about tracking users. the commercial sector on the other hand…













  • +1 for nginx, although there has been some concern because nginx is developed by a group of russians though it is open source and appears to still be widely used. If this worries you, look into traefik.

    Otherwise does your ProxMox setup run docker containers? If so you can use NginxProxyManager which has a web gui for configuring your virtual hosts.

    At a high level what you need is this:

    • all domains routed to your host (or home if self hosting) IP.
    • that IP needs to have a reverse proxy server like traefik or nginx listening on port 80 and port 443 if you want ssl/tls.
    • your app servers which run lemmy, nextcloud, etc can be anywhere on your network where your reverse proxy can access. You’ll need to create vhosts for each. The server uses the Host header to determine which IP to reverse proxy to, eithe lemmy.moorefam.net or nextcloud.moorefam.net
    • the reverse proxy will get the content from lemmy or nextcloud and serve it via that IP and port.
    • ensure your home router is port forwarded on 80 (and 443 if you want ssl/tls) if you want to access these instances from the public internet but beware, you might want to add a firewall in-between if you aren’t confident in your router’s firewall.