Lead admin for https://lemmy.tf, tech enthusiast

  • 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle















  • I’ve got a baremetal server with OVH running VMware, so it’s just a VM that I manage. I’m paying more for it than I’d like, but it’s running far more than just Lemmy. If I wind up ditching it in the future, it’s just a quick vMotion off to another machine + DNS updates.

    Here’s a current output of my storage about a week into hosting the instance. It’s growing slower than I expected, and I do have plans to move volumes/pictrs up to an s3 bucket whenever I start running low on local storage.

    [jon@lemmy lemmy]# du -sh volumes/*
    2.5G    volumes/pictrs
    2.2G    volumes/postgres
    

    I would recommend locking down SSH on your Lemmy server, I have mine restricted to allow logins from VPN only. Otherwise you’ll get probed 24/7 with a public server.


  • Do you need access control? If not, a simple Apache/Nginx directory listing is nice and easy, just drop your files in your webroot and you’re set. h5ai is a nice addition if you go that route.

    If you need access control (or at least some sort of obfuscated URLs), Nextcloud is a good option. Pretty easy to get up and running, and there’s a ton of plugins available.


  • From what I’ve seen and read, server to server traffic is less taxing on instances than client to server. So even if your instance is JUST you, it would be your instance talking to everything else so it would have some net benefit on the federation. But it would take a lot of users self-hosting solo instances for this to help in any noticeable way, I’d think.

    There is certainly no downside to running a solo instance, if you’re even slightly interested I would say go for it!


  • I’m one of the other Lemmy.tf admins and I’ll share a bit. We’re currently on the docker-compose deployment from the repo, running on a VM with 4c/8gb ram/256gb disk. It’s on a baremetal VMware box at OVH with loads of resources to expand as needed.

    I’m hoping we get enough users on here to force me into converting to a Helm chart and moving this to my Kubernetes cluster. Pod scaling would help address some of the issues larger instances are starting to run into, and it seems like a fun project.

    As for Unraid, your best bet is to see if you can install docker-compose on it. This thread from 2020 suggests it should be possible, but the binary may not persist restarts. If you can’t use compose you would probably have to strip it apart and deploy one container at a time, and potentially work around the need for the Docker networks.

    I may be interested in helping with an Unraid deployment guide if there’s heavy interest- I’m running it on my NAS at home and can tinker a bit. Feel free to DM me if you’ve got questions or need any assistance.

    Edit: That Unraid forum post has a reply about using a bash alias to run docker-compose in Docker, this is the route I’d go rather than having to do jank stuff to make the binary persistent. Should be able to follow the normal docker-compose install from your root user once you have compose ready. Make sure to do your port forwarding or use Nginx Proxy Manager since SSL is mandatory to federate.