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

help-circle
  • I did this recently and I wish I could answer you, but I’m on mobile and don’t remember exactly what got it working. I also referenced the guide linked below, along with the proxmox documentation.

    If you start blacklisting drivers, you’ve gone too far for passing through Intel quicksync. I think I’m the end it was a pretty basic config, like checking motherboard settings and adding text to the grub config.

    Also don’t guides say you have to use q35 as the machine type for the VM, but that didn’t work for me. Only 440fx works for me.



  • Good timing for this thread. I just finished consolidating 2 computers worth of fun into 1 newer computer that can do it all. I sold my wife on the idea with electricity as the reasoning.

    In the end, it uses 30 watts less, which is not as much as I had hoped. That’s about $5 a month.

    180 watts with an i5-13400, 9 spinning disks, 1 M.2 SSD, no extra GPU, 24 port switch (powers 3 AP’s), modem, Mikrotik router, and a large UPS. I wonder if the UPS uses any power as a trickle charge for the batteries.


  • I’d say start with getting Lemmy going inside your home network (not accessible to the outside world). That’ll give you a chance to play around with Docker if you want to go the Docker route. I like to make Portainer the first docker container I install (I install it with Docker Compose), and then I manage all other docker containers/etc. through Portainer. Just a quick heads up on Portainer… what Docker calls “docker compose”, Portainer calls a “Stack”, because it can have a “stack” of different stuff running under it.

    Anyway, from there I’d figure out a reverse proxy. I use Nginx Proxy Manager, which is nginx under the hood, with a web interface to manage things. I’ve never tried Caddy, but people like that one, too.

    The reverse proxy is what controls security, basically. Someone from outside your network types in lemmy.superspruce.org, and you’ve told Dynadot to forward that to your home IP address. You open port 80 and 443 on your router, and forward them to the machine running Nginx-Proxy-Manager. So NPM gets everything that’s pointed at your house on those ports. It see’s the request is for lemmy.superspruce.org, and you’ve told NPM where to look for that, and it handles it from there.

    Just doing these things will open up all sorts of learning challenges that you’ll have to figure out through Googling.

    It took me years to finally decide to figure out a reverse proxy, and once I wrapped my head around it it makes so much sense. I wish I had learned it sooner.












  • The number of redundant drives actually doesn’t make much difference, but it does “help”. Instead of picturing individual drive failures, picture a house fire.

    Also picture the next step after one of the drives fails – you’ll be copying all of that data off of your 1 good drive, putting a lot of stress on it. That drive is likely from the same batch, same age, etc. as the failed drive. The likelihood of your good drive failing during the recovery process is higher than one might like.